Ameet Deulgaonkar

Hi.

Yes.

I'm the technical director in DFMG and overlooking this product.

Take a lot of vacations, do nothing.

And blame everybody else if things go wrong and take the credit if things go right.

Right, so this type is not the property, right?

So as Evan mentioned earlier, these services are defined in quantitative terms, right?

You mentioned things like IOPs per terabyte, right?

And you mentioned things like peak latency or an RPO if you're talking about a data protection service.

You define services in very abstract terms, something that you can measure after your provision and actually produce a report to a customer and say that, look, this is what I promised and this is what I delivered at the end.

Yeah, so that's probably the interesting question we need to answer.

How do we do this magic, right?

Now, if you look at it at the end of the day, to manage the SLOs, you need to know what are the capabilities of the resources, right?

And we need to discover the capabilities in the terms that I just explained to you, right, in terms of IOs per terabyte that the resource can deliver, what is its peak latency when I put more IO in it, and things like that.

So what we do is when you want to manage a storage system by, you know, social objectives, you go to our GUI and add it to the system.

And then we automatically discover the capability of the system, right?

For example, we use the reverse sizing process to figure out what's the total IOPS that can be done on a given node and aggregate, right?

And we book it back.

And we also know that for given workload of certain block size, certain percentage of random region, right?

What is the latency you expect from the system, right?