7.1
Table Of Contents
- Foundations and Concepts
- Contents
- 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
- Index
Comparison of Single-Tenant and Multitenant Deployments
vRealize Automation supports deployments with either a single tenant or multiple tenants. The
conguration can vary depending on how many tenants are in your deployment.
System-wide conguration is always performed in the default tenant and can apply to one or more tenants.
For example, system-wide conguration might specify defaults for branding and notication providers.
Infrastructure conguration, including the infrastructure sources that are available for provisioning, can be
congured in any tenant and is shared among all tenants. You divide your infrastructure resources, such as
cloud or virtual compute resources, into fabric groups and assign an administrator to manage those
resources as the fabric administrator. Fabric administrators can allocate resources in their fabric group to
business groups by creating reservations.
Single-Tenant Deployment
In a single-tenant deployment, all conguration can occur in the default tenant. Tenant administrators can
manage users and groups, congure tenant-specic branding, notications, business policies, and catalog
oerings.
All users log in to the vRealize Automation console at the same URL, but the features available to them are
determined by their roles.
Foundations and Concepts
12 VMware, Inc.