The following post details how to reconfigure both the CPU & Memory of a specific VM from within a vRealize Automation console.
Begin by enabling the Reconfigure Entitlement for the machine component.
Login as a Tenant Administrator:
Click Administration > Catalog Management > Entitlements:
This procedure details the steps to execute in order to remove an ESXi host from a source ViPR Export Group and add to an existing target Export Group.
Note: this procedure applies to ViPR 3.0 and below, ViPR 3.6 introduces a more automated procedure which I intend to cover in a future post.
Please ensure there are no EHC StaaS or VIPR native tasks being executed while performing the following procedure.
Note: Ensure the version of SMI-S complies with the EHC ESSM stated version.
The following steps detail the procedure for removing a host from a vSphere ESXi cluster in vCenter and utilizing the ViPR CLI to remove the same host from the cluster Export Group. Continue reading
Reference KB:
Directory sync is running endlessly in vRealize Automation 7.x (2146237)
While the above Kb refers to a known issue affecting VMware vRealize Automation 7.0.x, I also encountered this issue on vRA 7.1 and the resolution in the Kb worked successfully.
Sync displays as a running indefinitely:
While in the process of creating a vRA blueprint, none of my vSphere templates were displaying as an option for selection. This led me to verify some of my previous config, which led to identifying the source of the problem to be a misplaced template. Thanks @HeagaSteve for pointing me in the right direction!
As you can see when I click on the ellipsis in order to select a template I receive ‘No data to display’ in the list box:
vRealize Automation 7.1 – Create Tenant & Configure Authentication (Part 2)
Following on from the tenant & authentication post above, the following steps detail the creation of an Endpoint & Fabric Group in vRA 7.1.
This post will show how to create a vCenter endpoint followed by a Fabric Group, a vRO endpoint and the credentials required to connect vRA to these endpoints.
Begin by logging into the new tenant with a user who has the IaaS Administrator privileges:
Nice flow chart from vmware.com:
Login into your tenant:
https://vipvra.ppsilver.lab.local/vcac/org/ehc/
vRealize Automation 7.1 – Installation (Part 1)
Following on from the Install post above, the following steps detail the creation of a Tenant in vRA 7.1.
Begin by navigating to https://vRA-FQDN and logging into the default tenant using the Administrator account and password created during install:
Looks like there maybe a bug in the vRA 7.1 wizard deployment. I’m running vRA version 7.1 build 4270058 and Windows 2012 R2 build 9600.
Even though we configured the vCenter endpoint name as cloudvc01 during the vRealize Automation wizard based install, the IaaS Agent server was displaying the vCenter agent name using the FQDN cloudvc01.ppsilver.lab.local (screen captures below):
Wizard input – ‘Agents’:
