This post continues from the Operationalize Your World post. Do read it first so you get the context.
The SMB segment is a world of its own. There are things that are mandatory in Enterprise segment, but not relevant in SMB segment. As a result, products should be tailored for that market segment.
IMHO, there are actually 4 different market segments when it comes to SDDC Operations. I use No of VM as the marker for each segment. Each of the following segment requires different dashboards and reports:
- 100 VM
- 1000 VM
- 10000 VM
- 100000 VM
Now, it will be difficult to create a product with 4 sets of vROps dashboards & reports. I make a compromise on the above, and use this one instead:
- 400 VM: SMB market
- 4000 VM: Enterprise market
- 40000 VM: <give me a name here folks> market
I hope the above is acceptable. As the above has very wide range, I’d take the following reference point
- SMB market: 250 VM
- Enterprise market: 2500 VM
- Huge Private Cloud: 25000 VM
Let’s dive to the 250 VM segment. What are the unique characteristics?
- 1-2 guys doing everything. No siloes in the team. You and your best friends take care of the whole darn IT.
- You only have a few clusters. Each cluster only has a few ESXi Host.
- You know your environment very well because it’s small. They all fit into 1 rack. Architecture is simple. You have a mental picture of it in your head.
- You don’t buy hardware or VMware every quarter. Likely it’s every 2 years. Capacity planning and monitoring are simple.
- The workload is quite stable. You are not adding/removing/changing VM every day.
- Service Tier is an overkill as you only have 1-2 clusters for all workload.
Which of the above points apply to a large environment?
You are right. None.
As a result, SMB needs a purpose-built dashboards. It covers the following:
- Reclaimable Capacity
- When a VM Owner complains
Your main dashboard. It’s the first dashboard you check, likely on a daily basis as part of your cadence. It answers the no 1 question: is everything healthy?
This is what it looks like in vR Ops 6.3. I’ve added explanation so you can easily see that it’s layered into 4 areas.
The first element of Health is Availability. If a VM or ESXi is down, there is no need to talk about performance or capacity as the damn thing is dead 🙂
The Availability dashboard gives you details info. You can answer questions such as “When did it go down? For how long?”
The dashboard is also useful when you need to report uptime. You do need to create a report and customize it though. If you need it, email me your requirement.
Just because something is up, does not mean it’s fast. Performance dashboard provides the info here. The dashboard sports the new concept of Performance, which you can review here. It does not apply the formal SLA, as that’s not applicable in SMB. Even without SLA, you can use it to prove your innocence, or justify new hardware purchase.
Line Charts are used as performance problem might have started earlier, or it’s no longer happening and you’re doing a root cause.
If the performance issue is caused by villain VM, the dashboard lets you find the VM. Change the time line in the Top-N widget to the time where there is performance problem.
BTW, if you like the ability to find out which VM was causing the problem, send your thank you to Matthew Hurley.
Generally speaking, Performance problem happens because supply is not being met by demand. The Capacity dashboard gives detail info on the supply side. As there are only a few clusters, capacity management is much simpler.
Notice it takes into account performance.
If you mix Prod and Non Prod, capacity management becomes harder. Since the hardware is shared, we need to monitor at the overall cluster level. Since the Production VMs have a more stringent SLA, naturally their number reflects that. As a result, we need to show Prod and Non Prod differently. Let me know if you need it, as to me that complicates operations. This is another reason why I advocate separate cluster for Prod and Non Prod.
One common issue in virtual environment is VM sprawl. Some of these VMs end up not being used. You can reclaim CPU, RAM and Disk from these VMs.
- The easiest to reclaim is from orphaned VMs, as they are not even registered in vCenter.
- The second easiest is snapshot. You should only keep snapshot for 1 day or less.
Once the above is reclaimed, you need to look at Powered Off VMs and Idle VMs
- CPU and RAM are reclaimed from running VMs, as powered off VMs are no longer consuming the resource.
- CPU: claim from large VM (e.g. 8 vCPU or more). Avoid reclaiming from 2 vCPU unless you’ve completed the large VMs.
- RAM: claim from large VM (e.g. 16 GB RAM of more) that has Guest OS metrics. It’s more accurate than hypervisor metric.
The Reclaimable dashboard lists all the VMs that have been idle or powered off. It also lists the orphaned VMs and large snapshots.
If you configure vSphere hardening guide, and your Infra and VMs comply to it, you will see all green in the dashboard below. If not, you can see exactly which VM or infra is not complying. You can customize the default threshold, although it’s better than you customize the symptoms & alert instead.
You can see compliance for Network and vCenter too, under the vSphere Compliance widget. There is a drop-down there that is not shown.
Last but not least, your job is actually about making sure the VM is being served well. It’s a service. Your customers don’t care about your infrastructure. So when they complain that their VM has a problem, you need a dashboard that quickly prove if the problem is at your end or their end. TTI is not Time to Investigate, but Time to Innocence 😉
The Troubleshoot a VM dashboard is built exactly for that!
This dashboard is quite long, as it lets you check underlying ESXi and datastore. You can collapse the widget, as shown below, to see more.
Hope you find the material useful. If you do, go back to the Main Page. It gives you the big picture so you can see how everything fits together. If you already know how it all fits, you can go straight to download here.