As an API user I would like to GET an overcloud resource that contains all the end points
As an API user I would like to GET an overcloud resource that contains all the end points
so we'll need a new resource type, like 'GET /api/v1/end_points' etc - exposing appropriate routes.
is this story part of the whole 'we need to talk cross overcloud (especially if we go with http://
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Imre Farkas
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- icehouse-1
- Started by
- Imre Farkas
- Completed by
- Imre Farkas
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add API endpoint for the overcloud service endpoints
Addressed by: https:/
Add Heat output params for the overcloud service endpoints
-- this seems very confusing to me, can we have a design discussion on it, or perhaps an etherpad? -- lifeless
[ifarkas]
As lifeless and martyntaylor pointed out, it's sufficient to return the url for the overcloud Keystone endpoint. The user can query the service catalog using that.
Work Items
Dependency tree
* Blueprints in grey have been implemented.