Re: [openstack-dev] Use of egg snapshots of neutron code in neutron-*aas projects/distributing openstack

2015-02-17 Thread Doug Wiegley
There's no need for additional neutron packaging. The real trick is that the neutron-*aas packages need to have a package dependency of neutron, and whichever release of openstack they're all cut with, they just have to match. Put another way, use your existing neutron package from the same

Re: [openstack-dev] Use of egg snapshots of neutron code in neutron-*aas projects/distributing openstack

2015-02-17 Thread Armando M.
I also failed to understand the issue, and I commented on the bug report, where it's probably best to continue this conversation. Thanks, Armando On 16 February 2015 at 07:54, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2015 04:13 PM,

Re: [openstack-dev] Use of egg snapshots of neutron code in neutron-*aas projects/distributing openstack

2015-02-16 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2015 04:13 PM, James Page wrote: Hi Folks The split-out drivers for vpn/fw/lb as-a-service all make use of a generated egg of the neutron git repository as part of their unit test suite dependencies. This presents a bit of a

Re: [openstack-dev] Use of egg snapshots of neutron code in neutron-*aas projects/distributing openstack

2015-02-16 Thread Gary Kotton
Hi, The same issue is the for the backe end drivers. I think that they always need to be aligned with the master branch. When we cut stable all of the aaS and drivers also need to be cut. This was one of the pain points that we brought up with the split and the consensus was: we¹ll deal with it