From time to time a change is needed and in the case of vROps, changing the Master Node IP address is not something you will do via the GUI (well, at least not all the configurations 🙂 ).
I am a big vROps Interactions XML fan, as a matter of fact I’ve written on this topic a few times before. Now that the vApp structure has changed from 2 to 1 VM, I wasn’t able to find my beloved XML files. So dude, where are my XML’s?
In the previous part we have created a 2-node vRealize Operations 6 High Availability cluster. With its new architecture, vROps unified UI is expected to get lots of HTTPS requests traffic so it only makes sense to load balancing it, no?!
vRealize Operations Manager 6 brings new high availability options to the table and has several deployment modes. In this 2-part series I will show you how to create a 2-node vROps High Availability Cluster mode cluster and put it behind a vShield Edge Load Balancer.
With vROps just around the corner, I am getting a lot of questions around how the migration of all that hard work that was done in vCenter Operation Manager 5.x to vRealize Operations 6 will work. Well, quite easily.
Branding can sometimes be very important so I thought to myself why not doing a facelift to vCOps login page?! In order to do that you just need to know where to look.
Well, this post is all about pure fun and doing stupid things with smart products. Although I’m not that of soccer fan I’ve decided to accept the challenge and help all the VI admins soccer puppies out there.
In part 4 of this series we have finished laying down the Super Metrics infrastructure for the OvDC Admin Custom Dashboard. Custom Groups is a powerful feature within vCOps. Having said that, I will use it in order to dynamically grouping the OvDC resources.