Open Stack

+1

Anyway, we would need to have caution on how the new single-package
would provide the old ones to handle the upgrade from split to single,
and also, back compatibility with the deployment tools.

Anyway, wouldn't it be openstack-neutron instead of python-neutron ?





----- Original Message -----
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Reviving the old thread.
> 
> On 17/06/14 11:23, Kevin Benton wrote:
> > Hi Ihar,
> > 
> > What is the reason to breakup neutron into so many packages? A
> > quick disk usage stat shows the plugins directory is currently
> > 3.4M. Is that considered to be too much space for a package, or was
> > it for another reason?
> 
> I think the reasoning was that we don't want to pollute systems with
> unneeded files, and it seems to be easily achievable by splitting
> files into separate packages. It turned out now it's not that easy now
> that we have dependencies between ml2 mechanisms and separate plugins.
> 
> So I would be in favor of merging plugin packages back into
> python-neutron package. AFAIK there is still no bug for that in Red
> Hat Bugzilla, so please report one.
> 
> > 
> > Thanks, Kevin Benton
> > 
> > 
> > On Mon, Jun 16, 2014 at 3:37 PM, Ihar Hrachyshka
> > <ihrachys at redhat.com> wrote:
> > 
> > On 17/06/14 00:10, Anita Kuno wrote:
> >>>> On 06/16/2014 06:02 PM, Kevin Benton wrote:
> >>>>> Hello,
> >>>>> 
> >>>>> In the Big Switch ML2 driver, we rely on quite a bit of
> >>>>> code from the Big Switch plugin. This works fine for
> >>>>> distributions that include the entire neutron code base.
> >>>>> However, some break apart the neutron code base into
> >>>>> separate packages. For example, in CentOS I can't use the
> >>>>> Big Switch ML2 driver with just ML2 installed because the
> >>>>> Big Switch plugin directory is gone.
> >>>>> 
> >>>>> Is there somewhere where we can put common third party code
> >>>>> that will be safe from removal during packaging?
> >>>>> 
> > 
> > Hi,
> > 
> > I'm a neutron packager for redhat based distros.
> > 
> > AFAIK the main reason is to avoid installing lots of plugins to
> > systems that are not going to use them. No one really spent too
> > much time going file by file and determining internal
> > interdependencies.
> > 
> > In your case, I would move those Brocade specific ML2 files to
> > Brocade plugin package. I would suggest to report the bug in Red
> > Hat bugzilla. I think this won't get the highest priority, but once
> > packagers will have spare cycles, this can be fixed.
> > 
> > Cheers, /Ihar
> >> 
> >> _______________________________________________ OpenStack-dev
> >> mailing list OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >> 
> > 
> > 
> > 
> > 
> > _______________________________________________ OpenStack-dev
> > mailing list OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQEcBAEBCgAGBQJTvRmeAAoJEC5aWaUY1u57OSoIALVFA1a0CrIrUk/vc28I7245
> P3xe2WjV86txu71vtOVh0uSzh7oaGHkFOy1fpDDPp4httsALQepza8YziR2MsQHp
> 8fotY/fOvR2MRLNNvR+ekE+2n8U+pZW5vRchfOo3xKBGNeHs30Is3ZZHLyF6I7+T
> TrSR1qcHhkWgUF6HB6IcnRGHlNjhXJt1RBAjLVhbc4FuQAqy41ZxtFpi1QfIsgIl
> 7CmBJeZu+nTap+XvXqBqQslUbGdSeodbVh6uNMso6OP+P+3hKAwgXBhGD2Mc7Hed
> TMeKtY8BH5k1LAsadkMXgRm0L9f+vBPHeB5rzQgyLDBD6UpwH9bWryaDoDEJFYE=
> =M8GI
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>