[openstack-dev] [networking-ovn] Re: [ovs-dev] Issue when using ovn with Openstack

"dev" wrote on 07/19/2016 10:44:27 PM: > From: Chen Li > To: d...@openvswitch.org > Date: 07/19/2016 10:44 PM > Subject: [ovs-dev] Issue when using ovn with Openstack > Sent by: "dev" > > Hi list, > > I have

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

"discuss" wrote on 06/17/2016 05:24:19 PM: > From: Cathy Zhang > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)"

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 06/17/2016 04:07:38 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: discuss <disc...@openvswitch.org>, Na Zhu <na...@cn.ibm.com>, > "OpenStac

Re: [openstack-dev] [networking-ovn] provider networks

Murali R <muralir...@gmail.com> wrote on 06/17/2016 12:33:09 PM: > From: Murali R <muralir...@gmail.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, discuss <disc...@openvswitch.org> > Date: 06/17/2016 12:33 PM > Subject: Re: [ovs-disc

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

In-line below "discuss" wrote on 06/15/2016 05:51:20 PM: > From: John McDowall > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)"

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Apologies for being delayed on replying and in-line back as well Ryan John McDowall <jmcdow...@paloaltonetworks.com> wrote on 06/15/2016 05:58:35 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Na Zhu <na...@cn.ibm.com&

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

"discuss" wrote on 06/14/2016 10:31:40 PM: > From: John McDowall > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)"

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 06/02/2016 11:03:28 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, "disc...@openvswitch.org" > <disc...@openv

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/31/2016 07:57:02 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, "disc...@openvswitch.org" > <disc...@openv

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/31/2016 03:21:30 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, "disc...@openvswitch.org" > <disc...@openv

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/31/2016 03:19:54 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, "disc...@openvswitch.org" > <disc...@openv

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

"Armando M." wrote on 05/31/2016 01:12:32 PM: > From: "Armando M." > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 05/31/2016 01:13 PM > Subject: [openstack-dev] [Neutron][Release]

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/26/2016 11:08:43 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff <b...@ovn.org>, "disc...@openvswitch.org" > <disc...@openv

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/26/2016 10:59:48 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS, Ben Pfaff <b...@ovn.org> > Cc: "disc...@openvswitch.org" <disc...@openvswitc

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ben Pfaff <b...@ovn.org> wrote on 05/25/2016 07:44:43 PM: > From: Ben Pfaff <b...@ovn.org> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: John McDowall <jmcdow...@paloaltonetworks.com>, > "disc...@openvswitch.org" <disc...@openvswitch.org>, OpenS

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/25/2016 07:27:46 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/24/2016 06:33:05 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/18/2016 03:55:14 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

se?   Ryan   - Original message -From: John McDowall <jmcdow...@paloaltonetworks.com>To: Ryan Moats/Omaha/IBM@IBMUSCc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org>Subject:

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/11/2016 12:37:40 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/11/2016 12:37:40 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/11/2016 12:06:55 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/11/2016 11:30:07 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/10/2016 11:11:57 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/09/2016 10:46:41 AM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org>, "OpenStack

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall <jmcdow...@paloaltonetworks.com> wrote on 05/08/2016 07:34:52 PM: > From: John McDowall <jmcdow...@paloaltonetworks.com> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" <disc...@openvswitch.org> > Date: 05/08/2016 07:35

[openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

... Ryan Moats (regXboi on IRC, jayhawk87 on github) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [Neutron][DVR]

4/2015 03:44 PM > Subject: Re: [openstack-dev] [Neutron][DVR] > > > On 4 December 2015 at 05:56, Ryan Moats <rmo...@us.ibm.com> wrote: > > I pretty much agree with Oleg here - I'm not sure an additional tag > > for defects is needed. > > The idea of a DvrImpact in the

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Apologies to those who get this twice - I'm fighting with mail clients/servers this morning (and I'm pretty sure I'm losing) As a US person, I'm going to vote -1 on moving to 1600 UTC on Tuesdays - I already have too many other meetings stacked up in this slot... Ryan Moats (regXboi) Dina

Re: [openstack-dev] [Neutron][DVR]

into? I'm not yet for or against, I'm just trying to think what the commit messages are going to end up looking like... Ryan Moats (regXboi) Oleg Bondarev <obonda...@mirantis.com> wrote on 12/04/2015 02:44:58 AM: > From: Oleg Bondarev <obonda...@mirantis.com> > To: "OpenStack D

Re: [openstack-dev] [Neutron] Bug deputy process

I missed this the first time around, but I concur with the comments of the other deputies - the effort only took me about an hour or two a day and I think it's been rather helpful :) Ryan Moats (regXboi) __ OpenStack

[openstack-dev] [neutron] Ether pad on O(n)/Linear Execution Time/Hyper-Scale

utron or if it should be elsewhere (like user docs that go along with code that would implement [2] in oslo... Thoughts and comments are welcome, Ryan Moats (regXboi) [1] https://etherpad.openstack.org/p/hyper-scale [2] https:/

Re: [openstack-dev] [Neutron] Weekly DVR Meeting starting next week

Ditto Ryan (regXboi) Moats Carl Baldwin wrote on 11/02/2015 11:47:27 AM: > From: Carl Baldwin > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 11/02/2015 11:48 AM > Subject: Re:

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

(With apologies to the Who)... "Meet the new things, same as the old things" DVR - let's make it real folks :) Performance - I keep turning over rocks and finding things that just don't make sense to me... I suspect others will come a calling as we go...

[openstack-dev] [neutron] congrats to armax!

First, congratulations to armax on being elected PTL for Mitaka. Looking forward to Neutron improving over the next six months. Second thanks to everybody that voted in the election. Hopefully we had something close to 100% turnout, because that is an important responsibility of the population.

Re: [openstack-dev] [neutron][L3][QA] DVR job failure rate and maintainability

I couldn't have said it better, Sean. Ryan Moats "Sean M. Collins" <s...@coreitpro.com> wrote on 09/14/2015 05:01:03 PM: > From: "Sean M. Collins" <s...@coreitpro.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <

[openstack-dev] [neutron] PTL Candidancy

a large list of new items for the design summit [1], which we will work to pare down into items that can be delivered in Mitaka Thanks, Ryan Moats (IRC handle: regXboi) [1] https://etherpad.openstack.org/p/neutron-mitaka-designsummit

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

One thing came up during lunch was including unit and functional testing of dual stack in the check and gate queues - I was regaled over lunch with one operator's experiences in trying to run Neutron on a dual stack system. Ryan Moats (regXboi) Edgar Magana edgar.mag...@workday.com wrote on 08

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/19/2015 04:26 PM Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup On Wed, Aug 19, 2015 at 05:11:55PM EDT, Ryan Moats wrote: One thing came up during lunch was including unit and functional

[openstack-dev] [neutron][infra] - py34 tests, devstack/base trusty and how does the neutron check pipeline choose between them (oh my)...

if the selection of devstack-trusty for [1] is the bug, or the fact that devstack-trusty is missing pieces that bare-trusty has is the bug. Looking for help from knowledgeable people about how to go about getting this addressed. Thanks, Ryan Moats IRC: regXboi [1] http://logs.openstack.org/05

Re: [openstack-dev] [Openstack-operators] [Neutron][L3] [Large Deployments Team] Representing a networks connected by routers

I will be there for my lightning talk, and I think armax and kevin_benton will be there - it would be good to find some time for us to pow-wow, along with some teleconference so that carl_baldwin and mestery can join in... Ryan Moats (regXboi) Mike Dorman mdor...@godaddy.com wrote on 08/03/2015

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

If that's the case, then I'd say let's just solve this right way and create a new construct rather... Ryan Moats Kevin Benton blak...@gmail.com wrote on 07/28/2015 06:44:53 PM: From: Kevin Benton blak...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

Kevin, doesn't this in itself create technical debt on the nova side in the sense of what an instance attaches to? I agree that it looks like less technical debt than conditionally redefining a network, but without nova buy-in, it looks like a non-starter... Ryan Kevin Benton blak...@gmail.com

Re: [openstack-dev] [stable][neutron] dvr job for kilo?

+1 Kyle Mestery mest...@mestery.com wrote on 07/27/2015 08:16:07 AM [with a bit of cleanup]: On Mon, Jul 27, 2015 at 6:57 AM, Thierry Carrez thie...@openstack.org wrote: Ihar Hrachyshka wrote: I noticed that dvr job is now voting for all stable branches, and failing, because the branch

Re: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron

The alternative is to do what has been done with the neutron meeting itself - have it be held in two alternating time slots. Ryan Damon Wang damon.dev...@gmail.com wrote on 07/22/2015 12:08:03 PM: From: Damon Wang damon.dev...@gmail.com To: OpenStack Development Mailing List (not for usage

[openstack-dev] [neutron] new etherpad for Neutron instrumentation

to adoption by operators and would like (as we move forward) to invite operators in to provide their input... Thanks, Ryan Moats [1] https://etherpad.openstack.org/p/neutron-instrumentation__ OpenStack Development Mailing List

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

Gabriel Bezerra gabri...@lsd.ufcg.edu.br wrote on 03/10/2015 12:34:30 PM: Em 10.03.2015 14:24, Carl Baldwin escreveu: Neutron currently does not enforce the uniqueness, or non-overlap, of subnet cidrs within the address scope for a single tenant. For example, if a tenant chooses to use

[openstack-dev] [api][neutron] Re: Best API for generating subnets from pool

that might be ok. This would be my preferred approach of the two given. Ryan Moats [1] http://lists.openstack.org/pipermail/openstack-dev/2015-March/058538.html__ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [neutron] looking for status of an old wiki page work item

the author and the other contributors working on it will resume it for the next release. Salvatore [1] https://review.openstack.org/#/c/132661/ On 5 February 2015 at 22:52, Ryan Moats rmo...@us.ibm.com wrote: I've run into a set of use cases where it would really be useful to be able

[openstack-dev] [neutron] looking for status of an old wiki page work item

. So, I'm wondering if there is a blueprint that I missed when I went searching or if there are folks that would be interested in seeing along the lines of [1] getting implemented... Thanks in advance, Ryan Moats [1] https://wiki.openstack.org/wiki/Neutron/sharing-model-for-external-networks [2

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

+1 to that idea... Jay Pipes jaypi...@gmail.com wrote on 02/02/2015 04:35:36 PM: What about having a separate HTTP header that indicates the OpenStack Error Code, along with a generated URI for finding more information about the error? Something like: X-OpenStack-Error-Code: 1234

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

Sigh... hit send too soon and forgot to sign... +1 to that idea... Ryan Jay Pipes jaypi...@gmail.com wrote on 02/02/2015 04:35:36 PM: What about having a separate HTTP header that indicates the OpenStack Error Code, along with a generated URI for finding more information about the error?

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

, then I think we will find that we've solved the multi-master problem essentially for free. Ryan Moats Mike Bayer mba...@redhat.com wrote on 11/19/2014 12:05:35 PM: From: Mike Bayer mba...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Ian Wells ijw.ubu...@cack.org.uk wrote on 11/19/2014 02:33:40 PM: [snip] When you have a plugin that's decided to be synchronous, then there are cases where the DB lock is held for a technically indefinite period of time.  This is basically broken. A big +1 to this statement Ryan

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

isolation and related questions On Nov 19, 2014, at 1:49 PM, Ryan Moats rmo...@us.ibm.com wrote: I was waiting for this because I think I may have a slightly different (and outside of the box) view on how to approach a solution to this. Conceptually (at least in my mind) there isn't a whole

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

+1 Sumit Naiksatam sumitnaiksa...@gmail.com wrote on 08/08/2014 02:44:55 PM: From: Sumit Naiksatam sumitnaiksa...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/08/2014 02:45 PM Subject: Re: [openstack-dev]

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

. Ryan Moats Edgar Magana edgar.mag...@workday.com wrote on 08/07/2014 04:02:43 PM: From: Edgar Magana edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:03 PM Subject: Re: [openstack-dev] [Neutron

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

Edgar Magana edgar.mag...@workday.com wrote on 08/07/2014 04:37:39 PM: From: Edgar Magana edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:40 PM Subject: Re: [openstack-dev] [Neutron][policy]

Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward

Jay Pipes jaypi...@gmail.com wrote on 08/06/2014 01:04:41 PM: [snip] AFAICT, there is nothing that can be done with the GBP API that cannot be done with the low-level regular Neutron API. I'll take you up on that, Jay :) How exactly do I specify behavior between two collections of ports

Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward

Policy and the way forward Hi Ryan, On Wed, Aug 6, 2014 at 11:55 AM, Ryan Moats rmo...@us.ibm.com wrote: Jay Pipes jaypi...@gmail.com wrote on 08/06/2014 01:04:41 PM: [snip] AFAICT, there is nothing that can be done with the GBP API that cannot be done with the low-level regular

Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward

[snipping to save BW] Aaron Rosen aaronoro...@gmail.com wrote on 08/06/2014 03:26:24 PM: Note: I'm not going to use the pure group policy API as I have been a fan of the 2-group approach from day 1, I'm going to use the commands as stated in the patch set, and I'm going to assume (dangerous

Re: [openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy

Yes Henry Fourie louis.fou...@huawei.com wrote on 07/31/2014 12:32:23 PM: From: Henry Fourie louis.fou...@huawei.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Cc: Subrahmanyam Ongole song...@oneconvergence.com Date: 07/31/2014 12:33

[openstack-dev] [neutron] A request for sub-projects to post meeting summary emails to the ML

of an IRC meeting to the ML with a note of anything that was agreed in the meeting and include a link to the meeting minutes and transcript. Thanks, Ryan Moats (regXboi)___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

[openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy

to specify policy as something between two groups. Ryan Moats (regXboi) References: [1] http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-28-21.02.log.txt [2] https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit# [3] http://lists.openstack.org

[openstack-dev] Trying to make sense of allow_overlapping_ips in neutron

somebody lend me a hand and either (a) tell me I'm reading the code wrong or (b) explain why that choice was made? Thanks in advance, Ryan Moats rmo...@us.ibm.com___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi