View Single Volume
(Difference between revisions)
Mike.robski (Talk | contribs) |
Mike.robski (Talk | contribs) m (1 revision) |
Revision as of 09:25, 24 May 2013
This operation will return details of a single volume.
Contents |
GET /volumes/id
This operation will return details of a single volume.
Request Parameters
- id
- The unique identifier of the volume.
Result
JSON
{ "volume" : { "id": "{volume_id}", "display_name" : "{display_volume_name}", "display_description" : "{display_volume_description}", "size" : {size_quantity}, "volume_type" : "{volume_type_id}", "metadata" : {}, "availability_zone" : "{availability_zone_id}", "attachments": [], "links": [ { "href": "http://{api_server}/volumes/{volume_id}/", "rel": "self" } ], "snapshot_id": "", "created_at": "2012-05-03 11:35:44" } }
volume
- id - string
- Identifier of the volume instance.
- display_name - string
- Display name for this volume.
- display_description - string
- Descriptive information for this volume.
- size - int
- Volume size.
- volume_type - string
- Identifier of the volume type used. *(Not used in the current version).
- metadata - string
- Additional metadata info.
- availability_zone - string
- Identifier of the availability zone into which this volume was created.
- attachments - list
- List of attachments this volume is associated with.
- links - array
- Hypermedia for this resource.
- snapshot_id - string
- Identifier of the snapshot associated with this volume if exists.
- created_at - string
- Volume creation timestamp.
Response Codes
- Success
- HTTP/1.1 200 OK
- Failure
- HTTP/1.1 401 Unauthorized - This server could not verify that you are authorized to access the document you requested. Either you supplied incorrect credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.
- HTTP/1.1 404 Not Found - The resource does not exist.
Examples
Successfully get single volume details
- GET http://{api_server}/volumes/hbs2012May03_0OxRg0Jz7
Request Headers:
Content-Type:application/json Charset=UTF-8 Authorization:Base64-encoded username & password string
Response Code:
HTTP/1.1 200 OK
Response Body:
{ "volume": { "display_name": "vol-test-003", "attachments": [], "links": [ { "href": "http://{api_server}/volumes/hbs2012May03_0OxRg0Jz7/", "rel": "self" } ], "availability_zone": "test_zone", "created_at": "2012-05-03 11:35:44", "volume_type": "", "display_description": "Another test volume.", "snapshot_id": "", "metadata": {}, "id": "hbs2012May03_0OxRg0Jz7", "size": "30GB" } }
Failure while trying to request for a volume that does not exist
- GET http(s)://{api_server}/volumes/{fake_volume_id}
Request Headers:
Content-Type:application/json Charset=UTF-8 Authorization:Base64-encoded username & password string
Response Code:
HTTP/1.1 404 Not Found
Response Body:
{ "itemNotFound": { "message": "Resource not found", "code": 404, "details": "", "errorid": "59e0b3dd-2173-432a-8ff5-60efe16e83bf" } }
Failure while trying to make an unauthorized request
- GET http://{api_server}/volume/{volume_id}
Request Headers:
Content-Type:application/json
Charset=UTF-8
Authorization:Base64-encoded fake_authentication_string
Response Code:
HTTP/1.1 401 Unauthorized
Response Body:
401 Unauthorized This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.