Resource availability based on Keystone Service Catalog
Resource (see https:/
We need to validate that all resources in the stack are
available, i.e. for every service used in each resource in the stack there is at least one endpoint available in Keystone.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- Pavlo Shchelokovskyy
- Direction:
- Approved
- Assignee:
- Kanagaraj Manickam
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- 5.0.0
- Started by
- Serg Melikyan
- Completed by
- Steve Baker
Related branches
Related bugs
Bug #1174005: swiftclient, quantumclient, and cinderclient, are not optional | Fix Released |
Sprints
Whiteboard
(stevebaker) I'm going to remove the milestone until there is an assignee
(shardy): sergmelikyan assigned after IRC request
Gerrit topic: https:/
Addressed by: https:/
Implements resource availability based on Keystone
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Conditionally expose resources based on services
Addressed by: https:/
Conditionally expose resources based on available services
Addressed by: https:/
List resource_type based on availability
Addressed by: https:/
Make sure default_client_name declared for required resources
Addressed by: https:/
Adds service_types to client_plugins
Addressed by: https:/
Refactor Adding service_types to client_plugins
Addressed by: https:/
Add functional test for resource exposure
Addressed by: https:/
Fix StackResourceUn