This feature is available only if you have a VMware Aria Universal subscription. As an administrator, you can add existing on-premises vRealize Automation 7.5 or 7.6 catalog items from one or more business groups to the Automation Service Broker catalog. The vRealize Automation 7.5/7.6 catalog items are imported and added to the Automation Service Broker catalog.
After the 7.5/7.6 catalog items are added, your users can request the current on-premises catalog items or any Automation Service Broker items from a single cloud catalog.
If you are interested in this feature but you do not yet have a VMware Aria Universal subscription, you can subscribe as you add the integration.
Review the following considerations to decide if you want to import the vRealize Automation 7.5/7.6 catalog items.
- The only catalog items that are imported are vSphere machines and Amazon EC2 machines. You cannot import catalog items for other machine types. If your imported vSphere and Amazon EC2 catalog items have resource-level custom properties, the custom properties are not displayed in the catalog request form. Although the custom properties are not displayed, the default property values are honored during deployment. Custom properties at the business group level are not imported or honored.
- Catalog items with custom forms, XaaS forms, and business group custom properties are not imported.
- During deployment, you cannot cancel a deployment. You must wait for the completion of the provisioning process.
- The request timeout that is set in each project that is running these imported catalog items should match the deployment time for the cloud template in your VMware Aria Automation instance. The default timeout value is 120 minutes. This might not be sufficient time for a successful deployment. To change the Request Timeout value, select , and then click Provisioning.
- After the catalog item is deployed, you can only run Delete and Change lease day 2 actions. Even if you have other actions entitled in 7.5/7.6, you can only run those two actions. You must create a policy that entitles the project members to run the Deployment.Delete and Deployment.ChangeLease actions. This policy might be at the organization or project level. See How do I entitle deployment users to Automation Service Broker day 2 actions using policies.
- The vRealize Automation 7.5/7.6 lease policies are evaluated and honored. If you create an Automation Service Broker lease policy, it is evaluated and if more restrictive than the 7.5/7.6 lease, it is applied. If the Automation Service Broker policy is less restrictive, then the 7.5/7.6 policy is applied. For more about lease policies, see How do I configure Automation Service Broker deployment leases using policies.
Prerequisites
- Verify that you have the hostname URL for your vRealize Automation 7.5 or 7.6 instance.
- Verify that you have the vRealize Automation 7.5/7.6 name and credentials for the business group manager associated with catalog items that you are importing. The user must have the Catalog Administrator role and Infrastructure Architect role. These credentials are used to deploy the catalog items in vRealize Automation 7.5/7.6. They are also used to run day 2 actions on the deployments.
- Verify that you do not have any third-party certificates installed on your vRealize Automation 7.5/7.6 target instances.
Procedure
Results
The vRealize Automation 7.5/7.6 catalog items are imported into Automation Service Broker and shared in the catalog.
What to do next
- If the deployment fails, you must troubleshoot the failure in your vRealize Automation 7.5/7.6 instance.
- If you want to control how long a deployment can exist, create a lease. See Setting up Automation Service Broker policies.
- To provide more or fewer user inputs at request time, you can create a custom form. See Customize an Automation Service Broker icon and request form.