-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
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:
+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
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
-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
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
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
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.
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
-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
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
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
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
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
] [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
15 matches
Mail list logo
