If you struggle with Capacity Management, then you’ve approached it with the wrong understanding. The issue is not with your technical skills. The issue is you don’t look at it from your customers viewpoint.
Let’s check your technical skills if you don’t trust me ?
- Can you architect a cluster where the performance matches physical? Easy, just don’t overcommit.
- Can you architect a cluster that can handle monster VM? Easy, just get lots of core per socket.
- Can you architect with very high availability? Easy, just have more HA host, more vSAN FTT and failure domain.
- Can you architect a cluster that can run lots of VMs? Easy, just get lots of big hosts.
- Can you optimize the performance? Sure, follow performance best practices and configure for performance.
- Can you squeeze the cost? Sure, minimize the hardware, CPU socket, and choose the best bang for the buck. You know all the vendors and their technology. You know the pro and cons of each.
You see, it’s not your technical skills. It’s how you present your solution. Remember this?
“Customers want it good, cheap, and fast. Let them pick any 2”
In IaaS business, this translates into
- Good = high performance, high availability, deep monitoring.
- Cheap = low $$
- Fast = soon. How fast you can get this service.
You want good high performance at cheap price? Wait until next generation Xeon and NVM arrive.
In IaaS, it is a service. Customers should not care about the underlying hardware model and architecture. Whether you’re using NSX or not, they should not and do not care.
So, present the following table. It provides 4 sample tiers for CIO & customers to choose from. Tell them the hardware & software are identical.
You should always start your presentation by explaining Tier 1. That’s the tier they expect for performance. They want it as good as physical. Give customers what they want to hear, else they will go to someone’s else cloud (e.g. Amazon or Azure).
Tier 1 sports performance guarantee. This is only possible because you do not overcommit. To the VM, it’s as good as it’s running alone in the box. No contention. There is no need for reservation, and every VM can run at 100% all day long.
What’s the catch?
Obviously, just like First Class seat, tier 1 is expensive. It’s suitable only for those latency sensitive apps.
Show them the price for Tier 1. If they are happy, end of discussion. You architect for Tier 1, as that’s the requirements. If your customers want to fly first class, then you should not stop them.
What if VM Owners wants something much cheaper, and don’t mind a small drop of performance?
You then offer Tier 2 & Tier 3. Explain that you can cut down the cost to any discount they want. But you need to match the over commitment. If they want 50% discount, then it’s 2:1 overcommit. If they want 67% discount, then it’s 3:1 overcommit. It’s that simple.
Any IT fresh graduate can do the above 🙂 No need seasoned IT Prof with 1-2+ decade of combat experience.
Your professionalism comes in here: The performance drops does not drop as low as the discount. You can achieve 50% at <50% performance drop.
How is that possible?
2 reasons impacting Demand: VM Size and VM Utilization.
You control the VM size. By not having monster VM in the lower tier, the IaaS has higher chance of giving good performance for everyone.
BTW, this is your solution to avoid over-provisioned to begin with.
From experience, we know VMs don’t run at 100% most of the time. This utilization + size helps deliver a good performance.
So we know at 2:1 overcommit, the performance degradation will not 50%. But what it will be? 10%, 30%?
BTW, 10% means that the resource is not available immediately 10% of the time. It does not mean that it’s never available. It’s just that there is a latency in getting the resource (e.g. CPU).
We can’t predict what the degradation will be, as it depends on the total utilization of the VMs, which is not in your control. However, we can monitor the degradation experienced by each VM.
This is where you tell CIO: “What is your comfort level?”
Now, we don’t know the impact to the application when there is latency in infrastructure. That depends on the application. Even on the same identical software, e.g. SQL Server 2016, the impact may differ as it depends on how you use that software. Different nature of business workload (e.g. batch vs OLTP) gets impacted differently even on the identical version of the software.
The good thing is we’re not measuring application. We are measuring infrastructure. Infra that takes the shape of service (meaning VM owners don’t really care the spec) cannot be measured by the hardware spec as that’s irrelevant. So you track how well a VM is served by the IaaS instead.
For example, for a Tier 1 VM, what the VM gets will be very close to what it wants. For example, CPU Contention will be below 0.3%, while Memory Contention will simply be 0%. Disk Latency maybe 5 ms (you need to specify it as it can’t be 0 ms).
A Tier 3 VM, on the other hand, will have worse SLA. The CPU Contention maybe 15% (you decide with CIO), the Disk latency maybe 40 ms (again, this is a business decision).
An SLA isn’t useful if it’s not tracked per VM. You track it every 5 minutes for every single VM. This is part of Operationalize Your World.
I talked earlier about controlling the demand by limiting the VM size. You specify the limit to VM size for each tier. For example, any VM in Tier 2 cannot span a physical socket. You will impact the hypervisor scheduler. Customer who wants monster VM is more than welcome to move to higher tier. You do not act as gatekeeper or government. It’s their money and they don’t appreciate you playing parent.
How do you encourage right-sizing?
Not by “we try to save company money” motherhood talk. This is business, and both Apps team and Infra team are professional. Avoid playing the government in internal IT. The Application Team expects to be treated as customers, not just colleague.
Develop a pricing model that is compelling for them to go small. Use this as best practice:
The above uses Discount and Tax. As a result, it’s much cheaper to go small. A 32 vCPU VM costs 32x of 4 vCPU, not 8x.
The above gets you the model. How about the actual price?
In business, there is no point if you can’t put a price.
Bad news, your price has been set by leading cloud players (AWS & Azure). It’s a commodity business using commodity software and hardware. The price of DC co-location and admin salary are pretty similar too.
All these means the price can’t differ that much. Using the airline analogy, the price among airlines are similar too.
Here is the price from AWS (as at 31 July 2017).
I use M4 series as that gives balance CPU & RAM. Other series are cheaper but they are using older hardware and does not provide balance combination.
From the above, I take the 1-year contract, 100% paid up front for comparison. In Enterprise IT, you may get budget annually and the budget can be transferred up front at the start of fiscal year.
The price above excludes Storage and Network. Only Compute. It also excludes Support, Monitoring, Reporting, Guest OS update, Network, Backup, Security.
It includes: DC facility rent, IaaS software + maintenance.
How do you calculate your price from above? You can take a comparison, and make it apple to apple.
I took 50 4 vCPU VM and 25 8 vCPU VM, and calculate the 3 year price.
To convert to private cloud, use 2:1 overcommit. AWS counts the HT as core.
Based on the above, you can see the price of AWS is high, as it > $100K per ESXi.
To determine your VM cost, you start by determining your total cost. I put half of AWS as I still think it’s reasonable. $396K for 7 ESXi still give you room for IT team salary, DC colocation, etc.
The above gives you your price for the equivalent AWS or Azure machine.
You should run your own calculation. Use your own overcommit ratio and VM size.
Once done, you should take this price to your internal customers. Have a Pricing discussion. When you order food at restaurant, does the price matter to you?
As the architect of the platform, you know the value of your creation best.
I hope this blog gives you food for thought. Capacity Management does not start when the VM is deployed, or the hardware was purchased. It starts much earlier than that. Go back to that time, as that’s how you can get out of the never ending right-sizing and argument over capacity.