objections Flashcards

1
Q

How are you different from DRS?

A
  • DRS only makes moves and focuses on memory and CPU in isolation
  • DRS focuses on only Memory or Compute at the host level. When it’s system picks up high utilization of either resource, it moves the biggest VM on that host to another random host with no knowledge of the available capacity of its target.
  • Does not tell you anything about capacity.
  • Has DRS every told you to provision a new host

The goal of DRS is host load balancing, not workload performance or infrastructure efficiency
•Despite balancing VMs, workloads and applications still suffer contention
•DRS only takes action when the cluster is unbalanced.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Vcops gives me sizing … What’s the difference between your sizing and theirs?

A
  • VCops is only designed for anomaly detection and will send you an alert when an issue has already taken place.
  • We give you the actual decisions
  • The difference is Vcops is only going to give you sizing decisions in isolation without taking into consideration placement and capacity
  • But it’s not about sizing or placement decisions in isolation
  • We make sizing and placement decisions while understanding the underlying capacity of your infrastructure.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Do you guys have historical data so when something happens I could drill down?

A
  • Turbonomic does have historical data that you can drill into going back two years and we can set it up so you can go back further but that’s not the main design of Turbonomic
  • What Turbonomic does is takes all of that data to understand the current state of your infrastructure and then gives you prescriptive actions to drive your infrastructure to its healthiest state so you don’t need to go through historical reports because we give you the road map to driving your environment to its most performant and efficient state.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How do you guys look at storage?

A
  • We understand all the storage controllers in your infrastructure, the aggregates that live on those controllers, the data stores that pull from those aggregates & the workloads that run on those data stores
  • What we are looking at from a storage perspective are the storage amount, storage provisioned, IOPS and latency
  • Turbonomic would never tell you to move vms between two data stores pulling from the same aggregates because they would both have the same IOPS and that wouldn’t make sense.
  • And what you’ll see is that we give you recommendations based on storage to drive you to a more performant state
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Do you have multi-tenancy capabilities?

A
  • Yes we do
  • If you go under the admin tab and hit user configuration you can add users into the environment and dictate what they can access and have control over by making them either an observer, advisor, automater or administrator.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Automation is not something we can just turn on… I don’t see us doing it…

A
  • That’s fine, once you have Turbononomic in your environment and begin trusting the actions we are providing then you can choose to start automating vmotions like lots of our customers do.
  • Do you use DRS? Then you already automate Vmotions
  • Crawl, walk, run
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Some VMs cannot be moved what can you do in those cases?

A

• In the policy tab we can create groups and placement policies to lock VMs to hosts, improving compliance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

I don’t have hot add enabled…. How do I size VMs without any downtime to my end users?

A

• You can schedule certain actions to only happen during a desired change window

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Do you guys look at the OS level for applications like SQL?

A
  • Yes, with our App edition we can tie into the WMI of Apps like SQL, JVM, TomCat to pull OS level data
  • We look at the whole IT stack looking at everything from the application down to the storage.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Do you guys do charge back?

A
  • Yes (Short Answer try not to get caught in this)
  • Through our green circle community, you can import reports our customers and your peers have created to use Turbo for charge/show back amongst other desired features
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

I have DRS rules already in place do I have to do the same in VMturbo?

A
  • No you don’t

* We import all of your rules/policies right from vSphere

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Do VMTurbo’s placement actions conflict with DRS?

A

• When Turbo is in full automation, you shouldn’t see DRS doing much of anything. We recommend that our customers turn DRS onto its less aggressive mode so it can serve the purpose of abandoning an ESX host in the event that one shuts down

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Why are some of the check boxes greyed out/can I take storage v-motions and resizes from VMT

A

• Out of the box DataStore browsing is disabled, go to Analysis to enable it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Can VMT resize storage?

A
  • Yes we can,
  • If you go to the policy tab and under action hit storage, then you can see where you can resize storage and even automate those actions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Does VMTurbo use agents?

A

• No completely agentless, lightweight OVA template

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are its specifications?

A

• 16 GB Mem, 4 vCPUs, 160 GB Disk

17
Q

How long will it take to “learn” my environment?

A

• Within 1 hour Turbo will start giving recommendations to drive risk out your infrastructure and bring it to a state of health. After a week start to gain insight into Max/Min.

18
Q

What is UI?

A
  • It’s an inverse relationship of utilization for the most constrained resource for an entity
  • Just a side note we install on Flash the new UI will be able to install on HTML 5
19
Q

Different from pDRS?

A

What pDRS does:

  • Captures patterns of VM utilization (CPU and Memory) over time (10+ days), stored in vROps (6.4+)
  • Reserves VM CPU or memory up to 1 hour in advance of predicted, cyclical resource spikes, triggering DRS to rebalance based on assumed load

•pDRS cannot protect all workloads, just the predictable ones, and unpredictable workloads can still cause contention, even with workloads protected by pDRS.
(Note: pDRS is relatively new – few customers have deployed it.)

How many of your workloads behave the same way every day. Every week?

“Predictive DRS helps prevent resource contention on hosts that run VMs with predictable utilization patterns.”

pDRS leverages the anomaly detection that is trained by operators via vROps.

vROps feeds DRS with CPU or MEM spikes that were identified as normal behavior (e.g. expected increased usage).

These expected (predicted) spikes will be sent to DRS an hour before they occur, and DRS will consider them as if they were real spikes (observed) and will handle them the same way.