Add more information to the service catalogs to enable federated zones.

Registered by Christopher MacGown

At their most abstract, zones are a meta-concept layered over independent installations of OpenStack services. Whether nova cells, or swift regions, whatever quantum calls them, or federated instances of glance, a base zone need not be aware of the infrastructure, data, or implementation of their peers. After authenticating with Keystone, you receive back a service catalog containing the end-points for each service. Since we return endpoints in a list, we already expose a way of handling zones in a simple, effective manner.

Blueprint information

Status:
Complete
Approver:
Christopher MacGown
Priority:
Undefined
Drafter:
Christopher MacGown
Direction:
Needs approval
Assignee:
Christopher MacGown
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Joseph Heck

Related branches

Sprints

Whiteboard

http://etherpad.openstack.org/FolsomFederatedZones

marking obsolete, as it overlaps with service relationship blueprint based on essex design summit discussions. Chris - holler if you disagree.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.