Difference between revisions of "Trove-rpc-versioning"
Dan Nguyen (talk | contribs) m |
Dan Nguyen (talk | contribs) m (→Intro) |
||
| Line 1: | Line 1: | ||
=== Intro === | === Intro === | ||
This page describes the intent to implement oslo messaging's API Version Negotiation in Trove | This page describes the intent to implement oslo messaging's API Version Negotiation in Trove | ||
| + | ==== Oslo ==== | ||
[[Oslo/Messaging#API_Version_Negotiation]] | [[Oslo/Messaging#API_Version_Negotiation]] | ||
| + | |||
=== Goals === | === Goals === | ||
* Prevent backward incompatibility between Trove components. | * Prevent backward incompatibility between Trove components. | ||
Revision as of 22:16, 10 April 2014
Intro
This page describes the intent to implement oslo messaging's API Version Negotiation in Trove
Oslo
Oslo/Messaging#API_Version_Negotiation
Goals
- Prevent backward incompatibility between Trove components.
- Reduce the need for downtime during deployments
Work
- Keep track of a "version history" in comments in the code
- Update trove calls to the openstack.commom.rpc client to include a version cap param. (This is already supported in the client)
- Document the use cases and examples of how to add/modify API calls
