- Step 1: Select the blueprint
- Step 2: Name the deployment
- Step 3: Select the resource location
- Step 4: Review deployment requirements
- Step 5: Scale the deployment
- Step 6: Select machines for deployment
- Step 7: Enter deployment parameters
- Step 8: Create a deployment profile
- Step 9: Deploy the blueprint
Step 1: Select the blueprint
- On the Library page, point to the blueprint you want to deploy.
- Under Actions, click Actions > Deploy. The blueprint description page appears.
- Click Start deployment setup. The Profile page appears.
Step 2: Name the deployment
- In Deployment name, enter a friendly name for your deployment.
- In Deployment profile, select an existing deployment profile with the deployment settings you want to use.
Note: Deployment profiles are settings that are saved from a previous blueprint deployment. The deployment profile you select must match the blueprint you are deploying and the resource location you want to use. You cannot use a deployment profile that was created using a different blueprint or a different resource location. For example, you cannot use a deployment profile created from a previous deployment of XenDesktop to an AWS resource location to deploy the same blueprint to a XenServer resource location. You can delete unused deployment profiles from the list of available profiles. To delete a deployment profile, point to the profile, click the X icon, and click Delete.
- Click Next. The Resource Location page appears.
Step 3: Select the resource location
- In Resource Location, select the Amazon EC2 resource location where you want to deploy the blueprint. If the resource location you want to use does not exist, click Add Resource Location and follow the steps described in Add an Amazon Web Services resource location.
- Click Next. The Pre-deployment Checklist appears.
Step 4: Review deployment requirements
The Pre-deployment Checklist displays recommendations for provisioned VMs, VM template requirements, and deployment parameters for your blueprint based on the resource location you previously selected. To save time configuring your deployment, you can download the deployment parameters, enter the appropriate values, and import the updated parameters later in the deployment process (see section Step 7: Enter deployment parameters in this topic).
- Review each section of the Pre-deployment Checklist to verify your VM templates and resource location meet the stated requirements.
- (Optional) Click Export parameter list to download the deployment parameters in CSV format. Enter the appropriate values using a text editor or spreadsheet application. You can import these parameters on the Configuration page of the deployment process.
- Click Continue. The Scale page appears.
Step 5: Scale the deployment
If the blueprint supports autoscaling, you can turn it on or off and specify the minimum and maximum scaling values. If the blueprint does not support autoscaling, Smart Tools displays "N/A" in each machine tier. You can enable and configure autoscaling for a blueprint using the Blueprint Designer. For more information about enabling autoscaling in a blueprint, see Manage scaling.
- In VMs, enter the number of virtual machines in each VM tier in the blueprint. The default number of VMs is 1.
- Click Next. The Size page appears.
Step 6: Select machines for deployment
When you deploy the blueprint, Smart Tools can provision new VMs in your resource location or use existing machines that you specify for each machine tier in the blueprint. By default, the Create new VMs option is selected.
Note: If you want to use existing machines, the machines must have the Smart Tools Agent installed; otherwise, Smart Tools cannot locate them in your resource location.
To create new VMs during deployment
- Ensure Create new VMs is selected.
- Select the Amazon EC2 resource location from the list. The Configure VM dialog box appears.
- On the Choose a Region page, Select the appropriate region where the machine instance will run and click Next. The US East (Virginia) region is selected by default.
Note: Amazon EC2 offers multiple geographically dispersed regions where you can run instances. The distance of a region from end users of the service might impact network latency. For more information about EC2 regions, see the Amazon EC2 Product Documentation web site.
- On the Choose an AMI page, select an Amazon Machine Image (AMI) from the listed EC2 images.
Note: Citrix recommends selecting a preconfigured image from the Quick Start tab. However, you can also choose your own custom images in the My AMIs tab; or choose from thousands of community-submitted Linux and Windows AMIs (with different application stacks included) in the Community AMIs tab. If you select a custom or Community Windows-based AMI, verify the image has the EC2Config service installed.
- On the Instance Details page, configure the instance and then click Next:
- VM Name: Specify a friendly name.
- Suffix start: Specify the number at which Smart Tools will start numbering instances when they are provisioned. If the specified number already exists in your resource location, Smart Tools will use the next number in sequence.
- Network: Specify the virtual private cloud (VPC) where you want to run the instance. If the VPC you want to use does not exist, select Create VPC with public and private subnet and then perform the following actions:
- In VPC Name, enter a friendly name for your VPC.
- For the Public and Private subnets, enter the appropriate IP ranges and select the appropriate availability zones, if applicable, for your resource location. Some advanced production environments may deploy instances in multiple availability zones for failover purposes. For less critical deployments with fewer instances choose "No Preference." (Note that data transfer between instances in different availability zones may incur additional costs to your Amazon account.) For most Citrix-provided blueprints, the default values are sufficient.
- In NAT Instance Type, select the appropriate configuration for the machine that will be deployed as the NAT for the VPC. By default, T2 Micro is selected. If a NAT instance does not exist already in your resource location, Smart Tools will deploy one when it creates the VPC. By default, this instance is called "Citrix Nat Instance" and it is deployed to the VPC's public subnet.
- In NAT Instance Key Pair, select a key pair, if applicable, that Smart Tools will use to deploy the NAT instance. By default, No Key Pair is selected. Selecting a key pair is not required. However, if you intend to connect to the instance in the future, you must select a key pair.
Important: When Smart Tools creates the new VPC, Smart Tools will also allocate a new Elastic IP for the NAT instance. Therefore, be sure you have not reached the Elastic IP limit of five addresses for your AWS account.
- If using an existing private key, select the PEM file that you saved when you created the key pair and click Upload to attach it to the deployment configuration.
- To create a new key pair, select Create Key Pair, enter a friendly name, and then click Create Key. Smart Tools displays your private key, which you must save and keep in a safe place. The key pair you create is tied to a specific region and cannot be shared among regions. If the region you select for your deployment has no corresponding key pair, you must create one from the Credentials page. For more information on EC2 key pairs, see the Amazon EC2 Product Documentation web site.
- Instance: If applicable, select an Elastic IP for the instance. By default, No Elastic IP is selected. To allocate a new Elastic IP, select Allocate new Elastic IP address for this instance.
Note: If the maximum number of Elastic IP addresses is reached, use your AWS console to release an Elastic IP.
- Group Name: Select a security group for your instance. By default, the default group is selected.
Note: If the security group is not configured to allow Smart Tools to install the Smart Tools Agent on the instance, Smart Tools can modify the group during deployment. For more information about security groups, see the Amazon EC2 Product Documentation web site.
Note: If you have multiple server steps configured in your blueprint, you can copy VM configuration data from one server tier to another during blueprint deployment. To copy the VM configuration data to other VM tiers, select Copy this configuration to other VM tiers. If the blueprint includes recommended configuration parameters for these tiers, the parameters are used appropriately.
To use existing machines
- Select Use existing machines.
- Select a machine from the list. After you select a machine, Smart Tools displays the IP address.
- Click Next. The Configuration page appears.
Step 7: Enter deployment parameters
- For each section of the blueprint, enter the appropriate parameters that Smart Tools will use to deploy the blueprint.
- (Optional) If you downloaded the deployment parameters from the Pre-deployment Checklist in Step 4: Review deployment requirements," under Import parameters, click Choose File to upload the updated parameters in CSV format.
- Click Next.
Step 8: Create a deployment profile
Deployment profiles enable you to reuse your current deployment settings in the event you want to deploy the blueprint again to the same resource location. Using a deployment profile, you skip several steps in the deployment process, saving time and minimizing input errors. Creating a deployment profile is optional.
- Enter a friendly name for the profile.
- (Optional) Enter a description.
- Click Save. If you do not want to create a profile, click Cancel.
Step 9: Deploy the blueprint
- Review the deployment summary.
- Click Deploy.
After the deployment begins, Smart Tools displays the status of the deployment in the Deployment Details page. The Deployment Details page includes the real-time progress of each step in your blueprint. Depending on machine availability and the complexity of the blueprint, the deployment might take some time to complete, and some blueprint steps might take longer than others.