Replace the current concept of extensions in Keystone
The current extensions concept allows for experimental functionality to be introduced into Keystone. However, it leads to an increasingly complex set of wsgi components that may or may not be loaded, making it harder for other services/clients to be able to "interface with keystone". Experience from other projects (e.g. nova) suggests that as the number of extensions grows, the situation becomes unmanageable.
This blueprint proposes that the extension concept is replaces with the ability for functionality to be either be "stable", "experimental" or "out of tree".
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Henry Nash
- Direction:
- Approved
- Assignee:
- Keystone Drivers
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Morgan Fainberg
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Replace the concept of extensions in Keystone.
Gerrit topic: https:/
Addressed by: https:/
Classifying extensions and defining process
Gerrit topic: https:/
Addressed by: https:/
WIP - make federation part of keystone core
Gerrit topic: https:/
Addressed by: https:/
Include other stable extensions in core
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Use correct dependency decorator
Addressed by: https:/
Add ``service_
Addressed by: https:/
Move endpoint_policy migrations into keystone core
Addressed by: https:/
Move endpoint policy into keystone core
Addressed by: https:/
WIP: Move endpoint filter into keystone core
Addressed by: https:/
Move endpoint_filter migrations into keystone core
Addressed by: https:/
Move federation extension into keystone core
Addressed by: https:/
Move federation sql migrations to common
Addressed by: https:/
Move oauth1 extension into core
