Gabriel Chapman

the software infrastructure to provision and manage those things and abstract away the complexity of having to deal with 7,000 volumes.

You can go in there and create tiers and precious metal tiers and align them any way you want, and you kind of automate that process.

And we saw a lot of that in the OpenStack world being now applied into the traditional VMware-based world, where I look at it from the standpoint, as a former VM administrator myself, I would have loved to be able to go in and set per VM level QoS

to segment performance between disparate virtual machines and make sure that there was no competition or resources, period.

And I think a lot of people would love to have that contract, but they definitely need to test it out and see how it works in practice.

And in theory, it sounds great, but in practice, it may be a different thing.

The beauty of our platform, because it's based on the solid-fire technologies, we already have about six years' worth of proof points.

around multi-tenancy disparate workloads, leveraging QoS technologies.

Now we have about, with the release of the vVol technology in the last software release, now we have customers at proof points that we can go back and say, hey, here in an HCI solution, here's the first one that actually provides fully functional vVol support.

And on top of it, we're gonna let you segment workload.

based on performance characteristics, and then we'll do 100% of it automated as it integrates with the common tools and practices that you use today.

I think that's a compelling argument for a lot of customers to start to take a serious look at it.

Fundamentally, if we look at this to bring it back home to what HCI is, it's not a storage technology.

Yes, the most complex and hard to lick problems are in the storage layer for hyperconverged infrastructure, but it's the most simple to manage and administer.

It's how big, how fast, and who should access it.

And that's really the three points that you should actually have to determine when you're provisioning storage constructs with inside a hyperconversion environment.

The value is in the packaging and simplification and rapid deployment and scalability of the solution is a common building block approach, right?

And then additionally to that, how you can scale the resources independent of each other.

So it's, you know,

Moving away from just the pure storage portion, talk points about it.