I just love vSphere Tags. I think it’s one of those vSphere features that people don’t use that much – what a shame because when it comes to vROps integration it can come very handy!
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 🙂 ).
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.
In part 1 and part 2 we’ve covered how to create the Super Metrics and the custom XML files for our 1-Click Capacity Planning Interactive Custom Dashboard (WOW that’s a long name for a dashboard ). In the final part for this series we will finally create this great dashboard. Let’s start…
Going back to the early days of virtualization, capacity planning always was a process needed to be done in some point. If you into virtualization you know what the benefits are and why it’s important to go through a thorough capacity planning process but sometimes it’s hard to know what or where to look and where to begin.