Re: [openstack-dev] [Neutron] - Location for common third-party libs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/07/14 20:42, Kevin Benton wrote: I have filed a bug in Red Hat[1], however I'm not sure if it's in the right place. Ihar, can you verify that it's correct or move it to the appropriate location? Thank you, it's correct. Let's follow up in bugzilla. 1. https://bugzilla.redhat.com/show_bug.cgi?id=1120332 On Wed, Jul 9, 2014 at 3:29 AM, Ihar Hrachyshka ihrac...@redhat.com mailto:ihrac...@redhat.com wrote: 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 ihrac...@redhat.com mailto:ihrac...@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@lists.openstack.org mailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org mailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org mailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@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/ iQEcBAEBCgAGBQJTx9RmAAoJEC5aWaUY1u57Fc4H/i011lCJWfwO5cY6ikR94rol HccxdZIcIkXIPDwBHkOgvqWIK6tYYMsAaVNaG35VmsgKpbQxKb2hbsJosuX2gaww +tuXH8QdvjCdQGzEbqvCsKvgUInYfF/v5Pi2tgkhK5elb+QXtiJHMgHnLzsNmD2I cKFRRbkJHS2seQFYiNW62bGYsvn7lEwM9saEWiWWbdVqRreqcqG0Bpp7mQX2vsM9 4t3t+wGCO2BlNn6znQE/njj3op88N5tLjrZFVyJOy+GQbAV11qAXXzvziA5WBKvg qY5T6t9P07D9LPBpvLbM7asyoirpgFke2ozR+pXu0tU8U/uhPOtistloWXQ2tMM= =nxTq -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
I have filed a bug in Red Hat[1], however I'm not sure if it's in the right place. Ihar, can you verify that it's correct or move it to the appropriate location? 1. https://bugzilla.redhat.com/show_bug.cgi?id=1120332 On Wed, Jul 9, 2014 at 3:29 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: -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 ihrac...@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
+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 ihrac...@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
-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 ihrac...@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@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- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
I don't think that a common area as being proposed is a silver bullet for solving packaging issues, such as this one. Knowing that the right source tree bits are dropped onto the file system is not enough to guarantee that the end-to-end solution will work on a specific distro. Other issues may arise after configuration and execution. IMO, this is a bug in the packages spec, and should be taken care of during the packaging implementation, testing and validation. That said, I think the right approach is to provide a 'python-neutron' package that installs the entire source tree; the specific plugin package can then take care of the specifics, like config files. Armando On 17 June 2014 06:43, Shiv Haris sha...@brocade.com wrote: Right Armando. Brocade’s mech driver problem is due to NETCONF templates - would also prefer to see a common area for such templates – not just common code. Sort of like: common/brocade/templates common/bigswitch/* -Shiv From: Armando M. arma...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] - Location for common third-party libs? I believe the Brocade's mech driver might have the same problem. That said, if the content of the rpm that installs the BigSwitch plugin is just the sub-tree for bigswitch (plus the config files, perhaps), you might get away with this issue by just installing the bigswitch-plugin package. I assume you tried that and didn't work? I was unable to find the rpm specs for CentOS to confirm. A. On 17 June 2014 00:02, Kevin Benton blak...@gmail.com 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? Thanks -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
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? Thanks, Kevin Benton On Mon, Jun 16, 2014 at 3:37 PM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTn3G6AAoJEC5aWaUY1u573y4IAOlglKdT8nACA4MqOKt6YPEm 7+8yxLyIfUIJx/B61MvIA94m2j2O7uuUWbqyx+kGwSQQYXaXrHwnfgf43OSPktSf GZsms/iRCxe5/rKS+WPn51UNj6aauvR5O7SHAu4kpGS8Y25mb7nVcIAgtXzE3IwR rsEff1u8UAZ8uFPG1ZgerN5X2n2pn1R7xcSXB2g1rlbqbRdwtS2toHL7iSSwwJgq 6GH5iC+GmV1iMb1c7f0ZQvJm8jQYF2vBhl7efEXUnDEx6DQlpqDE/QI9tIwrwVkb nbwz0FnVCtdiN5rGdmJZ/NW/Uldx/seVmjzlD/u25GO8mKacm0WEwc8VCIpbsYk= =V+7m -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] - Location for common third-party libs?
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? Thanks -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
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? Thanks ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I think you would be best to talk to packagers. Rather than trying to move it around, perhaps asking the packagers why they are packaging it as they are might be a good place to begin. Thanks Kevin, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
I think there's is no suitable place at the moment in the source code tree. common and plugin specific indeed are semantically a bit at odds too! I am considering moving all library code for the vmware plugins outside of the source code tree, into their own package, maintained separately and independently from neutron release cycles. I'm not sure if and when that will happen, but I think it will beneficial to both the community and the vmware team. That's something you might consider for your libraries too, if you can't sort that with packagers as Anita said. A situation like this will however put distros which package plugins in distinct packages in a tight spot, as it would look rather weird to have the bigswitch plugin as a dependency for the ml2 plugin (I don't think drivers are packages separately) Salvatore On 17 June 2014 00:10, Anita Kuno ante...@anteaya.info 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? Thanks ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I think you would be best to talk to packagers. Rather than trying to move it around, perhaps asking the packagers why they are packaging it as they are might be a good place to begin. Thanks Kevin, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTn3G6AAoJEC5aWaUY1u573y4IAOlglKdT8nACA4MqOKt6YPEm 7+8yxLyIfUIJx/B61MvIA94m2j2O7uuUWbqyx+kGwSQQYXaXrHwnfgf43OSPktSf GZsms/iRCxe5/rKS+WPn51UNj6aauvR5O7SHAu4kpGS8Y25mb7nVcIAgtXzE3IwR rsEff1u8UAZ8uFPG1ZgerN5X2n2pn1R7xcSXB2g1rlbqbRdwtS2toHL7iSSwwJgq 6GH5iC+GmV1iMb1c7f0ZQvJm8jQYF2vBhl7efEXUnDEx6DQlpqDE/QI9tIwrwVkb nbwz0FnVCtdiN5rGdmJZ/NW/Uldx/seVmjzlD/u25GO8mKacm0WEwc8VCIpbsYk= =V+7m -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
Hi, It doesn't make sense to move the Big Switch ML2 driver into the Big Switch Plugin. This isn't how the other ML2 drivers are handled and it doesn't really solve the problem since someone installing the ML2 package couldn't use one of the ML2 drivers. I will report a bug; however, it won't be a high priority and I suspect other packagers could end up doing the same thing. That's why I was looking for an alternative approach. -- Kevin Benton On Mon, Jun 16, 2014 at 3:37 PM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTn3G6AAoJEC5aWaUY1u573y4IAOlglKdT8nACA4MqOKt6YPEm 7+8yxLyIfUIJx/B61MvIA94m2j2O7uuUWbqyx+kGwSQQYXaXrHwnfgf43OSPktSf GZsms/iRCxe5/rKS+WPn51UNj6aauvR5O7SHAu4kpGS8Y25mb7nVcIAgtXzE3IwR rsEff1u8UAZ8uFPG1ZgerN5X2n2pn1R7xcSXB2g1rlbqbRdwtS2toHL7iSSwwJgq 6GH5iC+GmV1iMb1c7f0ZQvJm8jQYF2vBhl7efEXUnDEx6DQlpqDE/QI9tIwrwVkb nbwz0FnVCtdiN5rGdmJZ/NW/Uldx/seVmjzlD/u25GO8mKacm0WEwc8VCIpbsYk= =V+7m -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
I believe the Brocade's mech driver might have the same problem. That said, if the content of the rpm that installs the BigSwitch plugin is just the sub-tree for bigswitch (plus the config files, perhaps), you might get away with this issue by just installing the bigswitch-plugin package. I assume you tried that and didn't work? I was unable to find the rpm specs for CentOS to confirm. A. On 17 June 2014 00:02, Kevin Benton blak...@gmail.com 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? Thanks -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
This approach would work but my only concern is then getting an external package added as a dependency to Neutron. Or would you just forgo that entirely and mock out all of the library calls? -- Kevin Benton On Mon, Jun 16, 2014 at 3:29 PM, Salvatore Orlando sorla...@nicira.com wrote: I think there's is no suitable place at the moment in the source code tree. common and plugin specific indeed are semantically a bit at odds too! I am considering moving all library code for the vmware plugins outside of the source code tree, into their own package, maintained separately and independently from neutron release cycles. I'm not sure if and when that will happen, but I think it will beneficial to both the community and the vmware team. That's something you might consider for your libraries too, if you can't sort that with packagers as Anita said. A situation like this will however put distros which package plugins in distinct packages in a tight spot, as it would look rather weird to have the bigswitch plugin as a dependency for the ml2 plugin (I don't think drivers are packages separately) Salvatore On 17 June 2014 00:10, Anita Kuno ante...@anteaya.info 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? Thanks ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I think you would be best to talk to packagers. Rather than trying to move it around, perhaps asking the packagers why they are packaging it as they are might be a good place to begin. Thanks Kevin, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
That could be a possible workaround. In this particular deployment the nodes no longer had access to the Internet though to install additional packages. -- Kevin Benton On Mon, Jun 16, 2014 at 3:59 PM, Armando M. arma...@gmail.com wrote: I believe the Brocade's mech driver might have the same problem. That said, if the content of the rpm that installs the BigSwitch plugin is just the sub-tree for bigswitch (plus the config files, perhaps), you might get away with this issue by just installing the bigswitch-plugin package. I assume you tried that and didn't work? I was unable to find the rpm specs for CentOS to confirm. A. On 17 June 2014 00:02, Kevin Benton blak...@gmail.com 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? Thanks -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] - Location for common third-party libs?
Right Armando. Brocade’s mech driver problem is due to NETCONF templates - would also prefer to see a common area for such templates – not just common code. Sort of like: common/brocade/templates common/bigswitch/* -Shiv From: Armando M. arma...@gmail.commailto:arma...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] - Location for common third-party libs? I believe the Brocade's mech driver might have the same problem. That said, if the content of the rpm that installs the BigSwitch plugin is just the sub-tree for bigswitch (plus the config files, perhaps), you might get away with this issue by just installing the bigswitch-plugin package. I assume you tried that and didn't work? I was unable to find the rpm specs for CentOS to confirm. A. On 17 June 2014 00:02, Kevin Benton blak...@gmail.commailto:blak...@gmail.com 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? Thanks -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
