Open Stack

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. <armamig at 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 <blak111 at 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 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
>
>


-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140616/8bcd8ead/attachment.html>