Comment 1 for bug 1314751

I'm not convinced this is actually a bug. In the cookbooks on ubuntu we template out the file

"/etc/default/neutron-server"

here: https://github.com/stackforge/cookbook-openstack-network/blob/master/templates/default/neutron-server.erb

When we are using ml2 as the core_plugin, this ends up containing:

NEUTRON_PLUGIN_CONFIG=/etc/neutron/plugins/ml2/ml2_conf.ini

And so this determines the config file that gets loaded along with the main neutron.conf:

/usr/bin/python /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file /var/log/neutron/server.log --config-file /etc/neutron/plugins/ml2/ml2_conf.ini

If you change the value in /etc/default/neutron-server to point to the monolithic ovs plugin config file like this:

NEUTRON_PLUGIN_CONFIG=/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

that is what gets loaded:

/usr/bin/python /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file /var/log/neutron/server.log --config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

Simples!

The real problem here is that we need to port all of the ovs specific setting out of the monolithic ovs plugin config file, and in to the ml2 configuration file under an [ovs] section.