Discoverable and Hierarchical Catalog
The current Keystone catalog does not have a coherent design to address a typical IT catalog stack. The lack of data organization and self-discovery approach makes it very limited in use and does not provide a good solution for a global service catalog that can support IaaS, PaaS and SaaS.
Our approach is to change the catalog definition to make it easy to discover the services, their geographical location, type and access interfaces.
The proposed solution is to create a catalog that is built on a hierarchical structure.
The tree-like structure can be then navigated using a set of links that provides URL pointing to the next level in the hierarchy something like, child/parent relationship.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Fabio Giannetti
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
(morganfainberg): This is implemented effectively via regions. Marking as obsolte.
GET v3/catalog -- only the v3 services
GET v2/catalog -- only the v2 services
GET /catalog -- all the v2/v3/vN services
Will return the following response:
{
"catalog": {
"services": [
{
},
]
},
...
}
]
}
}
It is possible to perform requests that are traversing the tree to obtain directly a sub-tree, e.g.:
GET v3/catalog/
This would allow to retrieve all the services, e.g. compute, that are available in a certain region.
