-
Epic
-
Resolution: Done-Errata
-
Major
-
None
-
[RFE] Remove requirement for project_id in Cinder API paths
-
False
-
False
-
Committed
-
No Docs Impact
-
OSP-9820 - System Scope Secure Role Based Access Control
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
-
Feature
-
Done
-
Regression Only
Today Cinder's API design assumes that a project_id will be on every request[1].
In order to consume system scoped requests, Cinder will need to update its APIs to remove project_id from the path. For example, use:
https://cinder.example.com/v3/volumes
instead of:
https://cinder.example.com/v3/422c276436a44096bb7cd626ef1813ca/volumes
where 422c276436a44096bb7cd626ef1813ca is the id of a project in keystone.
[1] - https://docs.openstack.org/api-ref/block-storage/v3/index.html#volumes-volumes
- external trackers
- links to
-
RHBA-2024:133297 Release of components for Red Hat OpenStack Services on OpenShift 18.0