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 release, just make sure it's there if an *aas is installed.
Tox does those egg games because putting neutron in requirements.txt causes other problems. When kilo gets a stable branch, that tox.ini will need to point at stable/kilo instead of master. But that shouldn't affect packaging. Ultimately, I'm hoping we can split out the library code, to make things saner: https://review.openstack.org/#/c/154736/ Thanks, doug > On Feb 16, 2015, at 8:13 AM, James Page <james.p...@ubuntu.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > 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 challenge for us downstream in distributions, > as we can't really pull in a full source egg of neutron from > git.openstack.org; we have the code base for neutron core available > (python-neutron), but that does not appear to be enough (see ). > > I would appreciate if dev's working in this area could a) review the > bug and the problems we are seeing a b) think about how this can work > for distributions - I'm happy to create a new 'neutron-testing' type > package from the neutron codebase to support this stuff, but right now > I'm a bit unclear on exactly what its needs to contain! > > Cheers > > James > > >  https://bugs.launchpad.net/neutron/+bug/1422376 > > - -- > James Page > Ubuntu and Debian Developer > james.p...@ubuntu.com > jamesp...@debian.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQIcBAEBCAAGBQJU4gj5AAoJEL/srsug59jD5agP/1NFgrLQjD7+d0OrxSByD+b0 > DEwlbSwFGvV6sIbjzP8/9ibUmxnCOcwW9Enn4+Ukp4KuhuWKuiEZYdOARkuEupaz > IyDw3F9NzytnER2s+sn2+tddQloTjCk0vzk+e5uH19ovwoLBmFOd/g5d+yNYt/SB > ozzA3S4WTyG8vws2AOBcubJkg1wYzyUSGATceBqYLFMa7e7GuazRR/XohOwa7iux > T1+4t72juhXUiFiPn4GD2aWjl30Eer0+juHdlje6EHtSRnODJXnYeEHIw/ndmTCy > gEmMZ3c9fUoJC51HBeOSjX+Mg5Hq/AaGLLQHU+shklg6pgXKZ1ZKFAYD5rjWrXB2 > jxPM0vFcJEh2yfMHTsgbgP6AnYF5g7/36izTdJsXWDgEJoE7Zt2J+NX5+SLTihtt > GbWIUh5ZstZXBD85u4o8iB+whhpzZd7rE/GRK2Ax/kY8WnB8xeiU5wA5AQN6nTMr > XPT/ObXsXKnyrLgn4KkRZymEeDO1yaaVrtGtLxF2Dap2CpH8so7hLQw/3KYxDsTP > 8dptOS4EzVm+jZPdAHMHIqsyA2wnRfyauPAyYDEeVioCUkijinrt61x62OM5s8+X > MbAOyjGGOPVXq0tFChbB9ZdSkMDNvj98sv1xhZ1yHmoKvJ56EM1drh7HhcJWD6/v > dv9uUmY4DhVlvjYKwPgY > =C4vr > -----END PGP SIGNATURE----- > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev