Peer-to-Peer Keystones for Federation Management
Registered by
Craig A. Lee
What does it mean to "import" remote services into a Keystone instance and make them available to local users? How is this importation managed? How is access to the imported service authorized? This blueprint begins to address these issues through the use of virtual organizations as a way of managing Keystone federation in a peer-to-peer manner. Other forms of broker/proxy federation management are possible. For now, however, this blueprint focuses just on P2P Keystones.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Craig A. Lee
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
(morganfainberg): This has largely been implemented via the K2K federation and will continue to see improvements on that front. Marking this BP as superseded.
(?)