In David Noland’s “Show Me All the Blueprints” blog, you learn that you can deploy your blueprint on clouds such as AWS and Azure, as well as XenServer, vSphere, or Hyper-V running in your own datacenter using Citrix Lifecycle Management.
Before you can deploy a blueprint on XenServer, vSphere, or Hyper-V running in your own datacenter, however, you need to create a resource location and assign a machine as the connector to the hypervisor in the cloud platform. Once you have the resource location setup, you can use the out-of-box or your own blueprint to launch servers.
You can monitor the server performances and also configure the monitoring options in the Details of the blueprint deployment on the CLM Manage page. But how about if I want to monitor the connector of the resource location?
It is fairly easy. You can create a blueprint to do the job.
Step 1: Create the blueprint
- From the Lifecycle Management menu bar, click Design & Deploy.
- Click New Blueprint.
- Enter the name of the blueprint as Connector.
- Click on the Deploy
- Expand the Cloud Step in Blueprint Designer panel on the left, drag the Server step and drop it in STEPS & BLUEPRINTS section under Runs On tab in the Design
- Click Save to save the blueprint.
Step 2: Deploy the blueprint
- From the menu bar, click Design & Deploy. You can also click Deploy from the Blueprint Designer and go to step 4.
- Find the blueprint from the list.
- Move the pointer over the blueprint and click Actions > Deploy.
- Click Start deployment setup.
- Enter a deployment name and click Next.
- Select All Existing Machines as the resource location In the Resource Location page and click Next.
- Review the Pre-deployment Checklist and continue clicking on Next to Set up creation of new VMs or select existing VMs for the deployment
- Select the connector machine name from the drop-down list and click Next.
- Cancel saving the profile name.
- Click Deploy.
You can view the monitoring information once the blueprint being completed.
Another note: The Cloud Server step should be the first step in a blueprint. Since it lets you launching new VM’s or choosing existing servers to run the blueprint on. From the above example, you can use the same blueprint to launch a VM on cloud if you choose a resource location in step 6 of Deploy the blueprint step.