You can add compatible services and scripts to custom or sample logical templates when you model an application blueprint. You can map the logical templates to actual cloud templates from vCloud Director, vRealize Automation, or Amazon EC2. Logical templates allow an application blueprint to remain cloud agnostic.

About this task

As part of the logical template definition, you can describe which services are already installed in the template with the operating system. Typically, in IT organizations, a few performance monitoring agents or virus scanners are installed in a template. Also, for example, vFabric tc Server might be preinstalled in the logical template to accelerate deployments. If you always use a particular service when you deploy a logical template, you can preinstall it to avoid having to add it for every deployment.

You can share a logical template publicly or privately in a group. Sharing is supported at the component level and not at the individual version level.

Save your changes frequently. The Application Services user interface session expires after 30 minutes of inactivity. If the session expires, any changes that were not saved are lost.

Prerequisites

Procedure

  1. On the Application Services title bar, click the drop-down menu and select Library > Logical Templates.
  2. Click New.
  3. Set the name of the logical template, add a description, and click Save.

    To keep track of which cloud template or operating system you are using, include the name of the cloud template or operating system.

  4. Click Create LT Version to create a logical template version.

    You can create multiple versions for a logical template.

    A page opens for creating a logical template version.

  5. Complete the template version information.

    Option

    Description

    Name

    Logical template version name stays the same.

    Version

    Add a qualifier to denote major and minor versions such as 1.2.1 or 1.0.1-CentOS56-32bit.

    Description

    Add detailed information about the logical template. For example, describe a script you are using or the amount of disk size required.

    Tags

    Categorize logical templates based on the functions that they provide. Application Services organizes the templates based on tags you see when you create a deployment blueprint for an application.

    Note:

    Only tags designated as Server Type appear in the drop-down menu.

    You can add multiple tags.

    To use a tag that is not in the list, click Cancel, and select Library > Tags to create a tag.

    Supported OS

    Specifies the operating system installed in the logical template. This OS information is used in the application blueprint to limit which services you can add to this template. Not all services run on all operating systems. For example, if you specify an Ubuntu operating system, when you use this template in a blueprint and try to add a service that is not compatible with Ubuntu, Application Services prevents you from adding that service.

    To use an operating system name that is not in the list, click Cancel, and select Library > Operating Systems to create an operating system name.

  6. Map a cloud template to the logical template.

    You can add multiple cloud templates to one logical template version or select different cloud templates for different clouds. Even if you are using the same cloud provider, you might need to select from different cloud templates at deployment time to allow for different template configurations.

    Duplicate cloud template and logical template mappings and empty rows are not saved.

    For example, with multiple cloud templates, you can use the same logical template. If you are deploying to a production environment, you can select a cloud template that has a large amount of disk space. For a test or staging environment, you can select a cloud template with a small amount of disk space.

    1. In the Cloud Provider Name column, click the down arrow to select a cloud provider.

      A list of cloud providers that you created appears.

    2. In the Cloud Template column, click the down arrow to designate a cloud template.

      Cloud templates that belong to the same group as the user appear in the drop-down menu. If the list of cloud templates is empty, the existing cloud templates do not belong to your group or a cloud template was not registered.

  7. (Optional) : To map multiple cloud templates to a logical template, repeat 6.
  8. (Optional) : Define a preinstalled service.
    1. In the Service Name column, click the down arrow to select a preinstalled service.
    2. To use a service that is not in the list, click Cancel, and select Library > Services to create a service and the action scripts it includes.

      If any preinstalled services are added to a logical template after creating a blueprint, the new preinstalled services are not added to the node.

  9. (Optional) : Add the new preinstalled services to the node.
    1. Drag the logical template with the preinstalled service to the application blueprint.
    2. Transfer the services and components to the new logical template.
    3. Recreate any applicable dependencies and delete the old template.
  10. When you finish creating the template, click Save.

Results

The logical template that you created is added to the Logical Templates page. The template also appears in the list of logical templates that you can include when you create a deployment blueprint for an application.

What to do next

Copy an existing logical template version, edit, or delete the template. See Maintain Logical Template Versions.