A standalone heat server which acts on multiple external OpenStacks
Building on https:/
All actions will be performed using whatever keystone endpoint and credentials are passed to the request. Tasks include:
- changing authpassword middleware to take the keystone endpoint from the request header rather than config
- providing a way for the cfn and cloudwatch pipelines to find out what keystone endpoint to use for incoming signal and watch data
Blueprint information
- Status:
- Complete
- Approver:
- Steven Hardy
- Priority:
- Medium
- Drafter:
- Steve Baker
- Direction:
- Approved
- Assignee:
- Steve Baker
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Ben Nemec
- Completed by
- Steven Hardy
Related branches
Related bugs
Sprints
Whiteboard
(shardy) Wiki page describing how this will work would be good, so set Definition to "Drafting", also since we have *way* too many BPs for h3, pushing this out to Icehouse - we can pull it back if we end up having time to do it, but lets focus on getting heat-standalone done first?
(stevebaker) I've created a wiki spec and assigned this to potential new contributor Ben Nemec.
Gerrit topic: https:/
Addressed by: https:/
Enable multi-cloud standalone mode
(stevebaker) Re-opening to track changes to ec2token middleware
Addressed by: https:/
Replace httplib with requests for ec2tokens auth
Addressed by: https:/
EC2token middleware implement multi-cloud auth
Addressed by: https:/
Always validate auth_uri with allowed_auth_uris
Work Items
Dependency tree
* Blueprints in grey have been implemented.
