7.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- 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
- Index
If multiple entitlements exist for the same business group, you can prioritize the entitlements. When a user
makes a catalog request, the entitlement and associated approval policy that applies is the highest priority
entitlement that grants the user access to that item or action.
Approval Policies
An approval policy is used to govern whether a service catalog user needs approval from someone in your
organization to provision items in your environment.
A tenant administrator or approval administrator can create approval policies. The policies can be for pre-
provisioning or post-provisioning. If a pre-approval is congured, then the request must be approved before
the request is provisioned. If it is a post-approval, the request must be approved before the provisioned item
is released to the requesting user.
The policies are applied to items in an entitlement. You can apply them to services, catalog items, catalog
item components, or actions that require an approver to approve or reject a provisioning request.
When a service catalog user requests an item that includes one or more approval policies, the approval
request is sent to the approvers. If approved, the request moves forward. If rejected, the request is canceled
and the service catalog user is notied regarding the rejection.
Infrastructure as a Service
With Infrastructure as a Service (IaaS), you can rapidly model and provision servers and desktops across
virtual and physical, private and public, or hybrid cloud infrastructures.
n
Conguring Infrastructure Fabric on page 26
The IaaS administrator and fabric administrator roles are responsible for conguring the fabric to
enable provisioning of infrastructure services. Fabric conguration is system-wide and is shared
across all tenants.
n
Infrastructure Source Endpoints on page 27
Infrastructure sources can include a group of virtualization compute resources or a cloud service
account.
n
Compute Resources on page 27
A compute resource is an object that represents a host, host cluster, or pool in a virtualization
platform, a virtual datacenter, or an Amazon region on which machines can be provisioned.
n
Data Collection on page 28
vRealize Automation collects data from infrastructure source endpoints and their compute resources.
n
Fabric Groups on page 29
An IaaS administrator can organize virtualization compute resources and cloud endpoints into fabric
groups by type and intent. One or more fabric administrators manage the resources in each fabric
group.
n
Business Groups on page 29
A business group associates a set of services and resources to a set of users, often corresponding to a
line of business, department, or other organizational unit.
n
Machine Prexes on page 29
You use machine prexes to generate the names of provisioned machines. Machine prexes are shared
across all tenants.
n
Resource Reservations on page 29
You can create a reservation to allocate provisioning resources in the fabric group to a specic business
group.
Foundations and Concepts
VMware, Inc. 25