Add a Server to a Deployment

Objective

To add a new Server to an existing Deployment using a Rightscale ServerTemplate within the Deployment Servers Tab UI.

Prerequisites

• An existing deployment to hold your Server
• Existing cloud resources to assign to the Server, which may include:
  • Security group(s)
  • SSH Key
  • Elastic IP (if applicable)
• 'Actor' user role privileges

Steps

1. Navigate to the deployment you previously created (where you are adding the server) from the Manage > Deployments menu.
2. Click the Add Server action button. Next, you should select the cloud that the server/instance should be placed in. Use the "Select Cloud" drop down menu to make your choice. Remember that if you specified a default Availability Zone for your deployment, you should add the server to a cloud that includes that zone. (e.g., US-East)
3. Click Continue to add a server to your deployment. The Add Server Assistant opens. Use the following field descriptions to add a server (example shown is for Amazon EC2): 

(click to enlarge)

Field Descriptions:

• ServerTemplate - Your ServerTemplate forms the basis for your Servers.
  • ServerTemplate Name - Use this field to 'filter' for a ServerTemplate, which will then be displayed in the box on the right (ServerTemplates in Your Account).
  • Publisher - Select the desired publisher of the ServerTemplate to be used for the Server ('Any' by default).
  • Tags - Filter ServerTemplates by tags, which are normally placed on the shared/published ServerTemplate when it is committed and published.
  • Category - The category where the ServerTemplate lives in our Multicloud Marketplace
  • Sort by - How the ServerTemplate display should be sorted
  • ServerTemplate Revision - After selecting the desired ServerTemplate by its Radio Button, use this field to select the desired revision of the ServerTemplate.
• Server Details
  • Server Nickname - The Server's Nickname, as it will appear in the Deployment
  • MultiCloud Image - Select the MCI to use or leave as 'inherit from the ServerTemplate' (default).
  • Instance Type - Select the Instance Type (e.g., small, medium, large, etc.) or use 'inherit from the MultiCloud Image' (default)
  • EBS Optimized - The instance will be available to connect to and fully utilize provisioned IOPS EBS volumes. This option requires an additional charge per instance.
  • IAM Instance Profile Name or ARN - Enter the Identity and Access Management (IAM) Instance Profile name. If you prefer, you can enter the Amazon Resource Name (ARN) in the ARN format (arn:aws:service:region:account:resource). IAM roles contained in the Instance Profile will be assigned to the server instance at launch time. For additional information on AWS IAM see What is IAM?
  • Datacenter / Zone - Select what Availability Zone (EC2) or Datacenter this Server should be in.  Recall that there are additional charges for traffic across zones in certain cloud environments.  Servers are typically placed in the same zone, unless the Deployment is working towards high availability across different zones. Some clouds have multiple zones or regions.
  • Subnets - If this option is available, it usually indicates that you are using an EC2-VPC only account, so the account has a default VPC assigned to it. Select the VPC subnet to be used with this server, or use the 'cloud default' subnet.
  • SSH Key - Specify the (previously created) SSH Key to use as the launch key for the Server.
  • Security Group - Select the (previously created) Security Group (or Groups) to use for security purposes.
  • IP Address - Specify what Elastic IP (or none) to use for the Server.  

4. Click Confirm, then Finish after you have filled out all of the necessary the fields. The Server should now be added to the Deployment.

See also

• Create an SSH Key
• Create Elastic IPs
• Create a Security Group