Openvswitch-agent still uses AMQP settings from DEFAULT configuration section

[Tom Verdaat]

In the Liberty release, the neutron openvswitch agent uses the message queue settings from the DEFAULT section in stead of the oslo_messaging_* section.

Experienced on Ubuntu 14.04 using the ubuntu-cloud-archive packages.

[Ema (menari2)]

hi Tom, Kaustav, is it ok if I picked up this bug? I will like to work on it as my first bug fix task. Please, if you have some guidance for me on how to approach this bug, I will be very grateful. Thanks.

[Victor Morales (electrocucaracha)]

IMHO, I think that this bug should be closed. The only place where I found that this connects with Message Broker is thru oslo.messaging module. In other words, the setup_rpc method of OVSNeutronAgent[1] class opens a new connection to create consumers[2], those consumers are created with oslo_messaging module[3] and all the agents should use the same shared code.

[1] https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L391-L394
[2] https://github.com/openstack/neutron/blob/master/neutron/agent/rpc.py#L46
[3] https://github.com/openstack/neutron/blob/master/neutron/common/rpc.py#L292-L296

[Tom Verdaat (tom-verdaat)]

It's not an issue for Liberty and it could very well have been fixed in master thanks to code refactoring efforts. If so, feel free to close it.