Define supported services
Within the OpenStack landscape, there are many services available to end users, such as Nova (compute) and Swift (storage). The scope of the service offering needs to have some defined limits as to what is a part of the core or the main offering for the SDK.
Blueprint information
- Status:
- Complete
- Approver:
- Brian Curtin
- Priority:
- Essential
- Drafter:
- Brian Curtin
- Direction:
- Needs approval
- Assignee:
- Terry Howe
- Definition:
- Approved
- Series goal:
- Accepted for master
- Implementation:
- Informational
- Milestone target:
- None
- Started by
- Terry Howe
- Completed by
- Terry Howe
Related branches
Related bugs
Sprints
Whiteboard
The supported services are:
* compute
* database
* identity
* image
* network
* object_store
* orchestration
* telemetry
Services should be identified by their program names, rather than their project names. For example, `openstack.compute` is the correct choice over `openstack.nova`.
Service APIs should be implemented as low-level as possible, allowing for higher-level clients to be built on top of them. For example, a command-line interface or a convenience module would be a higher-level way to interact with the low-level module, rather than starting the library based on convenience.