Document v2 to v3 API migration strategy
Now that v2 is officially deprecated, we need to publish some documentation explaining how our various stakeholders are expected to migrate forward to using the v3 API.
This could include:
- keystoneclient usage
- service catalog expectations
- curl examples for common things like default-domain password auth
- pipeline configuration
- interpreting various 300 multiple choice responses
ttx also laid out a great process for API deprecation [1], wherein this bp is required for keystone to progress beyond step 4.
[1] http://
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Dolph Mathews
- Direction:
- Needs approval
- Assignee:
- Dolph Mathews
- Definition:
- New
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Dolph Mathews
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Would this also be related to Tempest blueprint https:/
Will this also cover what is new in V3? jogo 2014/3/31
morganfainberg added that as an agenda item for April 1st's Keystone Meeting: https:/
I think this is related to Tempest blueprint https:/
Gerrit topic: https:/
Addressed by: https:/
Add v2 & v3 API documentation
Addressed by: https:/
add docs on v2 & v3 support in the service catalog
