openstack-ansible-os_neutron/releasenotes/notes/oslo-messaging-separate-backends-9b3fcaaa21a0d9f4.yaml
Andrew Smith 4db9c95d6f Update to use oslo.messaging service for RPC and Notify
This introduces oslo.messaging variables that define the RPC and
Notify transports for the OpenStack services. These parameters
replace the rabbitmq values and are used to generate the messaging
transport_url for the service. The association of the messaging
backend server to the oslo.messaging services will then be
transparent to the neutron service.

This patch:
* Add oslo.messaging variables for RPC and Notify to defaults
* Update transport_url generation
* Add oslo.messaging to tests inventories
* Add release note

Depends-On: If4326a6848d2d32af284fdbb94798eb0b03734d5
Depends-On: I2b09145b60116c029fc85477399c24f94974b61d
Change-Id: I717880458f69870acf75a101481b7776d250ebf4
2018-05-23 12:11:00 -04:00

20 lines
1.1 KiB
YAML

---
features:
- Support separate oslo.messaging services for RPC and Notifications
to enable operation of separate and different messaging backend servers.
deprecations:
- |
The rabbitmq server parameters have been replaced by corresponding
oslo.messaging RPC and Notify parameters in order to abstract the
messaging service from the actual backend server deployment.
- neutron_oslomsg_rpc_servers replaces neutron_rabbitmq_servers
- neutron_oslomsg_rpc_port replaces neutron_rabbitmq_port
- neutron_oslomsg_rpc_use_ssl replaces neutron_rabbitmq_use_ssl
- neutron_oslomsg_rpc_userid replaces neutron_rabbitmq_userid
- neutron_oslomsg_rpc_vhost replaces neutron_rabbitmq_vhost
- neutron_oslomsg_notify_servers replaces neutron_rabbitmq_telemetry_servers
- neutron_oslomsg_notify_port replaces neutron_rabbitmq_telemetry_port
- neutron_oslomsg_notify_use_ssl replaces neutron_rabbitmq_telemetry_use_ssl
- neutron_oslomsg_notify_userid replaces neutron_rabbitmq_telemetry_userid
- neutron_oslomsg_notify_vhost replaces neutron_rabbitmq_telemetry_vhost