Disk Transfer
This topic describes only the authorization information of EVS v2 APIs. For the v3 APIs that provide the same functions as their v2 APIs, their authorization information is the same as that of the v2 APIs.
For example, the v2 API for creating disks is POST /v2/{project_id}/cloudvolumes, and the v3 API for creating disks is POST /v3/{project_id}/cloudvolumes. The authorization information of both APIs is the same.
In the following tables, √ indicates that the item is supported, and × indicates that the item is not supported.
|
Permission |
API |
Action |
IAM Project (Project) |
Enterprise Project (Enterprise Project) |
|---|---|---|---|---|
|
Create an EVS disk transfer (OpenStack Cinder API). |
POST /v2/{project_id}/os-volume-transfer |
evs:transfers:create |
√ |
× |
|
Query all EVS disk transfers of a tenant (OpenStack Cinder API). |
GET /v2/{project_id}/os-volume-transfer |
evs:transfers:list |
√ |
× |
|
Query details of all EVS disk transfers of a tenant (OpenStack Cinder API). |
GET /v2/{project_id}/os-volume-transfer/detail |
evs:transfers:list |
√ |
× |
|
Query details of an EVS disk transfer (OpenStack Cinder API). |
GET /v2/{project_id}/os-volume-transfer/{transfer_id} |
evs:transfers:get |
√ |
× |
|
Accept an EVS disk transfer (OpenStack Cinder API). |
POST /v2/{project_id}/os-volume-transfer/{transfer_id}/accept |
evs:transfers:accept |
√ |
× |
|
Delete an EVS disk transfer (OpenStack Cinder API). |
DELETE /v2/{project_id}/os-volume-transfer/{transfer_id} |
evs:transfers:delete |
√ |
× |
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.