Re: [openstack-dev] [Neutron] Edge-VPN and Edge-Id

2014-11-29 Thread Ian Wells
On 27 November 2014 at 12:11, Mohammad Hanif wrote: > Folks, > > Recently, as part of the L2 gateway thread, there was some discussion on > BGP/MPLS/Edge VPN and how to bridge any overlay networks to the neutron > network. Just to update everyone in the community, Ian and I have > separately s

Re: [openstack-dev] [Ironic] Do we need an IntrospectionInterface?

2014-11-29 Thread Ramakrishnan G
+1 for a separate interface. On Fri, Nov 28, 2014 at 7:20 PM, Lucas Alvares Gomes wrote: > Hi, > > Thanks for putting it up Dmitry. I think the idea is fine too, I > understand that people may want to use in-band discovery for drivers like > iLO or DRAC and having those on a separated interface

Re: [openstack-dev] sqlalchemy-migrate call for reviews

2014-11-29 Thread Davanum Srinivas
Looks like there is a review in the queue - https://review.openstack.org/#/c/111485/ -- dims On Sat, Nov 29, 2014 at 6:28 PM, Jeremy Stanley wrote: > To anyone who reviews sqlalchemy-migrate changes, there are people > talking to themselves on GitHub about long-overdue bug fixes because > the Ge

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-11-29 Thread Andrew Woodward
I think it's necessary to start a working group for plugins and meet by weekly until issues like these are flushed out of the design ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

[openstack-dev] sqlalchemy-migrate call for reviews

2014-11-29 Thread Jeremy Stanley
To anyone who reviews sqlalchemy-migrate changes, there are people talking to themselves on GitHub about long-overdue bug fixes because the Gerrit review queue for it is sluggish and they apparently don't realize the SQLAM reviewers don't look at Google Code issues[1] and GitHub pull request commen

[openstack-dev] [all][races][rally] Better way to work on fixing races in gates with Rally

2014-11-29 Thread Boris Pavlovic
Hi guys, It's not a big secret that working on "races" especially in OpenStack gates is quite complicated task. Current workflow: 1) Some tempest test run fails 2) Build rules for elastic-recheck & report bug 3) Recheck specific bug XXX 4) Collect stats 5) Attempt to fix BUG, believe that it fix

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-29 Thread Duncan Thomas
Cinder does not expose an API for this, and should not be doing so - such an API is a security risk and of little benefit to most deployments in doing so. On 28 November 2014 at 18:57, Pradip Mukhopadhyay wrote: > Thanks Qiming & Pavlo. We had looked into the v2 of Cinder API listings: > http://