Support placing a cap on message version on the client side
Registered by
Russell Bryant
This blueprint is for the required changes in oslo to support rpc clients being configured with a version cap. This is a requirement for doing rolling upgrades where you need to prevent clients from sending new messages until all nodes have been upgraded to the version that supports them.
Blueprint information
- Status:
- Complete
- Approver:
- Mark McLoughlin
- Priority:
- Medium
- Drafter:
- Russell Bryant
- Direction:
- Approved
- Assignee:
- Russell Bryant
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Russell Bryant
- Completed by
- Russell Bryant
Related branches
Related bugs
Sprints
Whiteboard
pre-req for the same blueprint in nova (where some nova specific parts will be added): https:/
Implemented by https:/
(?)