Document v2 to v3 API migration strategy

Registered by Dolph Mathews

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://lists.openstack.org/pipermail/openstack-dev/2014-March/031040.html

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:
milestone icon 2014.2
Started by
Dolph Mathews
Completed by
Dolph Mathews

Related branches

Sprints

Whiteboard

Would this also be related to Tempest blueprint https://blueprints.launchpad.net/tempest/+spec/multi-keystone-api-version-tests for making sure other projects can run their API tests successfully with Keystone V3 in the gate? I'd think so. -- mriedem 2014/03/20

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://wiki.openstack.org/wiki/Meetings/KeystoneMeeting -dolphm

I think this is related to Tempest blueprint https://blueprints.launchpad.net/tempest/+spec/keystone-v3-jobs as well, about running full v3 check / gate jobs.

Gerrit topic: https://review.openstack.org/#q,topic:bp/document-v2-to-v3-transition,n,z

Addressed by: https://review.openstack.org/96242
    Add v2 & v3 API documentation

Addressed by: https://review.openstack.org/99075
    add docs on v2 & v3 support in the service catalog

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.