Stable Keystone Driver Interfaces

Registered by Vivek Dhayaal on 2015-08-05

Keystone has a number of backend drivers that are purportedly able to be replaced by a developer or deployer with their own implementation (e.g. utilizing mongodb as a store for Identity information). Currently these drivers have had significant interface changes each cycle making it difficult for developers to maintain custom (or subclassed) drivers as each release has caused a significant delta in all of the Keystone Driver Interface definitions. To properly support developers who are implementing drivers for Keystone out of tree, the Keystone Driver Interface need to be stable like the REST API is. This specification is to commit to the interface for each driver and ensure that drivers that are written against Liberty will work with the M-Release of Keystone as well (a minimum of 2-cycle Interface commitment).
http://specs.openstack.org/openstack/keystone-specs/specs/liberty/stable-driver-interfaces.html

Blueprint information

Status:
Complete
Approver:
David Stanek
Priority:
Medium
Drafter:
Vivek Dhayaal
Direction:
Approved
Assignee:
Vivek Dhayaal
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 8.0.0
Started by
Morgan Fainberg on 2015-09-02
Completed by
Morgan Fainberg on 2015-09-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/stable-driver-interfaces,n,z

Addressed by: https://review.openstack.org/209524 (merged)
    Stable Keystone Driver Interfaces

Addressed by: https://review.openstack.org/218481 (merged)
    Initial support for versioned driver classes

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.