[Rdo-list] Neutron-openswitch-agent configuration workaround in RDO Juno/Kilo and now in Liberty

Markelov Andrey amarkelov at yandex.ru
Thu Nov 5 14:47:24 UTC 2015

Ok. Thanks!

And if we are talking about plugin.ini/ml2_conf.ini according to network node in Kilo doc - 


For whom plugin.ini/ml2_conf.ini is needed? Neutron-server is started only on control node.
So it seems the only who used plugin.ini/ml2_conf.ini is neutron-openvswitch-agent (but in wrong manner after "bug fixing")?


05.11.2015, 15:47, "Ihar Hrachyshka" <ihrachys at redhat.com>:
> Markelov Andrey <amarkelov at yandex.ru> wrote:
>>  Thanks for clarification!
>>  No, as I wrote before it is not documented in Liberty,
>>  but Kilo & Juno:
>>  "Due to a packaging bug, the Open vSwitch agent initialization script
>>  explicitly looks for the Open vSwitch plug-in configuration file rather
>>  than a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in
>>  configuration file. Run the following commands to resolve this issue:"
>>  http://docs.openstack.org/kilo/install-guide/install/yum/content/neutron-compute-node.html
> Yeah. So long story short, the text you quoted was always wrong, and they
> finally fixed it by removing the notion of ‘a packaging bug’ which was
> never a packaging bug in RDO but a documentation bug in upstream docs.
> I am glad to hear it’s not there anymore. That said, I would make sure that
> they actually have proper instructions on how to configure the agent (using
> openvswitch_agent.ini). [For linuxbridge, they are correct:
> http://docs.openstack.org/liberty/install-guide-rdo/neutron-compute-install-option1.html]
> Ihar

Best regards,
Andrey Markelov

More information about the rdo-list mailing list