7.1

Table 3‑6. Preparing for Provisioning a vRealize Automation Deployment Using Infoblox IPAM Checklist
Task Location Details
Obtain, import, and
congure the external IPAM
solution provider plug-in or
package.
Obtain and import the vRealize Orchestrator
plug-in, run the vRealize Orchestrator
conguration workows, and register the IPAM
provider endpoint type in
vRealize Orchestrator.
If the VMware Solution Exchange
(hps://solutionexchange.vmware.com/store/ca
tegory_groups/cloud-management) does not
contain the IPAM provider package that you
need, you can create your own using an IPAM
Solution Provider SDK and supporting
documentation.
See “Checklist for Preparing External
IPAM Provider Support,” on page 14.
Create an external IPAM
solution provider endpoint.
Create a new IPAM endpoint in
vRealize Automation.
See “Create an External IPAM Provider
Endpoint,” on page 163.
Specify external IPAM
solution provider endpoint
seings in an external
network prole.
Create an external network prole and specify
the dened IPAM endpoint in
vRealize Automation.
See “Create an External Network
Prole by Using An External IPAM
Provider,” on page 184.
Dene a reservation to
use the external network
prole for an existing
network path.
Create a reservation that calls the network
prole in vRealize Automation.
See “Create a Reservation for Hyper-V,
KVM, SCVMM, vSphere, or
XenServer,” on page 213.
Dene a blueprint that
uses the external network
prole.
Create a blueprint that uses the reservation in
vRealize Automation.
Entitle the blueprint and
add it to the catalog.
Entitle the blueprint and add it to the catalog in
vRealize Automation.
Request machine
provision by using the
blueprint catalog item.
Use the blueprint catalog item to request
machine provisioning in vRealize Automation.
Query which IP address
the deployment resides on
by using the My Items page.
Determine the network IP address used for the
deployment in vRealize Automation.
Configuring XaaS Resources
By conguring XaaS endpoints you can connect the vRealize Automation to your environment. When you
congure vRealize Orchestrator plug-ins as endpoints, you use the vRealize Automation user interface to
congure the plug-ins instead of using the vRealize Orchestrator conguration interface.
To use vRealize Orchestrator capabilities and the vRealize Orchestrator plug-ins to expose VMware and
third-party technologies to vRealize Automation, you can congure the vRealize Orchestrator plug-ins by
adding the plug-ins as endpoints. This way, you create connections to dierent hosts and servers, such as
vCenter Server instances, a Microsoft Active Directory host, and so on.
When you add a vRealize Orchestrator plug-in as an endpoint by using the vRealize Automation UI, you
run a conguration workow in the default vRealize Orchestrator server. The conguration workows are
located in the vRealize Automation > XaaS > Endpoint  workows folder.
I Conguring a single plug-in in vRealize Orchestrator and in the vRealize Automation console
is not supported and results in errors.
Configuring vRealize Automation
226 VMware, Inc.