Ameet Deulgaonkar

But when we have ONTAP 9.1, and then when you have OnCommand Unified Manager or OPM, we start making use of this advanced headroom analytics that come in.

And we then make use of those information as well when placing these workloads.

Yeah, so, okay, when you asked the previous question, right, about API service in SLM, think about on-command API services as a platform for APIs, right?

It's basically a restful API platform and you can do a lot of things with that platform, right?

And if you look at the journey 1.1 and 1.0 and 1.2 has been that we wanted to finish the ONTAP story where we have complete APIs set for managing an ONTAP platform as is right.

Now, I think this is what Evan was alluding to earlier was that SLM and the APIs that it provides is more at the data fabric level, right?

Our vision is that with these APIs you should be able to manage an on-tap system and in future a solid file system in the same way, right?

And all the data management operations like, you know, taking a snapshot, replicating data to secondary storage and stuff like that, we want to create a common API for you to do that irrespective of the two endpoints you're talking to, right?

For example, in future you can easily envision saying that, look,

backup a data from SolidFire to ONTAP, right?

And you don't have to understand how it's done, right?

You just sort of say, provision me a volume with extreme performance that goes and sits on SolidFire, and then say, do a backup of that, and that the backup sits on, you know, value storage, which is ONTAP backed by, you know, SATA drives and things like that.

Or you could do flash-to-disk to cloud, right?

So the SLM API is not just provisioning API or setup API, but it will allow you to do complete data management, be it data movement, data cloning, replication, anything that you can think about in terms of an application lifecycle that you talk about.

Yeah, you can reach me on Twitter.

My handle is amith18.

Is it just me that's getting off on this?