Support placing a cap on message version on the client side

Registered by Russell Bryant on 2013-05-15

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:
milestone icon 2013.2
Started by
Russell Bryant on 2013-05-16
Completed by
Russell Bryant on 2013-05-16

Related branches

Sprints

Whiteboard

pre-req for the same blueprint in nova (where some nova specific parts will be added): https://blueprints.launchpad.net/nova/+spec/rpc-version-control

Implemented by https://review.openstack.org/29290

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.