7.3

You can work with Azure resource actions just as with any other XaaS resource actions in
vRealize Automation. See Creating XaaS Blueprints and Resource Actions and vRealize Orchestrator
Integration in vRealize Automation in Configuring vRealize Automation for more information about XaaS
resource actions.
Prerequisites
Configure a valid Azure Endpoint for your vRealize Automation deployment.
Procedure
1 Select Design > XaaS > Resource Actions
2 Click New.
3 Navigate to Orchestrator > Library > Azure in thevRealize Orchestrator workflow library.
4 Select the desired folder and workflow.
5 Configure the action for your needs as you would any other XaaS resource action.
Creating Puppet Enabled vSphere Blueprints
You can create Puppet enabled vSphere blueprints that support Puppet-based configuration management
of vSphere virtual machines.
Puppet-based configuration management typically uses roles and environments to define and manage
software configuration. Be aware that the meaning of role and environment in Puppet differs for the more
IT generic meaning.
An endpoint establishes a connection with an existing Puppet enterprise deployment. When the endpoint
is created, vRealize Automation retrieves the list of environments and roles associated with the specified
deployments. You can use these environments and roles in either early binding or late binding scenarios
when configuring a Puppet enabled virtual machine blueprint.
Note Puppet components are currently supported only on vSphere blueprints and virtual machines.
Add a Puppet Component to a vSphere Blueprint
You can add a Puppet configuration management component to a vSphere blueprint to facilitate enforced
management of vSphere virtual machines using a Puppet Master.
Adding a Puppet component to a vSphere blueprint adds a Puppet agent to virtual machines created from
that blueprint.
When creating Puppet-enabled vSphere blueprints, you must choose whether to create an early binding
or late binding configuration.
With early binding, users define the Puppet role and environment settings for all virtual machines based
on a particular blueprint when the Puppet component is added to the blueprint. These settings remain
static during the life of the blueprint. For late binding, you have several options.
n
Leave the Puppet environment andPuppet role text boxes empty in the blueprint, and users provide
these settings at request time.
Configuring vRealize Automation
VMware, Inc. 425