First question was how many of us were more than 50% virtualized, I didn’t see anyone without their hand up. I applaud us.
What are the implications of being 50% or more virtualized?
New and more abstractions, more dynamic
More stakeholders, dis-aggregation
What capacity problem areas get amplified?
Reactive capacity remediations
Purchase, optimize for efficiency and cost
Collaborate & Report
Tools that we use to monitor do not always agree. I’ve experienced this issue. We all have. The other issue is the tools have alerts but those alerts are usually false positives when it comes to performance. Noisy alerts cause us to miss the important alerts. Some time ago I declared alerting “broken”. We would ignore them or we would have to spend entirely too much time validating their truth.
Staying a head of the demand in our infrastructures can be challenging. I actually accomplished this for a while with an agreement with my partner for buying blades. I had a subscription plan setup so that compute resources were shipped to on a monthly schedule.
There is an awesome slide titled “Get the right metrics”. It describes capacity and demand concepts.
Contention can show up in different ways, dropped packets, CPU ready, memory contention, latency etc. Contention is the difference between what a VM gets and what a VM wants.
Humans can feel about 10% degradation in speed.
In vCenter Operations, you should investigate “health” issues immediately. Consumed memory has no bearing on what a VM actually needs. Even as consumed goes up and down demand may stay steady.
Looking for symptoms slide is another good one. Goes through examples of under, over, and proper provisioned machines. Demand is a good thing to look at. Cannot just use one symptom to solve a problem.
A see a pattern here… Another good slide is “Mapping Symptoms to Problems”.
Get the right metrics
Change your mindset
Watch for symptoms
Putting it all together
Map symptoms to problems
Remediate the virtual way
Overall a good session of VMware vCenter Operations.