In the first three articles of this series we deployed the vRLCM and vRIDM appliances, configured them, then replaced their certificates. Those configurations was the minimum but further customization steps may be required. During the deployment we created only one vCenter, but I think even small customers own more than one. Before we jump into the application deployment, let’s add more datacenters and vCenter Servers.
vRLCM Datacenter Management
1, Logon to your vRLCM instance with the user admin@local and choose Lifecycle Operations, then select Manage Datacenters
2, There you can find the “Default_datacenter” what was created during the vRLCM deployment. If you want you can edit it and fix the location if necessary. Once its complete, click on + Add Datacenter and fill the required fields: Datacenter Name and the Location.
3, Now you have the new datacententer and its location. It’s time to add new vCenter Server(s) into the DC what we created. Click on + ADD VCENTER or if you have multiple vCenters, you can import them.
4, If you chose IMPORT, then you have to upload the DATA in format of JSON or CSV. Sample files available for both type.
5, If you selected + ADD VCENTER, then the following details must be filled: vCenter Name, vCenter FQDN, Credentials chosen from the list, and finally vCenter’s Type.
You can create a role in your vCenter server with privileges that required deploying different products and the same role can be used here to connect vCenter servers.
The privileges of this role could be the following:
- Datastore › All privileges
- Host.Inventory.Modify Cluster
- Host.Local.Operations.Add host to vCenter
- Host.Local.Operations.Create Virtual Machine
- Host.Local.Operations.Delete Virtual Machine
- Host.Local.Operations.Reconfigure Virtual Machine
- Network.Assign Network
- Resource.Assign vApp to Resource Pool
- Resource.Assign Virtual Machine to Resource Pool
- vApp › All privileges
- Virtual Machines ›All privileges
- Content Library › All privileges
Note: Due Content Library requirements this role must be created as a Global Role.
Note2: The official documentation doesn’t mention Host.Inventory.Modify Cluster privileges, but its required later when we creating anti-affinity rules for Log Insight cluster
Click on Validate, which will test the login, then Save if all is fine. You can repeat the process with other Datacenters and vCenter servers. If you don’t have the Credentials, you can go to the Locker / Password and create as many password aliases as require.
With this article the setup of vRealize Suite Lifecycle Manager is complete. If you are stuck somewhere, or something is not clear do not hesitate to comment or drop an e-mail. Likes are also welcome! 🙂
At this point there are two options available, one is deploy new solutions like Log Insight, Automation or Operations Manager, while the second is importing solutions you already have. I will continue with adding a completer Log Insight solution.
Using vRealize Lifecycle Manager – Part One
Using vRealize Lifecycle Manager – Part Two
Using vRealize Lifecycle Manager – Part Three
Using vRealize Lifecycle Manager – Part Four
Using vRealize Lifecycle Manager – Part Five