7.3

What to do next
After you verify your work by provisioning the CentOS with MySQL catalog item, you can add additional
users to the entitlement to make the catalog item publicly available to your development and quality
engineering users. If you want to further govern the provisioning of resources in your environment, you
can create approval policies for the MySQL Software component and the CentOS for Software Testing
machine. See Scenario: Create and Apply CentOS with MySQL Approval Policies.
Managing Deployed Catalog Items
You can view and act on provisioned deployments, including machines, load balancers, networks, and
other deployment resources.
Running Actions for Provisioned Resources
The actions that are available for a provisioned resource depend on the type of resource, how the action
was configured and made available for provisioned items, and the operational state of the item.
The configured actions that are available for a provisioned machine or deployment appear in the Actions
menu for the selected resource on the Items tab.
If the item was provisioned by IaaS using an IaaS machine blueprint, the list of available actions is
determined by what was selected on the Actions tab for the machine type component when the blueprint
was created, and then by what is applicable based on machine type or state.
If the item was provisioned using an XaaS blueprint, the resource actions must be created, published,
and entitled in the same service that is used to provision the item. The list of available actions is
determined by the item type and the current state of the item.
The available actions for an item that was provisioned as an IaaS machine might also include XaaS
resource actions if the actions are mapped to the item.
Action Menu Commands for Provisioned Resources
Actions are changes that you can make to provisioned resources. The vRealize Automation actions are
used to manage the life cycle of the resources.
The commands on the Action menu for a provisioned resource include the actions specified on the
blueprint and might include custom menu operations created by your service architects. The available
actions depend on how your business group manager or tenant administrator configured the entitlement
that contains the resource on which the actions run.
You should not manage vRealize Automation-administered NSX objects outside of vRealize Automation.
For example, if you modify the member port of a deployed NSX load balancer in NSX, rather than in
vRealize Automation, then NSX data collection breaks association between the deployed machine and its
otherwise associated load balancer member pool. Scale in and scale out operations also produce
unexpected results if a deployed load balancer member port is changed outside of vRealize Automation.
Configuring vRealize Automation
VMware, Inc. 554