This feature is available only if you have a VMware vRealize Cloud 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 Service Broker catalog. The vRealize Automation 7.5/7.6 catalog items are imported and added to the 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 Service Broker items from a single cloud catalog. This single catalog provides your catalog consumers with a seamless request experience across multiple instances of vRealize Automation.
If you are interested in this feature but you do not yet have a vRealize Cloud 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 8.x 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 Provisioning. , and then click
- 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 Service Broker day 2 actions using policies.
- The vRealize Automation 7.5/7.6 lease policies are evaluated and honored. If you create a Service Broker lease policy, it is evaluated and if more restrictive than the 7.5/7.6 lease, it is applied. If the 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 Service Broker deployment leases using policies.
- 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.
- Configure the vRealize Automation integration.
You can configure an integration with on-premises vRealize Automation 7.5 or 7.6.
- Select .
- Click Add Integration and then click vRealize Automation.
- Enter a name that identifies this instance when you create the content source.
- Enter the URL for your vRealize Automation instance.
- Select or add a Cloud Proxy.
- Enter a user name and password for a business group manager who has the Catalog Administrator role and Infrastructure Architect role in your 7.5/7.6 instance.
- To validate the credentials and URL, click Validate.
- Click Add.
- Import the catalog items.
- Select .
- Click New, and then click vRA 7.x Catalog Items.
- Enter the Name for this content source so that you can identify it when you share the content.
- Select the Source vRA integration that you configured in the previous step.
- Select the Source vRA Business group that is entitled to the catalog items in vRealize Automation 7.5/7.6.
If you want to import catalog items for more than one business group, you must create a different content source for that group.
- Click Create and Import.
- Add a project so that you can share the imported catalog items with Service Broker users.
If the project includes the users that must be able to deploy the imported catalog items, you can use an existing project.
- In Service Broker, select , and then click New Project.
- Enter the project information on the Summary tab.
- Click the Users tab and then click Add Users.
To add project users, the individuals or the groups must already be active service organization users.
You are not required to configure any project infrastructure. The requests for these catalog items use the 7.5/7.6 infrastructure that is associated with the business group that you used to create the vRealize Automation integration in a previous step.
- Click Create.
- Share the imported catalog items with a project.
The people that you want to have permission deploy the imported 7.5/7.6 catalog items, but be a member of the selected project.
- Select , and create a new content sharing policy.
- Enter a name for the content sharing policy.
- In the Scope list, select the project that includes the users who must have permission to deploy the imported 7.5/7.6 items.
- In the Content sharing section, click Add Items and then select one or more catalog items to share with the project members.
You can select all the items imported from the vRealize Automation 7.5/7.6 content source, or you can select individual items. To select only particular items, select All Content in the Content Sources drop-down menu.
- In the Users section, select the users and user groups that you want to have access to the content.
You can share the content with all users and groups in the project, or you can select individual users and groups.
- Click Create.
- Verify that the imported catalog item is available in the catalog to members of the selected project.
The provisioning process begins and the Deployments page opens with your current request at the top.
- Click the Consume tab.
- In the Projects drop-down menu, select the project with which you shared the imported items.
You can select multiple projects.
- On the Catalog page, locate the imported catalog item, and review the projects to ensure that the project you configured is included.
- Click Request and provide any required information.
- Click Submit.
- Monitor the provisioning process to ensure that a catalog item runs successfully.
vRealize Automation 7.5 or 7.6 deploys the catalog item to the infrastructure allocated in the application.
- Select and locate your deployed request.
- Monitor the card status until it is successful.
- Verify that your users can run a day 2 action on the deployed catalog item.
Day 2 actions are changes that you can make to deployed catalog items. The deployment level actions might include Delete and Change Lease. Your vRealize Automation 7.5/7.6 instance runs the actions on the target system. Your project members must be entitled to run the actions. Review the information at the beginning of this article.
- Select and locate your successfully deployed catalog item.
- Click the Actions menu on the right.
Change Lease and Delete are the expected actions. Depending on your intent for the item, run one of the actions.
The vRealize Automation 7.5/7.6 catalog items are imported into 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 Service Broker policies.
- To provide more or fewer user inputs at request time, you can create a custom form. See Customize a Service Broker icon and request form.