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

2014-03-13 Thread Jay Pipes
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] [sahara] team meeting minutes March 13 [savanna]

2014-03-13 Thread Sergey Lukjanov
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] [qa] Python 3.3 patches (using six)

2014-03-13 Thread David Kranz
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] [Nova] FFE Request: Ephemeral RBD image support

2014-03-13 Thread Josh Durgin
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] does exception need localize or not?

2014-03-13 Thread Doug Hellmann
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] [qa] Python 3.3 patches (using six)

2014-03-13 Thread Sean Dague
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] [qa] Python 3.3 patches (using six)

2014-03-13 Thread David Kranz
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] does exception need localize or not?

2014-03-13 Thread Alexei Kornienko
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.

[openstack-dev] Duplicate code for processing REST APIs

2014-03-13 Thread Steven Kaufer
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] [Neutron][LBaaS] Mini-summit Interest?

2014-03-13 Thread Mark McClain
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

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

2014-03-13 Thread Roman Podoliaka
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] Duplicate code for processing REST APIs

2014-03-13 Thread Kevin L. Mitchell
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] [db][all] (Proposal) Restorable & Delayed deletion of OS Resources

2014-03-13 Thread Mike Wilson
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?

2014-03-13 Thread Edgar Magana
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] [keystone] 5 unicode unit test failures when building Debian package

2014-03-13 Thread John Dennis
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] [neutron][rootwrap] Performance considerations, sudo?

2014-03-13 Thread Carl Baldwin
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] [Mistral] Actions design BP

2014-03-13 Thread Dmitri Zimine
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] does exception need localize or not?

2014-03-13 Thread Doug Hellmann
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] Local vs. Scalable Engine

2014-03-13 Thread Dmitri Zimine
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?

2014-03-13 Thread Joshua Harlow
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

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

2014-03-13 Thread Joshua Harlow
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] [Mistral][Taskflow][all] Mistral + taskflow

2014-03-13 Thread Boris Pavlovic
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

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

2014-03-13 Thread Joshua Harlow
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] [qa] [neutron] Neutron Full Parallel job - Last 48 hours failures

2014-03-13 Thread Salvatore Orlando
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] [Mistral][Taskflow][all] Mistral + taskflow

2014-03-13 Thread Stan Lagun
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] [Mistral][Taskflow][all] Mistral + taskflow

2014-03-13 Thread Boris Pavlovic
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] Disaster Recovery for OpenStack - call for stakeholder

2014-03-13 Thread Luohao (brian)
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] Duplicate code for processing REST APIs

2014-03-13 Thread Matt Riedemann
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] [keystone] 5 unicode unit test failures when building Debian package

2014-03-13 Thread Thomas Goirand
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] [keystone] All LDAP users returned using keystone v3/users API

2014-03-13 Thread Nathan Kinder
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] OpenStack vs. SQLA 0.9

2014-03-13 Thread Thomas Goirand
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] [Nova][Cinder] Feature about volume delete protection

2014-03-13 Thread sxmatch
于 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] [Nova][Cinder] Feature about volume delete protection

2014-03-13 Thread 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, Zhangleiqiang 写道: > >> From:

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

2014-03-13 Thread weiyuanke
之前百度的张磊强师兄?? 你现在在华为搞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] OpenStack vs. SQLA 0.9

2014-03-13 Thread Roman Podoliaka
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

2014-03-13 Thread sxmatch
于 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] [Mistral][Taskflow][all] Mistral + taskflow

2014-03-13 Thread Renat Akhmerov
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

<    1   2