Ameet Deulgaonkar

And it depends on how much of cache you have in the system and things like that.

So we catalog all this information in our database.

And when a user comes and says, like you just said, that you want a terabyte of storage with certain service level, we take all the SLOs into account, right?

We take into account the latency requirements, the IOPs per terabyte requirements, the RPO requirements, right?

Not to mention RPO is very important when you talk about disaster recovery, right?

And then we figure out what is the best place to onboard that workload, right?

It could be a file share or a volume.

and then we go and do the appropriate provisioning in terms of storage configuration like provisioning volume settings, QoS settings, and other things.

The properties that you can define or the attributes that you can use today to define a service level is mostly performance and protection, right?

Because these two things are fundamental in terms of any service, storage service, right, that you offer.

In terms of high availability and many other things, they're pretty much standardized, right?

All CMODE systems are developed in an HA configuration, right?

They kind of provide a similar kind of availability.

Or the only difference we see is in a metro cluster and non-metro cluster scenario where you can think about the availability going from four nines to five nines and things like that.

But the fundamental problem is in terms of defining a performance objective and a protection objective.

And today, the first version talks about specifying these objectives when you define a service level.

Yeah, and I think we realize this kind of, you know, we know that there are different spectrum of customers we're talking about here, right, at the extreme.

And we have these large enterprises who want the customizability that you're talking about.

And maybe there are other customers in the SMB segment who just want a very simple process.

They don't care what's happening underneath.