Showcasing Virtual Datacenter Capacity using vCenter Operations Manager Dashboards.

A few months back, I wrote about the capabilities of vCenter Operations Manager around Capacity Management in this article - vCenter Operations Manager - Solving Performance, Capacity and Configuration Problems!!. With this article I wanted to take a step further and showcase how you can use vCOps in a real world scenario to monitor the capacity of your Virtual Datacenter in an automated manner.

If you read my last 2 articles on vCenter Operations Manager, you would notice that custom dashboards in vCenter Operations is an amazing way to showcase a lot of important data which is collected,analysed & computed by vCOps Patented Analytics and Capacity engine. In this article I will share a Custom Dashboard which in a single pane can showcase multiple facets of Capacity & Consolidation in your Virtual Datacenter. 

To begin with let's have a look at the dashboard and then we will break down the discussion on how to create it using the custom dashboard widgets.

Executive Capacity Dashboard

Well that is colorful, isn't it. As complex as it looks, if your approach towards creating this dashboard is correct, this should be a matter of few minutes. I will not go into step by step of how I created it, I would rather ask you to get your hands dirty and learn how to create such dashboards.

Here are a few pointers on this dashboard, which will help you create one on your own:-

a) The over all dashboard is a 2 column and 8 widget dashboard.

b) Each widget used is a Score Board Widget.

c) No super-metric used here. Each widget uses metrics which are already populated by default vCOps collection.

Let's look at each part horizontally.

Part 1 - Datacenter Capacity and Consolidation Ratios

Here the widget on the left uses a scoreboard widget to show the capacity of 2 data-centers  DC 1 and DC2.  I have used the Datacenter as the Resource tags here shown the "Summary" of each Datacenter such as number of Clusters, Datastores, ESXi Hosts and Virtual machines in a DC.

The widget on the right uses the scoreboard widget to show the consolidation ratios of both the virtual data-centers by using the Datacenter as the resource tag and  "Density" ratios to populate the following vCPU to pCPU, VMs to Hosts and vMem to pMem. This can give you the density of your Datacenter in a snap.

Part 2 - Capacity & Time Remaining in Each DC/Cluster 

This takes the capacity information to the next level. This section talks about, how many VMs can be deployed, how many VMs are deployed currently and the number of days remaining for VMs to be deployed (from left to right). I have done this for one cluster in each Datacenter as this is what I have in my lab. I used Score Board Widgets, Datacenter/Cluster as Resource Tags and "Capacity Remaining", "Time Remaining" and "Summary" as the metric providers for these scoreboards.

Note:- The number of days are a weird looking number since there has been no deployment in this cluster after installing vCOps. vCOps does not have a deployment pattern in this case, using which it can suggest you the approximate amount of days remaining.

Part 3 - Resource Wise Capacity Remaining

This part also uses 2 scoreboard widgets for each Datacenter/Cluster and this breaks down the part 2 of this dashboard further down to tell which which is the most constraining resource due to which you have given number of virtual machines which you can deploy in your Datacenter/Cluster. Again I have selected Datacenter as the "Resource Tag" and used "Capacity Remaining" resource wise such as CPU, Disk Space, Disk I/O, Memory and Network and showcased, ho many VMs you can deploy as per each individual resource.

Part 4 - Resource Wise Time Remaining

Coming to the last part of the dashboard. This again is made by using the Scoreboard widget and tells you how many days would a resource last with your deployment pattern of creating new Virtual Machines in each Datacenter/Cluster. Again I have selected Datacenter as the "Resource Tag" and used "Time Remaining" resource wise such as CPU, Disk Space, Disk I/O, Memory and Network and showcased, how many VMs you can deploy as per each individual resource.

Note:- The number of days are a weird looking number since there has been no deployment in this cluster after installing vCOps. vCOps does not have a deployment pattern in this case, using which it can suggest you the approximate amount of days remaining.

Having said this before, it is your creativity & need which can take you to heights with vCOps customization. I prefer this way of dash-boarding rather than seeing what is available out of the box in a lot of other products, as this gives the power to create in my hands, rather that being dependent on the manufacturer of the product.

I will close this article now, feel free to reach out if you have questions around the discussed topic. 

Don't forget to Share and Spread the Knowledge. 

Reclaiming Waste Capacity using vCOPS - How to Calculate Waste & Usage Accurately!

This article is coming out of a discussion which I had around a month ago with one of my colleague and then with a customer about the Capacity Management feature of vCenter Operations Manager (vCOPS).

If you are new to vCOPS, I would recommend reading my other posts on vCOPS which would make you familiar with this topic:

vCenter Operations Manager - Solving Performance, Capacity and Configuration Problems!!

Right Sizing vCenter Operations Manager vAPP For Efficient Performance !!

I believe this topic is worth writing about as this might help you understand how Capacity IQ which is now rolled up into vCenter Operations Manager (vCOPS), calculates the usage of resources for a Virtual Machine or for that matter any object in the vCenter. The resource usage ultimately helps the tool to monitor the Capacity Utilization over a period of time. This Capacity utilization leads to calculation of 2 minor badges:-

a) Reclaimable Waste, and

b) Density

These two values then roll up into a Main Badge known as "EFFICIENCY". A score of 100 on efficiency means that you are using the virtual infrastructure in the most appropriate way, and as that score starts reducing, you know that either you have virtual machines which are Over Sized or Under Sized which will lead to waste of resources or performance issues due to resource contention.

Below is a screenshot which shows how the efficiency badge and the sub-badges show in the vCenter Operations Dashboard.

At the end of the day, efficiency is the most important piece of information which the Capacity Management feature of vCOPS provides. From the perspective of an IT buyer, it becomes a tool which helps you to ensure that you do not waste any resources in your infrastructure by following primitive methods of resource allocation to servers and applications.

Hence, this allows you to right size your infrastructure as you operate and manage it. 

For example, a new application which needs to be deployed in your infrastructure needs a Windows 2008 R2 VM, with 4 vCPU and 16 GB of RAM as per the application owner. This might be a practice which is being carried forward by the application owner from the world of physical servers. However, with Virtual it is quite possible that the VM will never use the allocated capacity. The challenge is that how can we capture this data and present it back to the application owner.

vCOPS has the answer - Once this machine is created and the server goes into production, vCOPS would start monitoring this virtual machine on a regular basis and would capture data around utilization of CPU & Memory. After a period of 30 to 45 days, vCOPS would understand the capacity utilization patterns of this virtual machine. After this, a report in vCOPS about Reclaimable Waste will easily tell you about all the virtual machines which are over-sized on CPU or Memory. On the basis of this report you can reclaim the resource and save a lot of money for your organization by increasing the efficiency of the hardware. 

While I say this, it is important that you have the correct settings to monitor the utilization capacity and usage patterns of your virtual infrastructure. In a business environment where the servers work between 9 AM to 6 PM, Monday to Friday, it is important that you capture the utilization patterns during this period to calculate the reclaimable waste and density of the Virtual Machine. In such a scenario if you set the monitoring days and time to 24/7, you will end up capturing a lot of skewed data which does not reflect the correct business cycles. This will ultimately result in a very low efficiency and a huge amount of reclaimable waste which might not be TRUE otherwise.

To avoid such problems, follow the settings on the screenshot mentioned below and you should be good to go.

This would ensure that you capture the right data and process it into valid information which will help you manage capacity in your Virtual Infrastructure. It's important that any decision regarding capacity is not taken in a haste. Rather, we should ensure that we customize the settings for monitoring capacity on the basis of our own environment and then let the tool run for a period of 4 weeks to 6 weeks before you start looking into the results and begin to make changes for the betterment of your Virtual Infrastructure.

Hope this will help you learn more about what vCOPS can do for you and how you can do such tasks accurately.