Re: [openstack-dev] [Mistral][Taskflow][all] Mistral + taskflow

Folks, Mistral and TaskFlow are significantly different technologies. With different set of capabilities, with different target audience. We may not be doing enough to clarify all the differences, I admit that. The challenge here is that people tend to judge having minimal amount of informatio

Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

于 2014-03-14 11:59, Zhangleiqiang (Trump) 写道: From: sxmatch [mailto:sxmatch1...@gmail.com] Sent: Friday, March 14, 2014 11:08 AM To: Zhangleiqiang (Trump) Cc: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection 于 2014-03-11 19:24

Re: [openstack-dev] OpenStack vs. SQLA 0.9

Hi all, I think it's actually not that hard to fix the errors we have when using SQLAlchemy 0.9.x releases. I uploaded two changes two Nova to fix unit tests: - https://review.openstack.org/#/c/80431/ (this one should also fix the Tempest test run error) - https://review.openstack.org/#/c/80432/

Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

之前百度的张磊强师兄？？ 你现在在华为搞open stack？ --- 韦远科 010 5881 3749 中国科学院 计算机网络信息中心 云计算平台：eccp.csdb.cn On 2014年3月6日, at 下午2:19, Zhangleiqiang wrote: > Hi all, > > Current openstack provide the delete volume function to the user. > But it seems there is no any protection for use

Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

> From: sxmatch [mailto:sxmatch1...@gmail.com] > Sent: Friday, March 14, 2014 11:08 AM > To: Zhangleiqiang (Trump) > Cc: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova][Cinder] Feature about volume delete > protection > > > 于 2014-03-11 19:24, Zhangleiqiang 写道: > >> From:

Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

于 2014-03-11 19:24, Zhangleiqiang 写道: From: Huang Zhiteng [mailto:winsto...@gmail.com] Sent: Tuesday, March 11, 2014 5:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection On Tue, Mar 11, 2014 a

Re: [openstack-dev] OpenStack vs. SQLA 0.9

On 03/14/2014 02:06 AM, Sean Dague wrote: > On 03/13/2014 12:31 PM, Thomas Goirand wrote: >> On 03/12/2014 07:07 PM, Sean Dague wrote: >>> Because of where we are in the freeze, I think this should wait until >>> Juno opens to fix. Icehouse will only be compatible with SQLA 0.8, which >>> I think i

Re: [openstack-dev] [keystone] All LDAP users returned using keystone v3/users API

On 03/13/2014 08:36 AM, Anna A Sortland wrote: > [A] The current keystone LDAP community driver returns all users that > exist in LDAP via the API call v3/users, instead of returning just users > that have role grants (similar processing is true for groups). This > could potentially be a very large

Re: [openstack-dev] [keystone] 5 unicode unit test failures when building Debian package

On 03/14/2014 05:20 AM, John Dennis wrote: > On 03/13/2014 12:31 AM, Thomas Goirand wrote: >> Hi, >> >> Since Havana, I've been ignoring the 5 unit test failures that I always >> get. Though I think it'd be nice to have them fixed. The log file is >> available over here: >> >> https://icehouse.dev-

Re: [openstack-dev] Duplicate code for processing REST APIs

On 3/13/2014 4:13 PM, Roman Podoliaka wrote: Hi Steven, Code from openstack/common/ dir is 'synced' from oslo-incubator. The 'sync' is effectively a copy of oslo-incubator subtree into a project source tree. As syncs are not done at the same time, the code of synced modules may indeed by diffe

Re: [openstack-dev] Disaster Recovery for OpenStack - call for stakeholder

1. fsfreeze with vss has been added to qemu upstream, see http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg01963.html for usage. 2. libvirt allows a client to send any commands to qemu-ga, see http://wiki.libvirt.org/page/Qemu_guest_agent 3. linux fsfreeze is not equivalent to windows f

Re: [openstack-dev] [Mistral][Taskflow][all] Mistral + taskflow

Stan, There is a big difference between TaskFlow and Mistral. TaskFlow is implemented + it's part of OpenStack (already). Mistral is under development and it's not a part of OpenStack. If Mistral would like someday to make incubation request it will get reasonable question: "Why Mistral reimplem

Re: [openstack-dev] [Mistral][Taskflow][all] Mistral + taskflow

Joshua, Boris, Renat, I call for this discussion to be technical rather than emotional. "Seems" is not appropriate word here. It seems like both Mistral and TaskFlow duplicate many similar services and libraries outside of OpenStack (BTW, what exactly in TaskFlow is OpenStack-specific?). So it is

Re: [openstack-dev] [qa] [neutron] Neutron Full Parallel job - Last 48 hours failures

Hi Rossella, thanks for doing this work! I think your results are pretty much consistent with what we've been empirically observing in recent days. elastic-recheck is flagging a resurgence of bug 1253896, and we need to have somebody look at it as soon as possib.e For bug 1291922, I've marked it

Re: [openstack-dev] [db][all] (Proposal) Restorable & Delayed deletion of OS Resources

Seems ok to me, and likely a good start, although I'm still not very comfortable with the effects of soft_deletion (unless its done by admins only), to me it complicates scheduling (can u schedule to something that has been soft_deleted, likely not). It also creates a pool of resources that can

Re: [openstack-dev] [Mistral][Taskflow][all] Mistral + taskflow

Joshua, Fully agree, seems like Mistral duplicates a lot of efforts of TaskFlow. I just don't see any reason why Mistral is reimplementing TaskFlow and not just adding new features to... Best regards, Boris Pavlovic On Fri, Mar 14, 2014 at 3:02 AM, Joshua Harlow wrote: > Separating from the

[openstack-dev] [Mistral][Taskflow][all] Mistral + taskflow

Separating from the following: * http://lists.openstack.org/pipermail/openstack-dev/2014-March/029870.html What can we do to resolve this, and reduce duplication in effort, code and so on. I believe that we are really doing the same thing, but it appears that something (imho) is wrong with the p

Re: [openstack-dev] does exception need localize or not?

From: Doug Hellmann mailto:doug.hellm...@dreamhost.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Thursday, March 13, 2014 at 12:44 PM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openst

Re: [openstack-dev] [Mistral] Local vs. Scalable Engine

We have access to all configuration parameters in the context of api.py. May be you don't pass it but just instantiate it where you need it? Or I may misunderstand what you're trying to do... DZ> PS: can you generate and update mistral.config.example to include new oslo messaging options? I f

Re: [openstack-dev] does exception need localize or not?

On Thu, Mar 13, 2014 at 5:03 PM, Alexei Kornienko < alexei.kornie...@gmail.com> wrote: > On 03/13/2014 10:44 PM, Doug Hellmann wrote: > > > > > On Thu, Feb 27, 2014 at 3:45 AM, yongli he wrote: > >> refer to : >> https://wiki.openstack.org/wiki/Translations >> >> now some exception use _ and so

Re: [openstack-dev] [Mistral] Actions design BP

Thanks Renat for a clear design summary, thanks Joshua for the questions, +1 to "let's move TaskFlow vs Mistral" discussion to separate thread, and my questions/comments on https://wiki.openstack.org/wiki/Mistral/Blueprints/ActionsDesign below: - Async actions: how do results of async action

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

Right, the L3 agent does do this already. Agreed that the limiting factor is the cumulative effect of the wrappers and executables' start up overhead. Carl On Thu, Mar 13, 2014 at 9:47 AM, Brian Haley wrote: > Aaron, > > I thought the l3-agent already did this if doing a "full sync"? > > _sync_

Re: [openstack-dev] [keystone] 5 unicode unit test failures when building Debian package

On 03/13/2014 12:31 AM, Thomas Goirand wrote: > Hi, > > Since Havana, I've been ignoring the 5 unit test failures that I always > get. Though I think it'd be nice to have them fixed. The log file is > available over here: > > https://icehouse.dev-debian.pkgs.enovance.com/job/keystone/59/console >

Re: [openstack-dev] [db][all] (Proposal) Restorable & Delayed deletion of OS Resources

After a read through seems pretty good. +1 On Thu, Mar 13, 2014 at 1:42 PM, Boris Pavlovic wrote: > Hi stackers, > > As a result of discussion: > [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion > (step by step) > http://osdir.com/ml/openstack-dev/2014-03/msg00947.html

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

That sounds like a good idea Mark! Yes, please do not do it during the World Cup at least the meeting is in Brazil :-) Edgar On 3/13/14 2:11 PM, "Mark McClain" wrote: > >On Mar 13, 2014, at 4:22 PM, Jay Pipes wrote: > >> >> >> I personally would not be able to attend a mini-summit days befo

Re: [openstack-dev] Duplicate code for processing REST APIs

On Thu, 2014-03-13 at 16:03 -0500, Steven Kaufer wrote: > While investigating some REST API updates I've discovered that there > is a lot of duplicated code across the various OpenStack components. > > For example, the paginate_query function exists in all these locations > and there are a few sli

Re: [openstack-dev] Duplicate code for processing REST APIs

Hi Steven, Code from openstack/common/ dir is 'synced' from oslo-incubator. The 'sync' is effectively a copy of oslo-incubator subtree into a project source tree. As syncs are not done at the same time, the code of synced modules may indeed by different for each project depending on which commit o

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

On Mar 13, 2014, at 4:22 PM, Jay Pipes wrote: > > > I personally would not be able to attend a mini-summit days before the > regular summit. I would, however, support a mini-summit about a month > after the regular summit, where the focus would be on implementing the > designs that are discuss

[openstack-dev] Duplicate code for processing REST APIs

While investigating some REST API updates I've discovered that there is a lot of duplicated code across the various OpenStack components. For example, the paginate_query function exists in all these locations and there are a few slight differences between most of them: https://github.com/openst

Re: [openstack-dev] does exception need localize or not?

On 03/13/2014 10:44 PM, Doug Hellmann wrote: On Thu, Feb 27, 2014 at 3:45 AM, yongli he > wrote: refer to : https://wiki.openstack.org/wiki/Translations now some exception use _ and some not. the wiki suggest do not to do that. but i'm not sure.

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

On 03/13/2014 04:56 PM, Sean Dague wrote: On 03/13/2014 04:29 PM, David Kranz wrote: On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: On 10 Mar 2014, at 22:54, David Kranz wrote: There are a number of patches up for review that make various changes to use "six" apis instead of Python 2 constru

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

On 03/13/2014 04:29 PM, David Kranz wrote: > On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: >> On 10 Mar 2014, at 22:54, David Kranz wrote: >> >>> There are a number of patches up for review that make various changes >>> to use "six" apis instead of Python 2 constructs. While I understand >>> the

Re: [openstack-dev] does exception need localize or not?

On Thu, Feb 27, 2014 at 3:45 AM, yongli he wrote: > refer to : > https://wiki.openstack.org/wiki/Translations > > now some exception use _ and some not. the wiki suggest do not to do > that. but i'm not sure. > > what's the correct way? > > > F.Y.I > > What To Translate > > At present the conve

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

On 03/13/2014 12:48 PM, Russell Bryant wrote: On 03/13/2014 03:04 PM, Josh Durgin wrote: These reverts are still confusing me. The use of glance's v2 api is very limited and easy to protect from errors. These patches use the v2 glance api for exactly one call - to get image locations. This has

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: On 10 Mar 2014, at 22:54, David Kranz wrote: There are a number of patches up for review that make various changes to use "six" apis instead of Python 2 constructs. While I understand the desire to get a head start on getting Tempest to run in P

Re: [openstack-dev] [sahara] team meeting minutes March 13 [savanna]

Heh, we should have a fathomless jar for it :( On Thu, Mar 13, 2014 at 11:30 PM, Matthew Farrellee wrote: > On 03/13/2014 03:24 PM, Jay Pipes wrote: >> >> On Thu, 2014-03-13 at 23:13 +0400, Sergey Lukjanov wrote: >>> >>> Thanks everyone who have joined Savanna meeting. >> >> >> You mean Sahara? :

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

On Thu, 2014-03-13 at 20:06 +, Jorge Miramontes wrote: > Now that the thread has had enough time for people to reply it appears > that the majority of people that vocalized their opinion are in favor > of a mini-summit, preferably to occur in Atlanta days before the > Openstack summit. There ar

Re: [openstack-dev] [nova] An analysis of code review in Nova

On 3/12/2014 7:29 PM, Arnaud Legendre wrote: Hi Matt, I totally agree with you and actually we have been discussing this a lot internally the last few weeks. . As a top priority, the driver MUST integrate with oslo.vmware. This will be achieved through this chain of patches [1]. We want thes

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

I disagree with the new dependency graph here, I don't think its reasonable continue to have the Ephemeral RBD patch behind both glance v2 support and image-multiple-location. Given the time that this has been in flight, we should not be holding up features that do exist for features that don't. I

Re: [openstack-dev] [sahara] team meeting minutes March 13 [savanna]

On 03/13/2014 03:24 PM, Jay Pipes wrote: On Thu, 2014-03-13 at 23:13 +0400, Sergey Lukjanov wrote: Thanks everyone who have joined Savanna meeting. You mean Sahara? :P -jay sergey now has to put some bitcoins in the jar... ___ OpenStack-dev mail

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

Hey everyone, Now that the thread has had enough time for people to reply it appears that the majority of people that vocalized their opinion are in favor of a mini-summit, preferably to occur in Atlanta days before the Openstack summit. There are concerns however, most notably the concern that

Re: [openstack-dev] [keystone] All LDAP users returned using keystone v3/users API

Hi Mark, The existing v3/users API will still exist and will show all users. So you will still be able to grant role to a user who does not have one now. I wonder if it makes sense to add a new API that would show only users that have role grants. So we would have: v3/users - list all users

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

On 03/13/2014 03:04 PM, Josh Durgin wrote: > These reverts are still confusing me. The use of glance's v2 api > is very limited and easy to protect from errors. > > These patches use the v2 glance api for exactly one call - to get > image locations. This has been available and used by other > feat

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

The restore use case is for sure inconsistently implemented and used. I think I agree with Boris that we treat it as separate and just move on with cleaning up soft delete. I imagine most deployments don't like having most of the rows in their table be useless and make db access slow? That being sa

[openstack-dev] [fuel-dev] [Fuel] Fuel Project 4.1 milestone reached!

Hi All, Just wanted to let everyone know that the Fuel Project met it¹s 4.1 milestone on Monday March 7th. This latest version includes (among other things): * Support for the OpenStack Havana 2013.2.2 release. * Ability to stop a deploym

[openstack-dev] [db][all] (Proposal) Restorable & Delayed deletion of OS Resources

Hi stackers, As a result of discussion: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step) http://osdir.com/ml/openstack-dev/2014-03/msg00947.html I understood that there should be another proposal. About how we should implement Restorable & Delayed Deletion

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

Excerpts from Tim Bell's message of 2014-03-12 11:02:25 -0700: > > > > > If you want to archive images per-say, on deletion just export it to a > > 'backup tape' (for example) and store enough of the metadata > > on that 'tape' to re-insert it if this is really desired and then delete it > > fr

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

Excerpts from Jay Pipes's message of 2014-03-12 10:58:36 -0700: > On Wed, 2014-03-12 at 17:35 +, Tim Bell wrote: > > And if the same mistake is done for a cinder volume or a trove database ? > > Snapshots and backups? > and bears, oh my! +1, whether it is large data on a volume or saved sta

Re: [openstack-dev] [sahara] team meeting minutes March 13 [savanna]

On Thu, 2014-03-13 at 23:13 +0400, Sergey Lukjanov wrote: > Thanks everyone who have joined Savanna meeting. You mean Sahara? :P -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/

[openstack-dev] [sahara] team meeting minutes March 13 [savanna]

Thanks everyone who have joined Savanna meeting. Here are the logs from the meeting: Minutes: http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-03-13-18.04.html Log: http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-03-13-18.04.log.html It was decided to not keep ba

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

On 03/12/2014 04:54 PM, Matt Riedemann wrote: On 3/12/2014 6:32 PM, Dan Smith wrote: I'm confused as to why we arrived at the decision to revert the commits since Jay's patch was accepted. I'd like some details about this decision, and what new steps we need to take to get this back in for Jun

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

Hi all, I would like to fix direction of this thread. Cause it is going in wrong direction. To assume: 1) Yes restoring already deleted recourses could be useful. 2) Current approach with soft deletion is broken by design and we should get rid of them. More about why I think that it is broken:

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

Will do! On Mar 13, 2014 10:13 AM, Solly Ross wrote: > > @Monty: having a packaging system sounds like a good idea.  Send us a pull > request on github.com/kanaka/noVNC. > > Best Regards, > Solly Ross > > - Original Message - > From: "Monty Taylor" > To: "Sean Dague" , "OpenStack D

[openstack-dev] [Neutron] [Nova] libvirt+Xen+OVS VLAN networking in icehouse

I've been playing with an icehouse build grabbed from fedorapeople. My hypervisor platform is libvirt-xen, which I understand may be deprecated for icehouse(?) but I'm stuck with it for now, and I'm using VLAN networking. It almost works, but I have a problem with networking. In havana, the VIF get

Re: [openstack-dev] [Congress][Data Integration]

Thanks for the feedback. Will create a design on these lines and send across for review On Wed, Mar 12, 2014 at 3:53 PM, Tim Hinrichs wrote: > Hi Rajdeep, > > This is an great problem to work on because it confronts one of the > assumptions we're making in Congress: that cloud services can be >

Re: [openstack-dev] Disaster Recovery for OpenStack - call for stakeholder

Funny this topic came up. I was just looking into some of this yesterday. Here's some links that I came up with: * https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sub-sect-qemu-ga-freeze-thaw.html - Describes how applicatio

Re: [openstack-dev] [heat][neutron] OS::Heat::AutoScalingGroup and OS::Neutron::PoolMember?

Therve told me he actually tested this and it works. Now if I could only configure DevStack to install a working Neutron... Regards, Mike From: "Fox, Kevin M" To: Chris Armstrong , "OpenStack Development Mailing List (not for usage questions)" , Date: 03/13/2014 02:19 PM Subject:

Re: [openstack-dev] [heat][neutron] OS::Heat::AutoScalingGroup and OS::Neutron::PoolMember?

Hi Chris, That's great to hear. I'm looking forward to installing icehouse and testing that out. :) Thanks, Kevin From: Chris Armstrong [chris.armstr...@rackspace.com] Sent: Wednesday, March 12, 2014 1:29 PM To: Fox, Kevin M; OpenStack Development Mailing List (

Re: [openstack-dev] [Mistral] Local vs. Scalable Engine

On the transport variable, the problem I see isn't with passing the variable to the engine and executor. It's passing the transport into the API layer. The API layer is a pecan app and I currently don't see a way where the transport variable can be passed to it directly. I'm looking at https://g

[openstack-dev] oslo incubator deprecation policy tweak

The Oslo team is working hard to move code from the incubator into libraries, and that work will speed up during Juno. As part of the planning, we have been developing our deprecation policy for code in the oslo-incubator repository. We recognize that it may take some projects longer than others to

Re: [openstack-dev] OpenStack vs. SQLA 0.9

On 03/13/2014 12:31 PM, Thomas Goirand wrote: > On 03/12/2014 07:07 PM, Sean Dague wrote: >> Because of where we are in the freeze, I think this should wait until >> Juno opens to fix. Icehouse will only be compatible with SQLA 0.8, which >> I think is fine. I expect the rest of the issues can be a

Re: [openstack-dev] [keystone] All LDAP users returned using keystone v3/users API

Hi Anna, On Thu, Mar 13, 2014 at 8:36 AM, Anna A Sortland wrote: > [A] The current keystone LDAP community driver returns all users that > exist in LDAP via the API call v3/users, instead of returning just users > that have role grants (similar processing is true for groups). This could > potent

[openstack-dev] [tempest][identity] Tempest

Hello, community! I'm trying to use Tempest to run tests on DevStack environment that is set up to use Identity API v3. Keystone uses policy.v3cloudsample.json to enable domain and cloud admins. The environment itself

Re: [openstack-dev] Replication multi cloud

Hi Chmouel, using this approach should I need to have the same users in both keystone? Is there any way to map user A from cloud X to user B in cloud Y? Our clouds have different users and replicates the keystone could have some problems, not only technical. Cheers, Marco On Thu, Mar 13, 2014

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

On Thu, Mar 13, 2014 at 7:50 AM, Joe Hakim Rahme < joe.hakim.ra...@enovance.com> wrote: > On 10 Mar 2014, at 22:54, David Kranz wrote: > > > There are a number of patches up for review that make various changes to > use "six" apis instead of Python 2 constructs. While I understand the > desire to

[openstack-dev] [oslo.messaging] [zeromq] nova-rpc-zmq-receiver bottleneck

Hello Folks, When zeromq is use as rpc-backend, "nova-rpc-zmq-receiver" service needs to be run on every node. zmq-receiver receives messages on tcp://*:9501 with socket type PULL and based on topic-name (which is extracted from received data), it forwards data to respective local services, over

Re: [openstack-dev] OpenStack vs. SQLA 0.9

On 03/13/2014 12:42 PM, Dan Smith wrote: >> Because of where we are in the freeze, I think this should wait >> until Juno opens to fix. Icehouse will only be compatible with >> SQLA 0.8, which I think is fine. I expect the rest of the issues >> can be addressed during Juno 1. > > Agreed. I think w

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

For some guests we use the LVM imagebackend and there are times when the guest is deleted on accident. Humans, being what they are, don't back up their files and don't take care of important data, so it is not uncommon to use lvrestore and "undelete" an instance so that people can get their data. O

Re: [openstack-dev] Replication multi cloud

You may be interested by this project as well : https://github.com/stackforge/swiftsync you would need to replicate your keystone in both way via mysql replication or something like this (and have endpoint url changed as well obviously there). Chmouel On Thu, Mar 13, 2014 at 5:25 PM, Marco Fa

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

@Monty: having a packaging system sounds like a good idea. Send us a pull request on github.com/kanaka/noVNC. Best Regards, Solly Ross - Original Message - From: "Monty Taylor" To: "Sean Dague" , "OpenStack Development Mailing List (not for usage questions)" , openst...@nemebean.com C

[openstack-dev] [MagnetoDB] MagnetoDB API draft

Hi all, Here is the draft for MagnetoDB API: https://wiki.openstack.org/wiki/MagnetoDB/api Your comments and propositions are welcome. And welcome to discuss this draft and any other KeyValue aaS -related subjects in our IRC channel: #magnetodb. Please note, MagnetoDB team mostly in UTC+2. Best

Re: [openstack-dev] [Neutron][ML2] Can I use a new plugin based on Ml2Plugin instead of Ml2Plugin as core_plugin

-- edited the subject I'm resending this question. The issue is described in email thread and. In brief, I need to add load new extensions and it seems the mechanism driver does not support that. In order to do that I was thinking to have a new ml2 plugin base on existing Ml2Plugin and add my chan

[openstack-dev] [MagnetoDB] Weekly meeting summary

Hello openstackers, You can find MagnetoDB team weekly meeting notes below Meeting summary 1. *General project status overview* (isviridov, 13:02:15) 2. *MagnetoDB API Draft status* (isvirid

Re: [openstack-dev] OpenStack vs. SQLA 0.9

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Because of where we are in the freeze, I think this should wait > until Juno opens to fix. Icehouse will only be compatible with > SQLA 0.8, which I think is fine. I expect the rest of the issues > can be addressed during Juno 1. Agreed. I think we

Re: [openstack-dev] OpenStack vs. SQLA 0.9

On 03/12/2014 07:07 PM, Sean Dague wrote: > Because of where we are in the freeze, I think this should wait until > Juno opens to fix. Icehouse will only be compatible with SQLA 0.8, which > I think is fine. I expect the rest of the issues can be addressed during > Juno 1. > > -Sean Sean,

Re: [openstack-dev] Replication multi cloud

Thanks Donagh, I will take a look to the ontainer-to-container synchronization to understand if it fits with my scenario. Cheers, Marco On Thu, Mar 13, 2014 at 03:28:03PM +, McCabe, Donagh wrote: > Marco, > > The replication *inside* Swift is not intended to move data between two > differ

Re: [openstack-dev] [TripleO] test environment requirements

On Thu, Mar 13, 2014 at 2:51 AM, Robert Collins wrote: > So we already have pretty high requirements - its basically a 16G > workstation as minimum. > > Specifically to test the full story: > - a seed VM > - an undercloud VM (bm deploy infra) > - 1 overcloud control VM > - 2 overcloud hypervis

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

I agree. Solly - in addition to potentially 'adopting' noVNC - or as a parallel train of thought ... As we started working on storyboard in infra, we've started using the bower tool for html/javascript packaging - and we have some ability to cache the output of that pretty easily. Would you

[openstack-dev] [Horizon] Regarding bug/bp https://bugs.launchpad.net/horizon/+bug/1285298

Hi all, Akihiro, David, This is regarding the review for - https://review.openstack.org/#/c/76653/ Akihiro - Thanks for the review as always and as I mentioned in the review comment I completely agree with you. This is a small featurette. However this is small in that it adds to a chociefield i

Re: [openstack-dev] [Congress] Policy types

Hi Prabhakar, I'm not sure the functionality is split between 'policy' and 'server' as cleanly as you describe. The 'policy' directory contains the Policy Engine. At its core, the policy engine has a generic Datalog implementation that could feasibly be used by other OS components. (I don't

Re: [openstack-dev] Disaster Recovery for OpenStack - call for stakeholder

Bruce, Nice list of use cases; thank you for sharing. One thought Bruce Montague wrote on 13/03/2014 04:34:59 PM: > > * (2) [Core tenant/project infrastructure VMs] > > > > Twenty VMs power the core infrastructure of a group using a > private cloud (OpenStack in their own datacenter). Not a

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

Aaron, I thought the l3-agent already did this if doing a "full sync"? _sync_routers_task()->_process_routers()->spawn_n(self.process_router, ri) So each router gets processed in a greenthread. It seems like the other calls - sudo/rootwrap, /sbin/ip, etc are now the limiting factor, at least on

[openstack-dev] [keystone] All LDAP users returned using keystone v3/users API

[A] The current keystone LDAP community driver returns all users that exist in LDAP via the API call v3/users, instead of returning just users that have role grants (similar processing is true for groups). This could potentially be a very large number of users. We have seen large companies with

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

On 2014-03-13 09:44, Sean Dague wrote: I think a bigger question is why are we using a git version of something outside of OpenStack. Where is a noNVC release we can point to and use? In Juno I'd really be pro removing all the devstack references to git repos not on git.openstack.org, because

Re: [openstack-dev] Replication multi cloud

Marco, The replication *inside* Swift is not intended to move data between two different Swift instances -- it's an internal data repair and rebalance mechanism. However, there is a different mechanism, called container-to-container synchronization that might be what you are looking for. It wi

Re: [openstack-dev] [Neutron][LBaaS] LBaaS design proposals

This is the object model proposals: https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance/Discussion From: Prashanth Hari [hvpr...@gmail.com] Sent: Thursday, March 13, 2014 9:51 AM To: OpenStack Development Mailing List (not for usage questions) Subject

[openstack-dev] [qa] [Infra] pep8 issues in tempest gate / testscenarios lib

Hi folks, I can't make it to the QA meeting for today so I wanted to summarize the issue that we have with the pep8 and tempest gate. An example for the issue you can find here: https://review.openstack.org/#/c/79256/ http://logs.openstack.org/56/79256/1/gate/gate-tempest-pep8/088cc12/consol

Re: [openstack-dev] any recommendations for live debugging of openstack services?

Well, for a non-interactive view of things, you can use the openstack.common.report functionality. It's currently integrated into Nova, and I believe that the other projects are working to get it integrated as well. To use it, you just send a SIGUSR1 to any Nova process, and a report of the c

Re: [openstack-dev] [3rd party testing] How to setup CI? Take #2

oh and in my haste I forgot to say: thank you extremely much to everybody who's been giving me pointers on IRC and especially to Jay for the blog walkthrough! On 13 March 2014 15:30, Luke Gorrie wrote: > Howdy! > > I have some tech questions I'd love some pointers on from people who've > succee

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

@sdague: We (the upstream noVNC/websockify maintainers) are attempting to get back on the bandwagon WRT releases. Unfortunately, before a few months back, the developer had taken a break from noVNC work, so there isn't a recent release. We just pushed a new release of Websockify the week befor

[openstack-dev] [Neutron][LBaaS] LBaaS design proposals

Hi, I am a late comer in this discussion. Can someone please point me to the design proposal documentations in addition to the object model ? Thanks, Prashanth ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

On 10 Mar 2014, at 22:54, David Kranz wrote: > There are a number of patches up for review that make various changes to use > "six" apis instead of Python 2 constructs. While I understand the desire to > get a head start on getting Tempest to run in Python 3, I'm not sure it makes > sense to d

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

The easiest/quickest thing to do for ice house would probably be to run the initial sync in parallel like the dhcp-agent does for this exact reason. See: https://review.openstack.org/#/c/28914/ which did this for thr dhcp-agent. Best, Aaron On Thu, Mar 13, 2014 at 12:18 PM, Miguel Angel Ajo wrote

Re: [openstack-dev] Climate Incubation Application

On 03/12/2014 12:14 PM, Sylvain Bauza wrote: > Hi Russell, > Thanks for replying, > > > 2014-03-12 16:46 GMT+01:00 Russell Bryant >: > The biggest concern seemed to be that we weren't sure whether Climate > makes sense as an independent project or not. We thin

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

I think a bigger question is why are we using a git version of something outside of OpenStack. Where is a noNVC release we can point to and use? In Juno I'd really be pro removing all the devstack references to git repos not on git.openstack.org, because these kinds of failures have real impact.

Re: [openstack-dev] Disaster Recovery for OpenStack - call for stakeholder

Hi, about OpenStack and VSS. Does anyone have experience with the qemu project's implementation of VSS support? They appear to have a within-guest agent, qemu-ga, that perhaps can work as a VSS requestor. Does it also work with KVM? Does qemu-ga work with libvirt (can VSS quiesce be triggered vi

Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step)

On 12 March 2014 17:35, Tim Bell wrote: > And if the same mistake is done for a cinder volume or a trove database ? Deferred deletion for cinder has been proposed, and there have been few objections to it... nobody has put forward code yet, but anybody is welcome to do so. _

Re: [openstack-dev] [3rd party testing] How to setup CI? Take #2

Howdy! I have some tech questions I'd love some pointers on from people who've succeeded in setting up CI for Neutron based on the upstream devstack-gate. Here are the parts where I'm blocked now: 1. I need to enable an ML2 mech driver. How can I do this? I have been trying to create a localrc w

Re: [openstack-dev] [OpenStack-Infra] Intermittent failures cloning noVNC from github.com/kanaka

@bnemec: I don't think that's been considered. I'm actually one of the upstream maintainers for noVNC. The only concern that I'd have with OpenStack adopting noVNC (there are other maintainers, as well as the author, so I'd have to check with them as well) is that there are a few other project

Re: [openstack-dev] [nova] [neutron] Top Gate Race - Bug 1248757 - test_snapshot_pattern fails with paramiko ssh EOFError

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Here is the latest marked fail - > http://logs.openstack.org/28/79628/4/check/check-tempest-dsvm-neutron/11f8293/ So, > looking at this a little bit, you can see from the n-cpu log that it is getting failures when talking to neutron. Specifically,

  1   2   >