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
Figure 1. Single-Tenant Example
Tenant
admin
Business
group mgr
Business
Group
Business
goup mgr
Business
Group
http://vra.mycompany.com/vcac/
Default Tenant
(System and
infrastructure config)
System
admin
IaaS
admin
Infrastructure Fabric
Hypervisors
Public
clouds
Physical
servers
Default Tenant
• User management
• Tenant branding
• Tenant notification
providers
• Approval policies
• Catalog management
• Tenant creation
• System branding
• System notification
poviders
• Event logs
Fabric
admin
Fabric
Group
Reservation Reservation
Fabric
admin
Fabric
Group
Reservation Reservation
Fabric
admin
Fabric
Group
Reservation Reservation
(Tenant config)
http://vra.mycompany.com/vcac/
Note In a single-tenant scenario, it is common for the system administrator and tenant administrator roles
to be assigned to the same person, but two distinct accounts exist. The system administrator account is
always administrator@vsphere.local, and the system administrator account creates a local user account to
assign the tenant administrator role.
Multitenant Deployment
In a multitenant environment, the system administrator creates tenants for each organization that uses the
same vRealize Automation instance. Tenant users log in to the vRealize Automation console at a URL
specic to their tenant. Tenant-level conguration is segregated from other tenants and from the default
tenant. Users with system-wide roles can view and manage conguration across multiple tenants.
There are two main scenarios for conguring a multi-tenant deployment.
Table 2. Multitenant Deployment Examples
Example Description
Manage infrastructure conguration
only in the default tenant
In this example, all infrastructure is centrally managed by IaaS administrators
and fabric administrators in the default tenant. The shared infrastructure
resources are assigned to the users in each tenant by using reservations.
Manage infrastructure conguration in
each tenant
In this scenario, each tenant manages its own infrastructure and has its own
IaaS administrators and fabric administrators. Each tenant can provide its own
infrastructure sources or can share a common infrastructure. Fabric
administrators manage reservations only for the users in their own tenant.
Foundations and Concepts
14 VMware, Inc.