7.2

vRealize Business for Cloud Overview
With vRealize Business for Cloud, directors of cloud operations can monitor their expenditures and design
more cost-ecient cloud services.
vRealize Business for Cloud provides the following benets:
n
Drives accountability by providing visibility into the cost of virtual infrastructure and public cloud
providers.
n
Promotes eciencies in the virtual infrastructure by making it possible to compare the costs, eciency,
and availability of their private cloud with public cloud providers and industry benchmark data.
n
Optimizes decisions about placement for virtual workloads and tradeos between buying new
hardware and using public cloud providers.
For more information about vRealize Business for Cloud, see the vRealize Business for Cloud
documentation set.
Tenancy and User Roles
vRealize Automation supports multiple tenants in the same installation. Users always log in and perform
their tasks in a specic tenant. Some administrator roles can manage conguration that aects multiple
tenants.
Tenancy Overview
A tenant is an organizational unit in a vRealize Automation deployment. A tenant can represent a business
unit in an enterprise or a company that subscribes to cloud services from a service provider.
Each tenant has its own dedicated conguration. Some system-level conguration is shared across tenants.
Table 1. Tenant Configuration
Configuration Area Description
Login URL Each tenant has a unique URL to the vRealize Automation console.
n
The default tenant URL is in the following format: hps://hostname/vcac
n
The URL for additional tenants is in the following format:
hps://hostname/vcac/org/tenantURL
Identity stores Each tenant requires access to one or more directory services, such as
OpenLDAP or Microsoft Active Directory servers, that are congured to
authenticate users. You can use the same directory service for more than one
tenant, but you must congure it separately for each tenant.
Branding A tenant administrator can congure the branding of the vRealize Automation
console including the logo, background color, and information in the header
and footer. System administrators control the default branding for all tenants.
Notication providers System administrators can congure global email servers that process email
notications. Tenant administrators can override the system default servers, or
add their own servers if no global servers are specied.
Business policies Administrators in each tenant can congure business policies such as approval
workows and entitlements. Business policies are always specic to a tenant.
Service catalog oerings Service architects can create and publish catalog items to the service catalog and
assign them to service categories. Services and catalog items are always specic
to a tenant.
Infrastructure resources The underlying infrastructure fabric resources, for example, vCenter servers,
Amazon AWS accounts, or Cisco UCS pools, are shared among all tenants. For
each infrastructure source that vRealize Automation manages, a portion of its
compute resources can be reserved for users in a specic tenant to use.
Foundations and Concepts
12 VMware, Inc.