4.1.2. Create Server

Normal Response Code(s): 202

Error Response Code(s): cloudServersFault (400, 500), serviceUnavailable (503), unauthorized (401), badMediaType(415), itemNotFound (404), badRequest (400), serverCapacityUnavailable (503), overLimit (413)

Status Transition:	BUILD ACTIVE
	BUILD ERROR (on error)

This operation asynchronously provisions a new server. 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 /server/ id , which will return a progress attribute (0-100% completion).

 A password is randomly generated for you and returned in the response object. For security reasons, it is not returned in subsequent GET calls against a specified server ID.

You can also specify custom cloud server metadata at launch time. This metadata is stored in the API system where it is retrievable by querying the API for server status. The maximum size of the metadata key and value is each 255 bytes and the maximum number of key-value pairs that can be supplied per server is 5.

You can inject data into the file system of the cloud server instance. For example, you might want to insert ssh keys, set configuration files, or store data that you want to retrieve from inside the instance. This feature provides a minimal amount of launch-time personalization. If you require significant customization, create a custom image.

Follow these guidelines when you inject files:

The file injection might not occur until after the server is built and booted.

During file injection, any existing files that match specified files are renamed to include the bak extension appended with a time stamp. For example, if the file /etc/passwd exists, it is backed up as /etc/passwd.bak.1246036261.5785.

After file injection, all files have root and the root group as the owner and group owner, respectively, and allow user and group read access only ( -r--r----- ).

Servers in the same shared IP group can share public IPs for various high availability and load balancing configurations.

To share public IPs, complete the following steps:

If you intend to use a shared IP on the server being created and you do not need a separate public IP address, you can launch the server into a shared IP group and specify an IP address from that shared IP group to be used as its public IP. You can accomplish this by specifying the public shared IP address in your request. This is optional and is only valid if you specify the sharedIpGroupId attribute.

	Note
	The sharedIpGroupId attribute is optional. For optimal performance, use this attribute only when you intend to share IPs between servers.

<?xml version="1.0" encoding="UTF-8"?>
<server xmlns="http://docs.rackspacecloud.com/servers/api/v1.0"
	      name="new-server-test" 
	      imageId="1" 
	      flavorId="1">
  <metadata>
    <meta 
      key="My Server Name">Apache1</meta>
  </metadata>
  <personality>
    <file 
      path="/etc/banner.txt">
        ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBp
        dCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5k
        IGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVs
        c2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4g
        QnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRo
        ZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlv
        dSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vy
        c2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6
        b25zLiINCg0KLVJpY2hhcmQgQmFjaA==
    </file>
  </personality>
</server>

{
    "server" : {
        "name" : "new-server-test",
        "imageId" : 1,
        "flavorId" : 1,
        "metadata" : {
            "My Server Name" : "Apache1" 
        },
        "personality" : [
            {
                "path" : "/etc/banner.txt",
                "contents" : "ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBp dCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5k IGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVs c2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4g QnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRo ZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlv dSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vy c2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6 b25zLiINCg0KLVJpY2hhcmQgQmFjaA==" 
            } 
        ] 
    }
}

<?xml version="1.0" encoding="UTF-8"?>

<server xmlns="http://docs.rackspacecloud.com/servers/api/v1.0"
	id="1235" name="new-server-test" 
	imageId="1" flavorId="1"
	hostId="e4d909c290d0fb1ca068ffaddf22cbd0"
	progress="0" status="BUILD"
	adminPass="GFf1j9aP">
  <metadata>
    <meta key="My Server Name">Apache1</meta>
  </metadata>
  <addresses>
    <public>
      <ip addr="67.23.10.138"/>
    </public>
    <private>
      <ip addr="10.176.42.19"/>
    </private>
  </addresses>
</server>

{
   "server" : {
     "id" : 1235,
       "name" : "new-server-test",
       "imageId" : 1,
       "flavorId" : 1,
       "hostId" : "e4d909c290d0fb1ca068ffaddf22cbd0",
       "progress" : 0,
       "status" : "BUILD",
       "adminPass" : "GFf1j9aP",
        "metadata" : {
            "My Server Name" : "Apache1" 
        },
        "addresses" : {
            "public" : [
                "67.23.10.138"
            ],
            "private" : [
                "10.176.42.19"
            ] 
        }
   }
}