7.3
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- Foundations and Concepts
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
Resource Mappings
You create resource mappings between the vRealize Automation catalog resource type and the
vRealize Orchestrator inventory type to manage resources provisioned outside of XaaS.
For example, you might want to create an action so that users can take a snapshot of their Amazon
machines. For this action to work on an Amazon machine provisioned, the three components involved,
XaaS, vRealize Orchestrator, and IaaS, need a common language You create that common language by
adding a resource mapping in XaaS that runs a vRealize Orchestrator scripting action or workflow to map
the IaaS Cloud Machine resource type to the vRealize Orchestrator AWS:EC2Instance inventory type.
vRealize Automation provides resource mappings, and the underlying vRealize Orchestrator script
actions and workflows, for vSphere, vCloud Director, and vCloud Air machines.
XaaS Blueprints
An XaaS blueprint is a complete specification of a resource.
With XaaS blueprints, you publish predefined and custom vRealize Orchestrator workflows as catalog
items for either requesting or provisioning. Blueprints for requesting run workflows with no provisioning
and provide no options for managing a provisioned item. Before you create a blueprint for provisioning,
you must map the workflow output parameter as a custom resource. Then you can assign resource
actions that define post-provisioning operations.
Resource Actions
You can create custom resource actions to configure the post-provisioning operations that the consumers
can perform.
To create post-provisioning operations, you must publish vRealize Orchestrator workflows as resource
actions. To create a resource action for an item provisioned by using XaaS, you use a custom resource
as an input parameter for the workflow. To create a resource action for an item that is provisioned by a
source different from XaaS, you use a resource mapping as an input parameter for the workflow. When
you entitle the resource actions, they appear in the Actions drop-down menu of the provisioned items on
the Items tab.
Common Components
vRealize Automation includes several common components in addition to the service catalog and catalog
item sources such as Infrastructure as a Service and XaaS.
Foundations and Concepts
VMware, Inc. 43