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 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 [0]).
 
 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
 
 
 [0] 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


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, 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 challenge for us downstream in
  distributions,

 I am packaging neutron for RDO, but I fail to understand your issue.

  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 [0]).

 Don't you ship egg files with python-neutron package? I think this
 should be enough to get access to entry points.

 
  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
 
 
  [0] https://bugs.launchpad.net/neutron/+bug/1422376
 
 
 
 __
 
 
 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
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iQEcBAEBAgAGBQJU4hLIAAoJEC5aWaUY1u57+QEH/1ZaBmuEpIHiW1/67Lh452PU
 o2dXy3fy23fns/9GUHbXn6ASRPi5usEqe4Qa+Z0jaVnipIQcdjvGZg8RET2KQsyo
 RsmLJlOJHA2USJP62PvbkgZ5bmIlFSIi0vgNs75904tGp+UqGkpW4VZ/KTYyzVL2
 kpBaMfJxHdjmEnPAdfk14u5kHkblavGqQO7plmjCRncFkUy63m/qWQ2zjQbpUxCZ
 wZJ1FTNqA16mo4ThFzdn/br5Mqeopfkcwht7EQV/cCYz6b9Y0oU4qXmL5qy/k8Xz
 yyU9hLagPrffLf0hJWdf3Zt0K3FqYDND1GJRvjgGvKSri4ylRt1zG07RG1ZdiWg=
 =QffD
 -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


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 challenge for us downstream in
 distributions,

I am packaging neutron for RDO, but I fail to understand your issue.

 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 [0]).

Don't you ship egg files with python-neutron package? I think this
should be enough to get access to entry points.

 
 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
 
 
 [0] https://bugs.launchpad.net/neutron/+bug/1422376
 
 
 __

 
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
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJU4hLIAAoJEC5aWaUY1u57+QEH/1ZaBmuEpIHiW1/67Lh452PU
o2dXy3fy23fns/9GUHbXn6ASRPi5usEqe4Qa+Z0jaVnipIQcdjvGZg8RET2KQsyo
RsmLJlOJHA2USJP62PvbkgZ5bmIlFSIi0vgNs75904tGp+UqGkpW4VZ/KTYyzVL2
kpBaMfJxHdjmEnPAdfk14u5kHkblavGqQO7plmjCRncFkUy63m/qWQ2zjQbpUxCZ
wZJ1FTNqA16mo4ThFzdn/br5Mqeopfkcwht7EQV/cCYz6b9Y0oU4qXmL5qy/k8Xz
yyU9hLagPrffLf0hJWdf3Zt0K3FqYDND1GJRvjgGvKSri4ylRt1zG07RG1ZdiWg=
=QffD
-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


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 when we get to the bridge.
Thanks
Gary

On 2/16/15, 5:13 PM, 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 [0]).

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


[0] 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