In my 1-Click Capacity Planning vCOps Dashboard blog series I’ve created 6 vCOps Super-Metrics. Two of them calculating ESXi host cluster CPU and memory total provisioned capacity. But let us not forget HA Admission Control behind.
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…
In the first part for this series I covered some of the super metrics needed for pulling out ESXi Cluster capacity planning data in vCOps. In this part I would like to show you how to work with vCOps interaction mode XML files.
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.
In my previous post for this series I touched on both the allocation and demand models available to us when using vCops for capacity planning. As we have seen, playing with vCops capacity planning policy is important. Let’s continue with the configurations.
Lately, I’ve been working a lot around vCops. Using vCops in the right way can be super useful with the most common tasks for VMware architects and administrators. If you are in a search for simplifying your organization capacity planning process, discovering critical issues in your virtual environment or you’re just trying to check which VMs are the most oversized in the datacenter, vCops is your guy.