ListVolumeDetailsForServerVolumeAttachment

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 +
=='''GET''' /servers/'''server_id'''/os-volume_attachments/'''volume_id'''''==
 
This operation returns volume details for the specific server's volume attachment.
 
This operation returns volume details for the specific server's volume attachment.
  
='''GET''' /servers/'''server_id'''/os-volume_attachments/'''volume_id'''''=
+
=== Parameters ===
 
+
== Parameters ==
+
 
; server_id
 
; server_id
 
: The unique identifier of the server.
 
: The unique identifier of the server.
Line 10: Line 9:
 
: The unique volume identifier.
 
: The unique volume identifier.
  
== Result ==
+
=== Result ===
=== JSON ===
+
==== JSON ====
 
  <nowiki>
 
  <nowiki>
 
{
 
{
Line 35: Line 34:
 
</nowiki>
 
</nowiki>
  
====volume====
+
=====volume=====
 
; id - ''string''
 
; id - ''string''
 
: Identifier of the volume instance.
 
: Identifier of the volume instance.
Line 69: Line 68:
 
: Volume creation timestamp.
 
: Volume creation timestamp.
  
== Response Codes ==
+
=== Response Codes ===
 
; Success:
 
; Success:
 
:''HTTP/1.1 200 OK''
 
:''HTTP/1.1 200 OK''
Line 77: Line 76:
 
:''HTTP/1.1 404 Not Found'' - The resource does not exist.
 
:''HTTP/1.1 404 Not Found'' - The resource does not exist.
  
== Examples ==
+
=== Examples ===
 
'''Successfully get volume details for a server volume attachment'''
 
'''Successfully get volume details for a server volume attachment'''
 
:'''GET''' http(s)://{api_server}/servers/test-server-0013/os-volume_attachments/hbs2012May03_0OxRg0Jz7
 
:'''GET''' http(s)://{api_server}/servers/test-server-0013/os-volume_attachments/hbs2012May03_0OxRg0Jz7
Line 172: Line 171:
 
     does not understand how to supply the credentials required.
 
     does not understand how to supply the credentials required.
  
 
+
[[Category:Hostway API]]
[[Category:API]]
+
[[Category:FlexCloud Server API]]
  
 
<!--  THIS CODE ENABLES DISQUS COMMENTS ON THE PAGE - DELETE TO DISABLE COMMENTING-->
 
<!--  THIS CODE ENABLES DISQUS COMMENTS ON THE PAGE - DELETE TO DISABLE COMMENTING-->

Revision as of 17:37, 14 December 2012

Contents

GET /servers/server_id/os-volume_attachments/volume_id

This operation returns volume details for the specific server's volume attachment.

Parameters

server_id
The unique identifier of the server.
volume_id
The unique volume identifier.

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 volume details for a server volume attachment

GET http(s)://{api_server}/servers/test-server-0013/os-volume_attachments/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 get volume details for a volume that does not exist

GET http(s)://{api_server}/servers/test-server-0013/os-volume_attachments/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": ""
      }
}

Failure while trying to get volume details for a server that does not exist

GET http(s)://{api_server}/servers/fake_server_id/os-volume_attachments/hbs2012May03_0OxRg0Jz7

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": ""
      }
}

Unauthorized request

GET http(s)://{api_server}/servers/test-server-0013/os-volume_attachments/hbs2012May03_0OxRg0Jz7

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.


blog comments powered by Disqus


Personal tools
Namespaces
Variants
Actions
APIs
Navigation
Toolbox