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
Other catalog items do not result in provisioned items. For example, a cell phone user can submit a
request for additional minutes on a mobile plan. The request initiates a workflow that adds minutes to the
plan. The user can track the request as it progresses, but cannot manage the minutes after they are
added.
Some catalog items are available only in a specific business group, other catalog items are shared
between business groups in the same tenant.
Actions
Actions are operations that you can perform on provisioned items.
Users can manage their provisioned items on the Items tab. The View Details option is always present in
the Actions menu. Additional options might be available depending on the type of item and the user's
entitlements. For example, Power On can be available for machines but not for HR services such as
provisioning a new hire.
You can perform request actions and immediate actions. Request actions initiate requests, which you can
track on the Requests tab and which can be made subject to approval. Statuses shown on the Requests
tab indicate the success or failure of the request, and do not indicate the successful completion of an
action. Immediate actions do not create requests and are always run immediately.
Built-in actions are available to all tenants and cannot be edited, although they can be enabled or
disabled. Custom actions can be created at a per-tenant level and shared across all business groups in
that tenant.
Entitlements
Entitlements determine which users and groups can request specific catalog items or perform specific
actions. Entitlements are specific to a business group.
Business group managers can create entitlements for the groups that they manage. Tenant
administrators can create entitlements for any business group in their tenant. When you create an
entitlement, you must select a business group and specify individual users and groups in the business
group for the entitlement.
You can entitle an entire service category, which entitles all of the catalog items in that service, including
items that are added to the service after you create the entitlement. You can also add individual catalog
items in a service to an entitlement. Services do not contain actions. You must add actions to an
entitlement individually.
For each service, catalog item, or action that you entitle, you can optionally specify an approval policy to
apply to requests for that item. If you entitle an entire service and a specific catalog item in that service in
the same entitlement, the approval policy on the catalog item overrides the policy on the service. For
example, you can entitle the Cloud Infrastructure service to members of a business group and allow them
to request any of its items with no approval policy. For a select number of catalog items that require more
governance for their provisioning, you can entitle those in the same entitlement and apply an approval
policy on just those items.
Foundations and Concepts
VMware, Inc. 30