[Openstack-operators] ovs->ml2 migration issues during icehouse upgrade
Jonathan Proulx
jon at jonproulx.com
Thu Jul 24 14:58:28 UTC 2014
On Thu, Jul 24, 2014 at 1:26 AM, Robert van Leeuwen
<Robert.vanLeeuwen at spilgames.com> wrote:
> I think it should (have) point to /etc/neutron/plugin.ini.
> That file should symlink to either the old or new file just like in the docs here:
>
> http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html
Which ini file is active is a function of the packaging so it's upto
the RPM and DEB folks notOpenStack upstream. teh
/etc/neutron/plugin.ini abstraction is the RPM way, which I personally
like a bit better than the DEB way.
What IU have discovered is is since all teh ini files specified on the
lauch command line are sourced in teh same way it doesn't make any
technical different if it's in /etc/neutron/plugin.ini
/etc/neutron/plugins/ml2/ml2.ini or even /etc/neutron/neutron.conf
(well except that breaking it into some different files means
different service can start with different config values, can't think
if that's actually useful now but it's good abstraction)
> Also is there a way to actually know for sure your client is actually doing ml2 stuff?
> I updated the database and it works so I guess it does but I do not really see it on the client...
If started with debug=true, on restart the service will log all the
config settings it has read, for example:
2014-07-10 14:01:09.385 20138 DEBUG
neutron.plugins.openvswitch.agent.ovs_neutron_agent [-]
===================
=============================================================
log_opt_values /usr/lib/python2.7/dist-packages/o
slo/config/cfg.py:1932
2014-07-10 14:01:09.386 20138 DEBUG
neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] allow_bulk
= True log_opt_values
/usr/lib/python2.7/dist-packages/oslo/config/cfg.py:1941
2014-07-10 14:01:09.386 20138 DEBUG
neutron.plugins.openvswitch.agent.ovs_neutron_agent [-]
allow_overlapping_i
ps = False log_opt_values
/usr/lib/python2.7/dist-packages/oslo/config/cfg.py:1941
and so on for all sorts of options, grep that log for 'core_plugin'
and you'll see what you're using:
2014-07-10 14:01:09.390 20138 DEBUG
neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] core_plugin
= ml2 log_opt_values
/usr/lib/python2.7/dist-packages/oslo/config/cfg.py:1941
It's still quite a mess. Took me an afternoon to understand and test
upgrade for all other OpenStack components, going on 2 weeks of more
than full days just trying to get Neutron to go again and I'm still
not all the way there.
-Jon
More information about the OpenStack-operators
mailing list