Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 09/07/14 13:13, Miguel Angel Ajo Pelayo wrote:
> 
> +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
> ?

I think no. openstack-neutron includes executables, service files,
configuration, while python-neutron is to provide Python code.

> 
> 
> 
> 
> 
> ----- Original Message ----- 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
>>>>
>>
>>
>>>> 
_______________________________________________
>> 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/

iQEcBAEBCgAGBQJTvTDZAAoJEC5aWaUY1u57f+MIAJvL7TnUnhSFEVHHdQ8WIUla
kovBdxKpkElqinrMJqBTegLaHnGVcJT4LeivZzKh0LlX32vVR8AKD1ajQSsrx1NB
ng1mu12YHz0XlA5VLwmc/aV+hU2Ibj7j1qlEmI1cEfsYZwi1FyIBXTwlyYbKlge+
jdtmpOs8GyD+EqNhgwBJuyJglDr7/Y0KdI9ePCk/Hl2TLmy2bguxWCXSXF9Di1+5
d796/kOGGZsSVX1sbUOzdB7dAPiIdBukQndAw4EhnCZvqpqgBP1Vkgu5LahsI2Wz
XIknmfgUbYPjQzY72FCvOLuu9dYggkx6bXEHy5j3joj8VOq0aAdT4DuTRlYtd3U=
=RaNB
-----END PGP SIGNATURE-----