Importing resource templates from clouds
If you have a virtual system pattern on a cloud system, you can import that pattern as a resource template. This resource template is a pattern from which you can provision cloud resources.
- IBM Cloud Orchestrator version 2.4 or later
- IBM SmartCloud® Orchestrator versions 2.2 and 2.3
- IBM PureApplication® System version 1.0 or later
- IBM Workload Deployer version 22.214.171.124 or later
To connect to OpenStack and OpenStack-based clouds, SoftLayer®, Amazon Elastic Compute Cloud, VMware vCenter, or Microsoft™ Azure, see Connecting to clouds through the blueprint designer.
- Cloud Orchestrator version 2.4 or later
- PureApplication System version 2.0 or later
To connect to OpenStack and OpenStack-based clouds, SoftLayer, Amazon Elastic Compute Cloud, VMware vCenter, or Microsoft Azure, see Connecting to clouds through the blueprint designer.
- Click .
- Click Import Template from Cloud.
- Under Import Resource Template, specify a name for the new resource template.
In the Cloud Connection list, select the connection to the cloud
If you do not have a connection to the cloud system, click New Connection, and specify the information for the connection, including the host name and login information for the cloud system. For more information, see Connecting to clouds through IBM UrbanCode Deploy.
- If the cloud system supports VSys.next patterns (Cloud Orchestrator version 2.4 or later or PureApplication System version 2.0 or later), select the Use VSys.Next patterns check box to use these patterns.
- In the Cloud Resource list, select the virtual system pattern to use.
- Click Save.
- Optional: Edit the properties for the nodes
in the resource template:
- Click the new resource template to select it.
- Click an agent prototype, go to the Configuration tab,
and click Resource properties.This table shows the properties for the node, including virtual image properties such as memory, number of processors, and starting passwords. The window also shows the properties for each script package on the node.
- Edit the properties by clicking Edit next
to a property.You can use variables to refer to values that are not yet specified. For example, if you have a database node that is named
DB_nodeand an application node that is named
app_node, you might have to use the host name of the database node in the application node configuration. However, the host name is not set until the cloud system provisions the nodes. In this case, you can refer to the host name of the database node with the following variable:
For more information about using property variables, see the documentation for your cloud system.