Bug 1921889 - RFE: Remove requirement for project_id in Cinder API paths
Summary: RFE: Remove requirement for project_id in Cinder API paths
Keywords:
Status: POST
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 18.0 (Zed)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Alpha
: 18.0
Assignee: Alan Bishop
QA Contact: Evelina Shames
Andy Stillman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-28 18:57 UTC by Harry Rybacki
Modified: 2023-07-29 08:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 822040 0 None MERGED Remove the need for project_id from API endpoints 2022-03-01 15:03:37 UTC
Red Hat Issue Tracker OSP-2160 0 None None None 2022-03-01 15:07:20 UTC

Description Harry Rybacki 2021-01-28 18:57:59 UTC
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


Note You need to log in before you can comment on or make changes to this bug.