diff --git a/api-ref/src/wadls/compute-api/src/v2/common.ent b/api-ref/src/wadls/compute-api/src/v2/common.ent
index ccdd7c3b6..1ec83b4b4 100644
--- a/api-ref/src/wadls/compute-api/src/v2/common.ent
+++ b/api-ref/src/wadls/compute-api/src/v2/common.ent
@@ -280,9 +280,9 @@
To provision the server instance with a NIC
for an already existing port, specify the
port-id in the port attribute in
- a networks object. Required if
- you omit the uuid
- attribute.
+ a networks object. The port
+ status must be DOWN. Required if
+ you omit the uuid attribute.
Enables booting the server from a volume
- when additional parameters are given.
+ when additional parameters are given.
+ If specified, the volume status must be
+ available, and the volume
+ attach_status in OpenStack Block Storage DB must
+ be detached.
+
Specifies the guest server disk file system format, such
as "ephemeral" or "swap".
-
diff --git a/api-ref/src/wadls/compute-api/src/v2/wadl/os-compute-2.wadl b/api-ref/src/wadls/compute-api/src/v2/wadl/os-compute-2.wadl
index c578fd63b..16e43efda 100644
--- a/api-ref/src/wadls/compute-api/src/v2/wadl/os-compute-2.wadl
+++ b/api-ref/src/wadls/compute-api/src/v2/wadl/os-compute-2.wadl
@@ -342,7 +342,7 @@
Creates a server.
- This operation asynchronously provisions a new server. The progress of this
+ The progress of this
operation depends on several factors including location of the requested image,
network i/o, host load, and the selected flavor. The progress of the request can be
checked by performing a &GET; on /servers/id, which will
@@ -354,6 +354,36 @@
attributes through subsequent &GET;s on the server.
You can boot a server from a volume by including block-device-mapping-v2
parameters in the create request.
+ Preconditions
+
+ The user must have enough server quota remaining
+ to create the number of servers requested.
+ The connection to the Image Service is
+ valid.
+
+ Asynchronous Postconditions
+
+ With correct permissions, you can see the server
+ status as ACTIVE through API calls.
+ With correct access, you can see the created
+ server in the compute node that OpenStack Compute manages.
+
+
+ Troubleshooting
+
+ If the server status remains BUILDING
+ or shows another error status, the request failed. Ensure you meet
+ the preconditions then investigate the compute node.
+
+ The server is not created in the compute node
+ which OpenStack Compute manages.
+ The compute node needs enough free resource to
+ match the specified resource of the server creation request.
+
+ Ensure the scheduler selection filter can
+ fulfill the request with the available compute nodes that
+ match the filter's selection criteria.
+
@@ -573,6 +603,10 @@
Gets details for a specified server.
+ Preconditions
+
+ The specified server must exist.
+
@@ -590,6 +624,10 @@
Updates the editable attributes of the specified server.
+ Preconditions
+
+ The specified server must exist.
+
@@ -668,6 +706,42 @@
Deletes a specified server.
+ Preconditions
+
+ The specified server must exist.
+ Anyone can delete a server when the server's
+ status is not locked.
+ You can delete a server which status is
+ not locked.
+ If the specified server is locked, you need to
+ have administrator privileges to delete the server.
+
+ Asynchronous Postconditions
+
+ With correct permissions, you can see the
+ specified server status as DELETED through API
+ calls.
+ The port attached to the specified server
+ is deleted.
+ The server is deleted from the list of
+ servers returned by an API calls.
+
+ The server managed by OpenStack Compute is
+ deleted on the compute node.
+
+ Troubleshooting
+
+ If server status remains in deleting
+ or shows another error status, the request failed. Ensure you
+ meet the preconditions then investigate the compute backend.
+
+ The request returns the HTTP 409 status code
+ when the server is locked even if you have a correct permissions.
+ Ensure you meet the preconditions then investigate the server
+ status.
+ The server managed by OpenStack Compute is not
+ deleted from the compute node.
+
&commonFaults; &getFaults;