Open Stack

Sorry for jumping into this conversation late.

Indeed the default linuxbridge init scripts point to different files. I've
taken two approaches with my Puppet scripts: either replace the init script
with one that points to the ml2 file, or clobber the linuxbridge_conf.ini
file with ml2 settings. I apologize for not doing the right thing and
filing a bug. :/

I've just finished setting up an OVS-based Neutron cloud, and although this
wasn't a migration, I ran into similar issues that have been talked about
in this thread:

The "vlan 4095" point was very helpful! I was seeing the same thing and it
was nice to learn the reason behind it.

Additionally, like Robert, I was unable to get anything working until I
added the "bridge_mappings" setting.

And finally, when creating the "main" bridge that will "host" the trunk
interface, that bridge cannot have the trunk port set to type internal.
This seems logical, but it's easy for someone to make that mistake. For
example, let's say the trunk interface is eth0. The documentation says to
do this:

ovs-vsctl add-br br-eth0
ovs-vscl add-port br-eth0 eth0

That sets everything up correctly. But let's say someone (ie me) says
"whatever, I'll just call the bridge eth0":

ovs-vsctl add-br eth0

This will automatically add the eth0 interface to the eth0 bridge, but of
type "internal". There are, of course, ovs commands to change that, but I
haven't had a chance to look them up -- I just did the br-eth0 route and
all was good.


On Mon, Jul 21, 2014 at 10:16 AM, Mathieu Gagné <mgagne at iweb.com> wrote:

> On 2014-07-21 12:00 PM, Jonathan Proulx wrote:
>
>> Coming back to this after a break...
>>
>> On my system (Ubuntu 12.04 Icehouse upgraded from havana) the agent
>> startup is clearly looking at the ml2_conf.ini and not the
>> openvswitch.ini:
>>
>> # grep exec /etc/init/neutron-plugin-openvswitch-agent.conf
>> exec start-stop-daemon --start --chuid neutron --exec
>> /usr/bin/neutron-openvswitch-agent --
>> --config-file=/etc/neutron/neutron.conf
>> --config-file=/etc/neutron/plugins/ml2/ml2_conf.ini
>> --log-file=/var/log/neutron/openvswitch-agent.log
>>
>>
> omg... Linux Bridge agent upstart config file differs from the
> Openvswitch's one.
>
> Linuxbridge:
> exec start-stop-daemon --start --chuid neutron --exec
> /usr/bin/neutron-linuxbridge-agent -- --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini
> --log-file=/var/log/neutron/linuxbridge-agent.log
>
> Openvswitch:
>
> exec start-stop-daemon --start --chuid neutron --exec
> /usr/bin/neutron-openvswitch-agent -- --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/plugins/ml2/ml2_conf.ini
> --log-file=/var/log/neutron/openvswitch-agent.log
>
> I don't know what to say...
>
> --
> Mathieu
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140723/7e6d12bb/attachment.html>