Comment 3 for bug 1738123

@gnuoy: We just realized that even hacking in this update to the /etc/neutron/plugins/ml2/openvswitch_agent.ini file, it fixes ovs agent, but does not fix neutron-l3-agent.

Can you add code into the charm-neutron-gateway project to handle appending --config-file=/etc/neutron/plugins/ml2/openvswitch_agent.ini if plugin in ['OVS', 'OVS_ODL'] into the service init file?

Note the startup command differences:

neutron 367937 8.1 0.0 569448 418396 ? Ss Jan03 104:41 /usr/bin/python /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/l3_agent.ini --config-file=/etc/neutron/fwaas_driver.ini --log-file=/var/log/neutron/neutron-l3-agent.log

neutron 883782 22.8 0.0 511724 355836 ? Ss 2017 2312:15 /usr/bin/python /usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/openvswitch_agent.ini --log-file=/var/log/neutron/neutron-openvswitch-agent.log

The neutron-l3-agent doesn't pull in the OVS configs, but DOES use ovsdb connections directly within the agent context.