<div dir="ltr">Hi Mathieu,<div><br></div><div>Good questions and I've been trying to think of some sort of answers that are even slightly helpful. Unfortunately when I test these things in lab/sandbox environments, I tend to do things that end up being more like duct tape than an acceptable solution for wide adoption.</div>
<div><br></div><div>I think Puppet should attempt to do what would be the result of any fixed packaging bugs. If linuxbridge follows suit with OVS, then create a symlink. And also make sure the init script is correct. As Jon says, it really doesn't matter what the ini files are called as long as they are specified in the init script, but consistency is always a good thing.</div>
<div><br></div><div>Regarding the contents of the ini files, it seems that there are pre-ML2 options that should be specified in various config files in order to get things working. I think just making sure that all correct settings are specified in an ini file (regardless of what ini file, as long as it's in the init script) should be good.</div>
<div><br></div><div>However, I think we're all in a situation where we don't even know what the right set of settings should be...</div><div><br></div><div>I apologize, but that probably doesn't help at all. :/</div>
<div class="gmail_extra">
<br><div class="gmail_quote">On Wed, Jul 23, 2014 at 10:43 AM, Mathieu Gagné <span dir="ltr"><<a href="mailto:mgagne@iweb.com" target="_blank">mgagne@iweb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Joe,<br>
<br>
What do you suggest doing for someone using Puppet?<br>
<br>
Should we create a symlink from ovs_neutron_plugin.ini to ml2_conf.ini for people with "old" packages?<br>
<br>
What about linuxbridge mechanism? Should we:<br>
- create a symlink from linuxbridge_conf.ini to ml2_conf.ini like OVS does and<br>
- open a bug report to get package fixed so agent reads ml2_conf.ini?<br>
<br>
<br>
This however raises the question: what if people are:<br>
- Still using the old Linuxbridge plugin in Icehouse and update the package with the proposed fix? I suppose the agent will stop working from lack of configs in ml2_conf.ini.<br>
- using OVS and upgrading from Havana to Icehouse while using the old OVS plugin. I suppose the agent will stop working from lack of configs in ml2_conf.ini.<br>
<br>
IMO, nothing of this mess would have happened if people put the configs in the right file in the first place but here we are. =)<br>
<br>
Mathieu<div><div><br>
<br>
On 2014-07-23 12:30 PM, Joe Topjian wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Sorry for jumping into this conversation late.<br>
<br>
Indeed the default linuxbridge init scripts point to different files.<br>
I've taken two approaches with my Puppet scripts: either replace the<br>
init script with one that points to the ml2 file, or clobber the<br>
linuxbridge_conf.ini file with ml2 settings. I apologize for not doing<br>
the right thing and filing a bug. :/<br>
<br>
I've just finished setting up an OVS-based Neutron cloud, and although<br>
this wasn't a migration, I ran into similar issues that have been talked<br>
about in this thread:<br>
<br>
The "vlan 4095" point was very helpful! I was seeing the same thing and<br>
it was nice to learn the reason behind it.<br>
<br>
Additionally, like Robert, I was unable to get anything working until I<br>
added the "bridge_mappings" setting.<br>
<br>
And finally, when creating the "main" bridge that will "host" the trunk<br>
interface, that bridge cannot have the trunk port set to type internal.<br>
This seems logical, but it's easy for someone to make that mistake. For<br>
example, let's say the trunk interface is eth0. The documentation says<br>
to do this:<br>
<br>
ovs-vsctl add-br br-eth0<br>
ovs-vscl add-port br-eth0 eth0<br>
<br>
That sets everything up correctly. But let's say someone (ie me) says<br>
"whatever, I'll just call the bridge eth0":<br>
<br>
ovs-vsctl add-br eth0<br>
<br>
This will automatically add the eth0 interface to the eth0 bridge, but<br>
of type "internal". There are, of course, ovs commands to change that,<br>
but I haven't had a chance to look them up -- I just did the br-eth0<br>
route and all was good.<br>
<br>
<br>
On Mon, Jul 21, 2014 at 10:16 AM, Mathieu Gagné <<a href="mailto:mgagne@iweb.com" target="_blank">mgagne@iweb.com</a><br></div></div><div>
<mailto:<a href="mailto:mgagne@iweb.com" target="_blank">mgagne@iweb.com</a>>> wrote:<br>
<br>
On 2014-07-21 12:00 PM, Jonathan Proulx wrote:<br>
<br>
Coming back to this after a break...<br>
<br>
On my system (Ubuntu 12.04 Icehouse upgraded from havana) the agent<br>
startup is clearly looking at the ml2_conf.ini and not the<br>
openvswitch.ini:<br>
<br></div>
# grep exec /etc/init/neutron-plugin-__<u></u>openvswitch-agent.conf<div><br>
exec start-stop-daemon --start --chuid neutron --exec<br></div>
/usr/bin/neutron-openvswitch-_<u></u>_agent --<br>
--config-file=/etc/neutron/__<u></u>neutron.conf<br>
--config-file=/etc/neutron/__<u></u>plugins/ml2/ml2_conf.ini<br>
--log-file=/var/log/neutron/__<u></u>openvswitch-agent.log<div><br>
<br>
<br>
omg... Linux Bridge agent upstart config file differs from the<br>
Openvswitch's one.<br>
<br>
Linuxbridge:<br>
exec start-stop-daemon --start --chuid neutron --exec<br></div>
/usr/bin/neutron-linuxbridge-_<u></u>_agent --<br>
--config-file=/etc/neutron/__<u></u>neutron.conf<br>
--config-file=/etc/neutron/__<u></u>plugins/linuxbridge/__<u></u>linuxbridge_conf.ini<br>
--log-file=/var/log/neutron/__<u></u>linuxbridge-agent.log<div><br>
<br>
Openvswitch:<br>
<br>
exec start-stop-daemon --start --chuid neutron --exec<br></div>
/usr/bin/neutron-openvswitch-_<u></u>_agent --<br>
--config-file=/etc/neutron/__<u></u>neutron.conf<br>
--config-file=/etc/neutron/__<u></u>plugins/ml2/ml2_conf.ini<br>
--log-file=/var/log/neutron/__<u></u>openvswitch-agent.log<div><br>
<br>
I don't know what to say...<br>
<br>
--<br>
Mathieu<br>
<br>
<br></div>
______________________________<u></u>___________________<br>
OpenStack-operators mailing list<br>
OpenStack-operators@lists.__<a href="http://openstack.org" target="_blank">op<u></u>enstack.org</a><br>
<mailto:<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@<u></u>lists.openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-operators" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-operators</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-operators</a>><br>
<br>
<br><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<br>
-- <br>
Mathieu<br>
</font></span></blockquote></div><br></div></div>