Move to only using the keystone v3 API
Currently, heat_keystoneclient uses a mixture of v2 and v3 clients, which is suboptimal from both a performance and code-elegance perspective.
We should move to just using the v3 API, but we need ec2tokens to work via the v3 API (and keystoneclient), before this will work. I'm looking into what's needed to make that work, then we can port heat_keystoneclient to v3-only.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Steven Hardy
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
- Implemented
- Milestone target:
- 2014.1
- Started by
- Steven Hardy
- Completed by
- Steven Hardy
Related branches
Related bugs
Sprints
Whiteboard
Need review of https:/
(stevebaker) we could mark this as blocked so it gets raised at the next projects meeting?
Gerrit topic: https:/
Addressed by: https:/
Convert heat_keystoneclient user-create logic to v3 API
Addressed by: https:/
Convert heat_keystoneclient user-delete logic to v3 API
Addressed by: https:/
Convert heat_keystoneclient user enable/disable logic to v3 API
Addressed by: https:/
heat_
Addressed by: https:/
heat_
Addressed by: https:/
Store credential ID for AccessKey and SignalResponder
Addressed by: https:/
heat_
Addressed by: https:/
heat_
Addressed by: https:/
Fix user and signal responder exception import
Addressed by: https:/
Purge remaining heat_keystoneclient v2 code
Addressed by: https:/
Don't delete trust on backup stack delete
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.