1. If the server is running, click the Stop button.
2. Click the Edit button.
3. Edit the server details as required.
4. Click the Save button.

Shut the server down immediately and unsafely

Click the Console button.

Duplicate the server

1. If the server is running, click the Stop button.
2. Click the Duplicate button.

1. If the server is running, click the Stop button.
2. Click the Delete button.

1. Click on the Hypervisor Settings section.
2. In the Customise column, select the check box of the parameter you want to modify.
3. Edit the parameter using the appropriate drop down menu.
4. If required, force a change to be inherited by resources lower down the hierarchy by clicking the Lock button. For more information about the hierarchy, see Hypervisor specific settings.
5. Click the Update button.

1. Click on the Disks section.
2. Do one or more of the following:
   
   • To add a new disk, click the Add Disk button.
   • To manage or delete an existing disk, click either the Manage or Delete button next to the required disk. For more information about managing disks, see Managing a Disk.
   • To change the boot disk for the server, click and drag the required boot disk to the top of the list using the four-pointer
      button.

View and manage the Network Interface Cards (NICs) attached to the server and add more if required

1. Click on the NICs section.
2. Do one or more of the following:
   

   • To add a NIC, enter the required name for the NIC, select the network to create it on and click the Addbutton.

     If you select Auto from the IP address drop down menu, the server's network interface is allocated an IP address from the first available subnet, regardless of your selection from the Subnet drop down menu.

   • To manage a NIC, click the Manage button next to the required NIC.
   • To delete a NIC, click the Delete button next to the required NIC.
   • To change the order of your NICs, click and drag the NICs into the required order using the four-pointer button.
     

1. Click on the Firewalls section.
2. Firewalls can be created from existing templates or from new templates. To create a firewall from a new template:
   
   1. Select the IP address of the server from the IP Address drop down.
   2. In the drop down below the IP Address drop down, select New firewall template.
   3. Specify the name you want to give the firewall template.
   4. If required, edit the default IN and OUT actions for the firewall. Exceptions to these rules can be defined when managing the firewall. For more information, see Managing a Firewall Template.
   5. Click the Add button.
3. To create a firewall from an existing template:
   
   1. Select the IP address of the server from the IP Address drop down.
   2. In the drop down below the IP Address drop down, select Existing firewall template
   3. Click the Add button.

Manage the Chef settings for the server

1. Click on the Chef Settings section.
2. Select whether or not to use Chef with the server using the Enable Chef check box.
3. Complete the following fields using information from your Chef account:
   
   
   • Chef Repository URL
   • Chef Server URL
   • Node Name
   • Environment
   • Validation Name
   • Validation Key
   • Recipes
   • Roles
      

4. Click the Save button.
   When the server first boots, a trigger compiles this information and sends it to the Chef server specified using the Chef Server URL field.

   This information is passed to the Chef server on first boot only. Subsequent reboots will not affect the information held by the Chef server and hence the configuration applied to the server will not reflect changes to these values after the server is first booted.

View and manage SSH keys present in the server's metadata

1. Click on the SSH Keys section.
2. Do one or more of the following:
   
   • To add an existing SSH key to the server's metadata:
     
     1. Select the required SSH key from the drop down. If the required SSH key is not displayed, it can be created from your public key. For more information, see Creating an SSH Key.
     2. Click the Add button. The SSH key is added to the server the next time the firstboot script is run.
   • To manage an SSH key present in the server's metadata, click the Manage button next to the required SSH key. Changes to the SSH key will take effect the next time that the firstboot script is run.
   • To remove an SSH key from a server's metadata, click the Detach button next to the required SSH key. The SSH key is removed the next time the firstboot script is run.

1. Click on the Deployment Instances section. 
2. Do one or more of the following:
   
   • To add the server to a new deployment instance, select New Deployment Instance from the Add To drop down, enter a name for the new deployment instance and click the Save button.
   • To add the server to an existing deployment instance, select Existing Deployment Instance from the Add To drop down, select the required deployment instance from the Instance drop down and click the Save button.

1. Click on the Related Resources and UUIDs section. 
2. To manage a related resource or UUID, click the Manage button next to it.

1. Click on the Metadata section. 
2. Edit the metadata as required. 
3. Click the Save button.

• Permission - Whether to allow or deny the user or group the ability to perform the action specified using the Capability drop down menu.
• Type - Whether the permission applies to a group, or an individual user.
• User/Group - The user or group to which the permission applies.
• Capability - The action that the user or group is specifically allowed or denied the ability to perform.
• Resource - The type of resource that the Capability pertains to, for example server, disk, or user.