An infrastructure source endpoint is a connection to the infrastructure that provides a set (or multiple sets) of resources, which can then be made available by IaaS administrators for consumption by end users. vRealize Automation IaaS regularly collects information about known endpoint resources and the virtual resources provisioned therein. Endpoint resources are referred to as compute resources(or as compute pods, the terms are often used interchangeably).

Infrastructure data is collected through proxy agents that manage and communicate with the endpoint resources. This information about the compute resources on each infrastructure endpoint and the machines provisioned on each computer resource is collected at regular intervals.

During installation of the vRealize Automation IaaS components, you can configure the proxy agents and define their associated endpoints. Alternatively, you can configure the proxy agents and define their associated endpoints separately after the main vRealize Automation installation is complete.

Endpoint Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-CMP-034

Create two vSphere endpoints.

One vSphere endpoint is required to connect to each vCenter Server instance in each region. Two endpoints will be needed for two regions.

As additional regions are brought online additional vSphere endpoints need to be deployed.

SDDC-CMP-035

Create one vRealize Orchestrator endpoint.

vRealize Automation extensibility uses vRealize Orchestrator. One vRealize Orchestrator cluster exists which requires the creation of a single endpoint.

Using external vRealize Orchestrator requires manual configuration of a vRealize Orchestrator endpoint.