Getting Started

Pre-Install Checklist

  • VMware’s vRealize Automation (vRA) and vRealize Orchestration (vRO) are already installed and configured.
    • vRO may be embedded (recommended) or external
  • vRA and vRO components have been configured according to VMware’s recommendations
  • If using vRealize Automation 7.3.0, upgrade to vRA 7.3.1 (required)
    Please contact VMware support for assistance installing this upgrade if the target vRA environment is an HA cluster, or if it is a Production instance.

    This install takes approximately 30-60 minutes and will require downtime.

    The vRA 7.3.1 upgrade is provided and supported by VMware. Please direct any questions or issues with this upgrade to VMware support.
  • vRA has the following configured:
    • Tenant (can be any tenant, including the root tenant, vsphere.local…)
    • Compute Resource(s)
    • Reservation(s)
    • vRA Blueprint(s)
  • If using an external vRO, vRO configured in vRA
    1. Login to the vRA tenant
    2. Click on the Administration tab > vRO Configuration > Server Configuration
    3. Toggle the Use an external Orchestrator server radio button
    4. Select Basic authentication and enter appropriate credentials
      • Should be a Service Account created/used for Step 1.1
      • Username in UPN format (user@domain)
    5. Click Test Connection
    6. If the connection is successful, click OK
    7. Click on the Infrastructure tab > Endpoints > Endpoints to add an external vRO endpoint in vRA
    8. Click on +New > Orchestration > vRealize Orchestrator
    9. Fill out the form accordingly
    10. Click on +New Custom Property to add the property:
      • Name: VMware.VCenterOrchestrator.Priority
      • Value: Any number with 1 being the highest priority
    11. Click OK to save
  • vCenter has the following configured:
    • Storage
    • Networks/Trunks/port groups
    • VM template(s)
    • vCenter Customization Specification(s)

Final Pre-Install Checklist

Once the basic vRA requirements are met, you are ready to continue.

Task Reference
vRA 7.3 only: vRA 7.3.0 has been upgraded to 7.3.1 vRealize 7.3.1 release notes
vRA and vRO are installed and configured  
For Clustered vRA and/or vRO, load balancing is configured according to VMware’s documentation HA and vRA with SovLabs
Successfully provisioned a VM from vRA using a blueprint  
Keep things simple by not using spaces or camel-casing for the following created for this install:
  • Tenant name
  • Users
  • Group names
  • Business Groups
Use all lowercase for these

Install Summary

# Step Location Notes
1 Configure vRA    
1.1 Create a local vRA user to be the service account to own the SovLabs content vRA console All lowercase, no spaces (e.g. sov_admin)
1.2 Create a custom group for Administrative users in vRA vRA Console All lowercase, no spaces (e.g. sov_admins)
1.3 Create a vRA Business Group to own the SovLabs vRA Extensibility Modules Service vRA Console Recommended to create a Business Group named sovlabs specifically for this purpose
1.4 Configure Roles and Permissions in vRA vRA Console Grant necessary roles and permissions to custom group (e.g. sov_admins)
2 Configure vRO    
2.1 Modify vmo.properties and js-io-rights files and set permissions vRO server  
2.2 Create krb5.conf for Kerberos Authentication to Windows VMs, if needed vRO server Set permission on krb5.conf to 0644
2.3 Increase vRO Max Heap to 768m for vco-configurator service vRO server  
2.4 Create a vRA Host via vRO workflow vRO client The default vRA host will not work for the SovLabs plugin.

The vRA Host must be Shared Session mode.

If using the vsphere.local tenant, the name must begin with sovlabs_
2.5 Create vRA IaaS Host via vRO workflow vRO client The vRA IaaS Host may already exist
3 Install SovLabs Plugin vRO Control Center  
3.1 Run the SovLabs Configuration workflow vRO client  
3.2 Add SovLabs License vRO Console  
Optional If using EMC’s Federation Enterprise Hybrid Cloud (FEHC), modify the setenv.sh file vRO server EMCs FEHC and SovLabs

Go to vRA Prereqs for SovLabs