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 8.0.1 and later cloud templates to the Service Broker cloud catalog.
After you add the 8.0.1 or later cloud templates as catalog items, your users can request the current on-premises cloud templates or any Service Broker catalog item from a single cloud catalog. The single catalog provides your consumers with a uniform request experience when they might be requesting cloud templates developed on-premises, in the cloud instance, or from other content sources.
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 8.0.1 or later cloud templates as catalog items.
- cloud templates with custom resource types are not imported.
- During deployment operation, 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 cloud templates 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 run only the Delete, Change Lease, Power On and Power Off day 2 actions on the deployment. Even if you have other actions entitled in 8.0.1 or later, you can only run these actions. To ensure that your users can run these actions, you must create a policy that entitles the project members to run the Deployment.Delete, Deployment.ChangeLease, Deployment.PowerOff, and Deployment.PowerOn 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 Change Lease action sets the lease date on your vRealize Automation 8.x instance.
- Verify that you have the hostname URL for your vRealize Automation 8.0.1 or later instance. If you are integrating 8.1 or later and you have more than one organization, each organization has a unique URL. You must repeat this procedure for each organization, including creating an integration for each organization. The end result is still one catalog.
- Verify that you have the vRealize Automation 8.x user name and password that has Cloud Assembly administrator permissions. These credentials are used to deploy the catalog items in vRealize Automation 8.x. They are also used to run the allowed day 2 actions on the deployments.
- Verify that the cloud templates that you are importing are deployable and released in Cloud Assembly before you import them.
- If you want to share cloud templates that were created for another project with the members of this project, verify that you allow sharing in the Cloud Assembly cloud template settings.
- Configure the vRealize Automation Cloud integration.
You can configure an integration with on-premises vRealize Automation Cloud 8.0.1 and later.
- Select .
- Click Add Integration and then click vRealize Automation 8.
- Enter a name that identifies this instance when you create the content source.
You cannot change the name after the integration is created.
- Enter the vRealize Automation 8.x URL.
- Select or add a Cloud Proxy.
- Enter a user name and password for user account that has the Cloud Assembly administrator user role in your 8.0.1 or later instance.
- To validate the credentials and URL, click Validate.
- Click Add.
- Import the cloud templates.
- Select .
- Click New, and then click vRealize Automation 8.x Cloud Templates.
- Enter the Name for this content source so that you can identify it when you share the content.
- Select the Source vRA 8.x integration that you configured in the previous step.
- Select the Source project that includes the vRealize Automation 8.0.1 or later cloud templates that you want to import.
If you want to import cloud templates for more than one project, you must create a different content source for each project.
- Click Create and Import.
- Add a project so that you can share the imported cloud templates with Service Broker users.
If you have a project that includes the users that must be able to deploy the imported cloud templates, you can use an existing project. Otherwise, create a new 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.
- Click Create.
- Share the imported cloud templates with a project.
The people that you want to have permission deploy the imported 8.0.1 or later cloud templates, but be a member of the selected project.
- Select .
- Select the project that includes the users who must have permission to deploy the imported 8.0.1 or later items.
- 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 8.x content source, or you can expand the source trees and select individual items.
- Click Save.
- Verify that the cloud template catalog items are available in the catalog to members of the selected project.
The provisioning process begins and the Deployments tab opens with your current request at the top.
- Click Catalog, locate the imported workflow, 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 8.x deploys the catalog item to the infrastructure allocated in the application.
- Click Deployments 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, Change Lease, Power Off, and Power On. Your vRealize Automation 8.0.1 or later instance runs the actions on the target system. Your project members must be entitled to run the actions.
- Click Deployments tab and locate you successfully deployed catalog item.
- Click the Actions menu on the right side of the card.
Change Lease, Delete, Power Off, and Power On are the expected actions. Depending on your intent for the item, run one of the actions.
The vRealize Automation 8.0.1 or later cloud templates 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 8.0.1 or later 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. The request form changes are applied to the vRealize Automation Cloud requests, not your 8.0.1 or later cloud templates.
- To apply approval policies to the requests, you can create approval policies for two possible criteria: requestedBy and catalogItem. No other criteria can be applied to these imported cloud templates. See How do I configure Service Broker approval policies.