Use the Keystone Credential API for Keypairs
Nova only maintains a store of Keypairs for historical reasons. Recently, the Keystone credential API has become an official part of the V3 API, and provides a reasonable, user-linked location to store Keypairs.
As an aspect of this work, the Nova should be able to enumerate the Keys based on filters other than just user ownership. For example, Keys should be associated with a project, and any Keys associated with the project should be candidates for injection into an new VM.
This can potentially expand to other forms of credentials managed by Keystone in the future, to include X509 certificates.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Adam Young
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
