Application Services registers a cloud provider by connecting to a vRealize Automation business group.

About this task

A vRealize Automation business group associates users with a set of services and resources, often corresponding to a business, department, or other organizational unit. Each business group can have access to one or more vRealize Automation blueprints used to request machines. These blueprints can belong to one or more business groups. To request machines, a user must belong to at least one business group. The machine resource information in the vRealize Automation blueprint is added manually or obtained from the cloned or linked cloned vSphere template.

Prerequisites

  • Log in to Application Services as an application cloud administrator.

  • Verify that vRealize Automation 6.1 or later is installed and configured.

  • Verify that the vRealize Automation business group that you plan to use with Application Services is created and configured.

  • Verify that you registered Application Services to vRealize Automation by using the CLI. See Register Application Services to vRealize Automation.

  • Verify that at least onevRealize Automation blueprint is available in the business group for the Application Services cloud provider to connect to. This blueprint must point to a virtual machine template that meets the Application Services requirements. See Virtual Machine Requirements for Creating vRealize Automation Custom Templates.

Procedure

  1. On the Application Services title bar, click the drop-down menu and select Clouds > Cloud Providers.
  2. Click the Add icon (Add).
  3. Complete the cloud provider information.

    For vRealize Automation 6.0 or later, when you register Application Services to vRealize Automation, the host name and business group name get populated for the logged-in user.

    Option

    Description

    Name and Description

    Include the vRealize Automation business group name in either of these fields. The text from these fields appears in the Deployment Profile wizard under the Cloud Provider column.

    Cloud Provider Type

    vCAC, vCloud, and EC2 are the supported types.

    vCAC Infrastructure IP/Host Name/URL

    Display the IP address or host URL for the registered vRealize Automation server. The field is read-only.

    Examples of a secure vCAC IP are https://192.0.2.115 and https://192.10.1.113:443.

    An example of a secure Host Name URL is https://vcac.it.vmware.com.

    User Name and Password

    Add business group manager credentials for the selected business group in vRealize Automation.

    The domain name is required when you enter the user name. An example of a user name is myname@mycompany.com.

    Business Group

    Select a business group from the Business Group drop-down menu. The menu contains the business groups of the logged-in user.

    Sharing

    Displays the Private status of the cloud provider. This value is always Private and is read-only.

  4. To test whether the values you entered are correct, click Validate Connection.
  5. Click Save to register the cloud provider.

    If required entries for the cloud provider were invalid or left blank, you are prompted to correct them.

  6. To register vRealize Automation blueprints, click Edit.
  7. In the Templates section, click Add.
  8. Select the check boxes next to one or more cloud templates or vRealize Automation blueprints in the list, and click OK.

    Only global blueprints and blueprints that belong to the selected business group of the cloud provider appear.

    The templates you registered are added to the list of cloud templates that you can choose from when you map a logical template to a cloud template.

  9. To change existing information for a vRealize Automation cloud provider, click Edit. in the toolbar, make your changes, and click Save.
  10. Click Save.

    As a best practice, refresh the cloud template information, vRealize Automation Infrastructure IP, and the host name when you edit a vRealize Automation cloud provider.

    Note:

    If the vRealize Automation blueprint name changes in the vRealize Automation environment, the new blueprint name does not appear in the Application Services user interface. The new blueprint name is updated only in the cloud template meta data.

Results

The cloud provider is registered and its templates are available for use in Application Services.

What to do next

Map the vRealize Automation cloud template to the Application Services logical templates. See Add a Logical Template to the Library.

Create a deployment environment to deploy an application to the vRealize Automation environment. See Create a vRealize Automation Deployment Environment.