This topic introduces the integration of vRealize Automation with vSphere resources used to create the Infrastructure as a Service design for use with the SDDC.

The following diagram illustrates the logical design of the vRealize Automation groups and vSphere resources.

Figure 1. vRealize Automation Logical Design




The following terms apply to vRealize Automation when integrated with vSphere. These terms and their meaning may vary from the way they are used when referring only to vSphere.

Term

Definition

vSphere (vCenter Server) endpoint

Provides information required by vRealize Automation IaaS to access vSphere compute resources.

Compute resource

Virtual object within vRealize Automation that represents a vCenter Server cluster or resource pool, and datastores or datastore clusters.

Note:

Compute resources are CPU, memory, storage and networks. Datastores and datastore clusters are part of the overall storage resources.

Fabric groups

vRealize Automation IaaS organizes compute resources into fabric groups.

Fabric administrators

Fabric administrators manage compute resources, which are organized into fabric groups.

Compute reservation

A share of compute resources (vSphere cluster, resource pool, datastores, or datastore clusters), such as CPU and memory reserved for use by a particular business group for provisioning virtual machines.

Note:

vRealize Automation uses the term reservation to define resources (be they memory, storage or networks) in a cluster. This is different than the use of reservation in vCenter Server, where a share is a percentage of total resources, and reservation is a fixed amount.

Storage reservation

Similar to compute reservation (see above), but pertaining only to a share of the available storage resources. In this context, you specify a storage reservation in terms of gigabytes from an existing LUN or Datastore.

Business groups

A collection of virtual machine consumers, usually corresponding to an organization's business units or departments. Only users in the business group can request virtual machines.

Reservation policy

vRealize Automation IaaS determines its reservation (also called virtual reservation) from which a particular virtual machine is provisioned. The reservation policy is a logical label or a pointer to the original reservation. Each virtual reservation can be added to one reservation policy.

Blueprint

The complete specification for a virtual machine, determining the machine attributes, the manner in which it is provisioned, and its policy and management settings.

Blueprint allows the users of a business group to create virtual machines on a virtual reservation (compute resource) based on the reservation policy, and using platform and cloning types. It also lets you specify or add machine resources and build profiles.

vRealize Automation Integration with vSphere Endpoint shows the logical design constructs discussed in the previous section as they apply to a deployment of vRealize Automation integrated with vSphere in the consolidated SDDC.

Figure 2. vRealize Automation Integration with vSphere Endpoint


vRealize Automation Integration with vSphere Endpoint