6.2

The following diagram shows a multitenant deployment where each tenant manages their own
infrastructure. The system administrator is the only user who logs in to the default tenant to manage
system-wide configuration and create tenants.
Each tenant has an IaaS administrator, who can create fabric groups and appoint fabric administrators
with their respective tenants. Although fabric administrators can create reservations for business groups
in any tenant, in this example they typically create and manage reservations in their own tenants. If the
same identity store is configured in multiple tenants, the same users can be designated as IaaS
administrators or fabric administrators in each tenant.
Figure 6‑3. Multitenant Example with Infrastructure Configuration in Each Tenant
IaaS
admin
IaaS
admin
Tenant
admin
Tenant A
http://vra.mycompany.com/
vcac/org/tenanta/
Tenant
admin
Tenant B
Business
group mgr
Business
Group
Business
group mgr
Business
Group
http://vra.mycompany.com/
vcac/org/tenantb/
Tenant
admin
Tenant C
Business
group mgr
Business
Group
Business
group mgr
Business
Group
http://vra.mycompany.com/
vcac/org/tenantc/
Default
Tenant
(System config)
Hypervisors
Public
clouds
Physical
servers
IaaS
admin
Fabric
Fabric
admin
Fabric Group
Business
group mgr
Business
Group
Business
group mgr
Business
Group
Reservation Reservation
Fabric
admin
Fabric Group
Fabric
admin
Fabric Group
Reservation Reservation Reservation Reservation
System
admin
Infrastructure
http://vra.
mycompany.com/
vcac/
Create and Configure a Tenant
System administrators create tenants and specify basic configuration such as name, login URL, identity
stores, and administrators.
Prerequisites
Log in to the vRealize Automation console as a system administrator.
Procedure
1 Specify Tenant Information
The first step to configuring a tenant is to add the new tenant to vRealize Automation and create the
tenant-specific access URL.
System Administration
VMware, Inc. 44