Service relationships

Registered by Joe Savak

A volume service may be associated with an explicit compute service. There is no way to explicitly indicate this relationship via the service catalog today. Type and names can be duplicated according to the contract and expanding a URL type for a relationship seems like over-kill. There needs to be a collection or grouping of services to indicate which ones play well with each other.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
None
Direction:
Needs approval
Assignee:
Joe Savak
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Morgan Fainberg

Related branches

Sprints

Whiteboard

http://etherpad.openstack.org/FolsomKeystoneServiceRelationships

(morganfainberg): I think this is mostly covered by the concept of Regions... I'm going to mark this as superseded and we can revisit later as needed

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.