Deploying a template

Deploy a template in your Cloud Automation Manager environment.

Before you begin

• VMware templates need to have vmware-tools installed or else the operating system configuration post the deployment is not possible.
• For content runtime that got created prior to this release, you must migrate existing content runtime instance so that your middleware content instance deployments can continue to function as before. For more information, see Migrating content runtime created prior to Cloud Automation Manager 3.1.2.

Procedure

To deploy a template, follow these steps:

1. In the left-side navigation bar, click Library > Templates. The template library is displayed.
2. Click the template that you want to deploy.

3. Read the information about the template and click Deploy.

   You can see the template source code in the Template Source tab and the template parameters in the Parameters tab.

4. Specify the following details to deploy a template:

   • From the Select a Namespace section > Namespace drop-down list, select a namespace.

     Note: This step is applicable only for globally accessible templates. You cannot change the namespace during deployment for templates that are associated with a namespace.

   • Instance Name - Enter a unique name for the instance. The instance name must begin with an alphabet and must have a combination of only these characters: [a-zA-Z][a-zA-Z0-9_-]

   • Cloud Connection - Select the cloud connection from the drop-down list. It is a connection to the cloud provider where you want to deploy the template. The cloud connection list only contains the connections defined for the type of cloud provider where you can deploy the template. For information about cloud connections, see Managing connections. If you specify an SSH key, ensure that the key format is correct. The SSH key must start with the ssh-rsa string and the crypted string cannot contain any space. For example:

      <code class="hljs">ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAkZ5wvjWedYOYnkx2Mp2lnXgTxLKnvSYkvfb36P6JQFPhLY0cmgqY9Vi7XP/LsOFeLk6+7qSsInIILQ5iZ8 /uKsNxAOo2gZdyh5FKzaMDTsBbZggwqayjplADQ1C+QbHbprJLKSFRx98+ROb19u+CUIFL0FSmO03m1ZzZB3cYrEIiXql0vJp3DeSUSq/xCQ76qrXT7qzMUTfJdi3hPjtfTh1UIzC5buyR7jhe8FocDf5dn3KRCMzIUUrvd3zvyYHmcer0InmtK3e2OTvu8V4Xw2Mx4BrbpjBcDAmBShaHOhKq7IqT8qPWek46UxY9vUmnBbB9hP5jOn+ip3HSBJc3BQ==
     

   • Terraform Version - Select the Terraform version from the drop-down list. For information about creating the user defined Terraform versions, see Managing Terraform Versions.

   • If you are deploying an Amazon EC2 template, ensure that the image that you specify supports the T2 instance type. For more information, see T2 Instances .

   • If you have used shared parameters while defining your template, then in the Select Data Objects, select the value of all Data Objects associated with the defined Data Types. For the following scenarios, a message is displayed with appropriate information:

     • Your template has a invalid Data Type. A link is provided in the message to edit the template.

     • You do not have any data objects associated with the specified data type. A link is provided in the message to create data objects.

       For a sample procedure that deploys a template having shared parameters, see Deploying a template having shared parameters.

   • If you are deploying enterprise middleware templates from the Enterprise Middleware Repository, select a value for Advanced Content Runtime Chef. This Advanced Content Runtime Chef value is a Data Object that is associated to "advanced_content_runtime_chef" Data Type. If you want your advanced content runtime to be available to middleware template deployments that are in a different namespaces, then modify the data object to be globally available by using the following steps:

     1. Go to Shared Parameters > Data Objects.
     2. Open the newly created Data Object in edit mode.
     3. Move the Make this globally accessible toggle to "on".

     Note: For middleware templates, you can select an Automated Content Runtime that is not deployed on the same cloud provided proper network connectivity exists.

   • Enter all the required deployment parameters. It varies from one template to another based on the definition.

     Note: If you must enter the user ID, then ensure that it corresponds to your operating system and cloud connection. Otherwise, the deployment fails with an error message. For more details, see the General issues section of Troubleshooting deployment issues.

5. Click Deploy. The template instance window is displayed. The Ready state indicates successful deployment.

   In the template instance window, you can see the instance status, the instance information, the related resource details, and the related input and output variables. You can view or copy the instance logs and you can also access the template from which the instance was deployed.

   Note: Cloud Automation Manager stores the Terraform state file in its database in an encrypted format.

6. Alternatively, for templates based on IBM Workload Deployer patterns, you can verify the deployment status in IBM Workload Deployer server:
   1. Log in to IBM Workload Deployer.
   2. Go to Virtual System Patterns.
   3. Select the pattern that you exported and deployed in Cloud Automation Manager.
   4. Check values of In the cloud now. The deployed instance name in Cloud Automation Manager is available in this field.

In Cloud Automation Manager, you can export a pattern from IBM Workload Deployer and create a new template. For the procedure to create a template based on IBM Workload Deployer pattern, see Creating a template from IBM Workload Deployer pattern.