Enable Oslo.Messaging Dual Backends

Registered by Andy Smith on 2016-11-16

Add the capability to enable the selection and configuration of separate messaging backends for oslo.messaging RPC and Notification communications. Introduce support for a brokerless messaging backend for oslo.messaging RPC communications in the overcloud.

Blueprint information

Status:
Complete
Approver:
Steven Hardy
Priority:
Medium
Drafter:
Andy Smith
Direction:
Approved
Assignee:
Andy Smith
Definition:
Approved
Series goal:
Accepted for queens
Implementation:
Implemented
Milestone target:
milestone icon queens-2
Started by
Andy Smith on 2016-11-16
Completed by
Alex Schultz on 2017-12-08

Related branches

Sprints

Whiteboard

[2017-12-08] The listed patches are merged.

The spec described two tasks. The separation of the backends via rpc and notify transport_urls is complete. The introduction of the dispatch router for direct messaging is realized through the aliase of the rabbitmq service. A spec for a more systemic way to easily support alternative backends will be targeted for the queens release.

Gerrit topic: https://review.openstack.org/#/q/topic:qdr

Addressed by: https://review.openstack.org/446695/
  Add external listener, connector and address configuration

Addressed by: https://review.openstack.org/448279/
  Create qdr HA mesh

Addressed by: https://review.openstack.org/423326/
  Qpid dispatch router composable role

Addressed by: https://review.openstack.org/425710/
  Qpid dispatch router puppet profile

Addressed by: https://review.openstack.org/447319/
  Include oslo.messaging amqp support for rpc and notifications

Addressed by: https://review.openstack.org/437942/
  Add qpid-dispatch-router to overcloud-controller element

Addressed by: https://review.openstack.org/425484/
  Use rpc and notify transport_url for oslo_messaging backends

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.