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 request cloud resources.

Before you begin

Create a virtual system pattern on a compatible cloud system. Each node in this pattern must include the Install IBM® UrbanCode Deploy Agent script package. See Creating cloud patterns for resource templates.
The following cloud systems are supported:
  • IBM SmartCloud® Orchestrator version 2.2 or later
  • IBM PureApplication™ System 1.0 or later
  • IBM Workload Deployer version 3.1.0.6 or later

Procedure

  1. Click Resources > Resource Templates.
  2. Click Import Template from Cloud.
  3. Under Import Resource Template, specify a name for the new resource template.
  4. In the Cloud Connection list, select the connection to the cloud system. 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 Cloud connections.
  5. In the Cloud Resource list, select the virtual system pattern to use.
  6. Optional: In the Teams fields, specify the access information for the new resource template.
  7. Click Save.
  8. Optional: Edit the properties for the nodes in the resource template:
    1. Click the new resource template to select it.
    2. 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 CPUs, and starting passwords. The window also shows the properties for each script package on the node.
    3. 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 named DB_node and an application node named app_node, you might need 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:
      ${DB_node.hostname}

      See the documentation for your cloud system for further information about using property variables.

    The table of properties for a node in the resource template

Results

The template opens, displaying the resource hierarchy for the template. The template contains a top-level folder and one agent prototype for each node in the pattern, as shown in the following figure.
The complete resource template, showing a main folder that contains two agent prototypes

What to do next

Create an application blueprint from this resource template. See Creating application blueprints.

Feedback