Support Separate RPC and Notification Messaging Backends

Registered by Andy Smith on 2017-10-12

The oslo.messaging library supports the deployment of dual messaging system backends for RPC and Notification communications. Tripleo currently supports the deployment of a single messaging backend (rabbitmq server) for both communication patterns. The proposal is to support separate backends and the provide the parameters needed to specify each messaging service.

This builds upon:
https://blueprints.launchpad.net/tripleo/+spec/om-dual-backends

Blueprint information

Status:
Started
Approver:
None
Priority:
Medium
Drafter:
Andy Smith
Direction:
Needs approval
Assignee:
Andy Smith
Definition:
New
Series goal:
Accepted for rocky
Implementation:
Good progress
Milestone target:
milestone icon rocky-1
Started by
Andy Smith on 2017-10-12

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/tripleo-messaging,n,z

Addressed by: https://review.openstack.org/507963
    WIP Separate rpc and notify messaging backends

Addressed by: https://review.openstack.org/510684
    WIP: Updates to separate messaging backends alternative

Addressed by: https://review.openstack.org/508259
    Add passwords for separate messaging backends

Addressed by: https://review.openstack.org/522406
    WIP Support both rabbitmq and oslo.messaging services

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.