BUILD &ARROW;
- ACTIVE
- ACTIVE
BUILD &ARROW;
- ERROR (on error) ERROR (on error)
ACTIVE &ARROW;
PASSWORD &ARROW;
ACTIVE
-
+
@@ -1696,14 +1683,14 @@ Host: servers.api.rackspacecloud.com/v1.0/
ACTIVE &ARROW;
DELETED
- SUSPENDED &ARROW;
DELETED
- SHARE_IP &ARROW;
ACTIVE (if
ACTIVE &ARROW;
SHARE_IP_NO_CONFIG
&ARROW; ACTIVE
-
+
ACTIVE &ARROW;
DELETE_IP &ARROW;
ACTIVE
-
+
@@ -2009,7 +1996,7 @@ Host: servers.api.rackspacecloud.com/v1.0/
ACTIVE &ARROW;
REBOOT &ARROW;
ACTIVE (ACTIVE &ARROW;
HARD_REBOOT &ARROW;
ACTIVE (ACTIVE &ARROW;
REBUILD &ARROW;
- ACTIVE
- ACTIVE
ACTIVE &ARROW;
REBUILD &ARROW;
- ERROR (on error) ERROR (on error)
QUEUE_RESIZE &ARROW;
PREP_RESIZE &ARROW;
RESIZE &ARROW;
- VERIFY_RESIZE
-
+ VERIFY_RESIZE
ACTIVE &ARROW;
QUEUE_RESIZE &ARROW;
- ACTIVE (on error)
- ACTIVE (on error)
VERIFY_RESIZE &ARROW;
ACTIVE
- VERIFY_RESIZE &ARROW;
- ACTIVE
- ACTIVE
@@ -2572,8 +2553,7 @@ Host: servers.api.rackspacecloud.com/v1.0/
QUEUED &ARROW;
PREPARING &ARROW;
SAVING &ARROW;
- ACTIVE
-
+ ACTIVE
QUEUED &ARROW;
PREPARING &ARROW;
SAVING &ARROW;
- FAILED (on error)
-
+ FAILED (on error)
- This schema file defines actions that can be performed on a - cloud server. All cloud server actions are derived from the Action type. -
-- Performs a HARD or SOFT reboot. -
-- Rebuilds a server. -
-- Resizes a server. -
-- Confirms a resize action. -
-- Reverts a resize action. -
-- This is the base type for all server actions. It is simply - a marker abstract type used to differentiate an Action - element from other elements. -
-- The type of reboot to perform. -
-- The id of an image to use for the rebuild. -
-- The id of the flavor to convert to. -
-- A HARD reboot is equivalent to power cycling the server. - The operating system is not allowed to gracefully - shutdown. -
-- With a SOFT reboot, the operating system is signaled to - restart. This allows for a graceful shutdown of all - processes. -
-
- This schema file defines faults that may be raised by the
- Cloud Servers API. These faults are derived from the CloudServersAPIFault. Most faults
- extend this type without adding any additional attributes or
- elements. The only exception is the OverLimitAPIFault which adds a
- retryAfter attribute. Because all faults
- extend a standard base type, it should be possible to capture
- all API faults with a single catch statement.
-
- Faults are associated with a default HTTP status code that - corresponds to the particular fault type. For example an <itemNotFound> element is associated - with the HTTP status code 404. Some elements, the <cloudServersFault> element for - example, may be associated with multiple status codes. It is - also possible for multiple fault elements to be associated - with the same default code. The examples below showcase the - default status codes for each element type. Note that these - default codes are not part of the formal schema. In practice, - however, an element type will likely be associated with its - corresponding default status code. -
-- A generic Cloud Servers API fault. -
-- The item or resource could not be found. -
-- The operation is not allowed because the corresponding - server is in a build state. -
-- There is not enough capacity to honor the request. -
-- The operation is not allowed because the corresponding - server is being re-sized or backed up. -
-- The re-size operation is not permitted. -
-- The API service is currently unavailable. -
-- Insufficient privileges to honor the request, perhaps an - authentication token needs to be obtained or renewed. -
-- The request is malformed. -
-- The Content Type of the request is not supported. -
-- The HTTP method (or verb) is not - supported by the corresponding resource. -
-- The operation is currently not implemented. -
-- A human readable message that is appropriate for display - to the end user. -
-- The optional <details> element may contain useful - information for tracking down errors (e.g a stack - trace). This information may or may not be appropriate - for display to an end user. -
-- The HTTP status code associated with the current fault. -
-- An optional dateTime denoting when an operation should - be retried. -
-- This schema file defines a - Server and all internal entities - related to servers including: - Addresses, - ShareIPs, - Files, and - MetaData. -
-- Common types used by multiple entities and possibly spanning - several types of requests. -
-- The element defines a server. -
-- A collection of servers. -
-- The element defines list of addresses (public and private). -
-- The element defines a list of public addresses. -
-- The element defines list of private addresses. -
-- The element defines request to share a public IP address. -
-- The element defines request to add an IP address. -
-- The element defines response that returns an added IP address. -
-- A server is a virtual machine instance in the Cloud Servers - system. Note that this complex type defines all elements - and attributes as optional because a server instance may - take many different forms depending on the operation. When - creating a server, for example, the name, imageId, and - flavorId attributes are required. In addition, optional - metadata and personality file elements may be specified: -
-- The response to such a crate operation will include the - administration password, host ID, and addresses associated - with the server: -
-- When modifying a server only the name and administration - password should be specified as these are the only - attributes that are modifiable. -
-- A collection of meta data items associated with the server. -
-- A server's public and private address. -
-- A collection of small files used to personalize a new - server instance. -
-- The name of the server. -
-- The ID of the server. -
-- The server's administration password. -
-- The ID of the image used to create the server. -
-- The current server flavor ID. -
-- A unique ID that identifies the physical host that the VM - is running on. This ID is unique per - account and not globally unique. -
-- The progress of the current server operation. -
-- The current state (or status) of the - server. -
-- An ID of the shared IP - group that the server belongs to. -
-- A collection of servers. -
-- A collection of metadata items. -
-- A MetadataItem is simply a name-value pair. The name is - specified in the key attribute and the value is included inline. -
-- A meta data name-value pair. -
-- A collection of files. -
-- A file is simply a full path along with base64 file - content. The name of the file is specified in the path - attribute and the file content is included - inline. -
-- Full file path. -
-- Public server addresses. -
-- Private server addresses. -
-- A collection of addresses. -
-- An IP address. -
-- This type is used to represent a request to share an IP - address. -
-- The shared IP group use to - share the address. -
-- If true, the server is configured with the new address - though the address may not be enabled. -
-- This type is used to represent a request to add an IP - address. -
-- If true, the server is added and configured with the new address - though the address may not be enabled. -
-- The server is ready to use. -
-- The server is in an inactive (suspended) state. -
-- The server has been deleted. -
-- A request to perform a resize action has been received. The - operation is pending. -
-- The server is being prepared to perform the resize - operation. -
-- The server is being resized. -
-- The server is waiting for the resize operation to be - confirmed so that the original server may be removed. -
-- The server is in rescue mode. -
-- The requested operation failed, the server is in an - error state. -
-- The server is being built. -
-- The server is being restored. -
-- The server password is being changed. -
-- The server is being rebuilt. -
-- A shared IP address is being removed. -
-- An IP address is being shared, but not configured. -
-- An IP address is being shared, and the server is being - configured with the new address. -
-- An IP address is being added, but not configured. -
-- An IP address is being added, and the server is being - configured with the new address. -
-- The server is going through a SOFT reboot. -
-- The server is going through a HARD reboot. -
-- The server is in an unknown state. -
-- Reserved for future use. -
-- Reserved for future use. -
-- Reserved for future use. -
-- Reserved for future use. -
-- Reserved for future use. -
-This schema file defines actions that can be performed on a + cloud server. All cloud server actions are derived from the Action type.
+Performs a HARD or SOFT reboot.
+Rebuilds a server.
+Resizes a server.
+Confirms a resize action.
+Reverts a resize action.
+This is the base type for all server actions. It is simply + a marker abstract type used to differentiate an Action + element from other elements.
+The type of reboot to perform.
+The id of an image to use for the rebuild.
+The id of the flavor to convert to.
+A HARD reboot is equivalent to power cycling the + server. The operating system is not allowed to + gracefully shutdown.
+With a SOFT reboot, the operating system is signaled + to restart. This allows for a graceful shutdown of all + processes.
+ This schema file defines faults that may be raised by the
+ Cloud Servers API. These faults are derived from the CloudServersAPIFault. Most faults extend this type
+ without adding any additional attributes or elements. The only
+ exception is the OverLimitAPIFault which adds a
+ retryAfter attribute. Because all faults
+ extend a standard base type, it should be possible to capture
+ all API faults with a single catch statement.
Faults are associated with a default HTTP status code that + corresponds to the particular fault type. For example an <itemNotFound> element is associated with the + HTTP status code 404. Some elements, the <cloudServersFault> element for example, may be + associated with multiple status codes. It is also possible for + multiple fault elements to be associated with the same default + code. The examples below showcase the default status codes for + each element type. Note that these default codes are not part + of the formal schema. In practice, however, an element type + will likely be associated with its corresponding default + status code.
+A generic Cloud Servers API fault.
+The item or resource could not be found.
+The operation is not allowed because the corresponding + server is in a build state.
+There is not enough capacity to honor the request.
+The operation is not allowed because the corresponding + server is being re-sized or backed up.
+The re-size operation is not permitted.
+The API service is currently unavailable.
+Insufficient privileges to honor the request, perhaps an + authentication token needs to be obtained or renewed.
+The request is malformed.
+The Content Type of the request is not supported.
+The HTTP method (or verb) is not + supported by the corresponding resource.
+The operation is currently not implemented.
+A human readable message that is appropriate for + display to the end user.
+The optional <details> element may contain + useful information for tracking down errors (e.g a stack + trace). This information may or may not be appropriate + for display to an end user.
+The HTTP status code associated with the current fault. +
+An optional dateTime denoting when an operation + should be retried.
+This schema file defines a Server and all internal + entities related to servers including: Addresses, ShareIPs, Files, + and MetaData.
+Common types used by multiple entities and possibly + spanning several types of requests.
+The element defines a server.
+A collection of servers.
+The element defines list of addresses (public and + private).
+The element defines a list of public addresses.
+The element defines list of private addresses.
+The element defines request to share a public IP address. +
+The element defines request to add an IP address.
+The element defines response that returns an added IP + address.
+A server is a virtual machine instance in the Cloud + Servers system. Note that this complex type defines all + elements and attributes as optional because a server + instance may take many different forms depending on the + operation. When creating a server, for example, the name, + imageId, and flavorId attributes are required. In addition, + optional metadata and personality file elements may be + specified:
+The response to such a crate operation will include the + administration password, host ID, and addresses associated + with the server:
+When modifying a server only the name and administration + password should be specified as these are the only + attributes that are modifiable.
+A collection of meta data items associated with the + server.
+A server's public and private address.
+A collection of small files + used to personalize a new server instance.
+The name of the server.
+The ID of the server.
+The server's administration password.
+The ID of the image used to create the server.
+The current server flavor ID.
+A unique ID that identifies the physical host that the + VM is running on. This ID is unique per + account and not globally unique.
+The progress of the current server operation.
+The current state (or status) of + the server.
+An ID of the shared IP + group that the server belongs to.
+A collection of servers.
+A collection of metadata items.
+A MetadataItem is simply a name-value pair. The name is + specified in the key attribute and the value is included inline.
+A meta data name-value pair.
+A collection of files.
+A file is simply a full path along with base64 file + content. The name of the file is specified in the path + attribute and the file + content is included inline.
+Full file path.
+Public server addresses.
+Private server addresses.
+A collection of addresses.
+An IP address.
+This type is used to represent a request to share an IP + address.
+The shared IP group use to share the address.
+If true, the server is configured with the new address + though the address may not be enabled.
+This type is used to represent a request to add an IP + address.
+If true, the server is added and configured with the new + address though the address may not be enabled.
+The server is ready to use.
+The server is in an inactive (suspended) state.
+The server has been deleted.
+A request to perform a resize + action has been received. The operation is + pending.
+The server is being prepared to perform the resize + operation.
+The server is being resized.
+The server is waiting for the resize operation to be + confirmed so that the original server may be removed. +
+The server is in rescue mode.
+The requested operation failed, the server is in an + error state.
+The server is being built.
+The server is being restored.
+The server password is being changed.
+The server is being rebuilt.
+A shared IP address is being removed.
+An IP address is being shared, but not configured. +
+An IP address is being shared, and the server is being + configured with the new address.
+An IP address is being added, but not configured.
+An IP address is being added, and the server is being + configured with the new address.
+The server is going through a SOFT reboot.
+The server is going through a HARD reboot.
+The server is in an unknown state.
+Reserved for future use.
+Reserved for future use.
+Reserved for future use.
+Reserved for future use.
+Reserved for future use.
+