Integrating vROps with vRA 8 using Workspace One Auth Source

Product Version - vRealize Automation 8.x

Why integrate vROps with vRA 8?

vRealize Automation can work with vRealize Operations Manager to perform advanced workload placement, provide deployment health and virtual machine metrics, and display pricing.

So what is the problem?

When configuring the integration, you will input the vROps URL and it will also ask you to input a username and password of the service account you wish to use. This is no problem if the accouint is a locally created account in vROps itself but most enterprises will want to use AD created service accounts which are then imported into vROps via WorkSpace One (vIDM)

So vROps 6.5 has been out for around a month now and I finally have a little while to write a post on what I personally really like.

There is a lot of great new enhancements and improvements added in 6.5 but for the sake of brevity I shall highlight two that I really liked.

Flexibility to increase RAM in between node sizes

So if you are familiar with vROps you will know that when you deploy it you have “T-Shirt” sizes to choose from, Small, Medium, Large and now Extra Large (6.5). However an additional extra in 6.5 is support to increase the memory allocation of your vROps nodes, you will not require additional CPU for the node until you hit the next node size bracket. If in doubt check the sizing guide spreadsheet VMware has provided so you can be sure on what you can and cannot do.