As an API user I would like to GET an overcloud resource that contains all the end points

Registered by Martyn Taylor on 2013-09-06

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://file.rdu.redhat.com/~jslagle/drawing2.png ) - or more just about being able to manage the overcloud services yourself. i.e. we can use this if we go idea2 way. -not so simple - would need a way for overcloud services to talk back to tuskar to get the endpoints (e.g. cos compute in overcloud 1 needs to talk to glance in overcloud 2). in fact the whole cross overcloud thing is a big problem (exploring nova-conductor a bit but fuzzy still)

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:
milestone icon icehouse-1
Started by
Imre Farkas on 2013-10-01
Completed by
Imre Farkas on 2013-11-15

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/tuskar-api-return-endpoints,n,z

Addressed by: https://review.openstack.org/49544
    Add API endpoint for the overcloud service endpoints

Addressed by: https://review.openstack.org/48924
    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.

This blueprint contains Public information 
Everyone can see this information.