Support Separate RPC and Notification Messaging Backends
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:/
Blueprint information
- Status:
- Complete
- Approver:
- Alex Schultz
- Priority:
- Medium
- Drafter:
- Andy Smith
- Direction:
- Approved
- Assignee:
- Andy Smith
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-3
- Started by
- Andy Smith
- Completed by
- Andy Smith
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Separate rpc and notify messaging backends
Addressed by: https:/
Updates to separate messaging backends alternative
Addressed by: https:/
Add passwords for separate messaging backends
Addressed by: https:/
Support both rabbitmq and oslo.messaging services
Addressed by: https:/
Remove rabbit params replaced by oslo messaging params
Addressed by: https:/
Switch from rabbit to oslo messaging params
Addressed by: https:/
[DNM] testing separate messaging backends
Addressed by: https:/
Add messaging notification transport url
Addressed by: https:/
Document updates to messaging configuration
