Nagananda Anur

I think that's the whole idea.

Essentially, for a given tenant associate what kind of service level they can consume and how much of that service level type

that they can consume and then SLM has that knowledge and whenever it provisions checks against those entitlements and provisions it you no longer have to specify tenancy to object level that you can easily abstract that kind of functionality.

Yeah, excellent point.

If you look at SLM product, right, the way we ship it is SLM product ships with what we call the platform APIs, the APIs which gives the programmatic access to all our on-tap platforms.

We ship with that, and as well as we ship SLO APIs.

So sometimes, you know, there are some customers who prefer to build solutions across using both.

So in your scenario, in the scenario what you're talking,

where, you know, you created a file share and you need to associate an export policy with it.

And then there will be API for you to associate an export policy.

Yeah, we provide those APIs.

And then create a file share associated with an export policy.

Then, you know, eventually you should be able to mount your host to, you know, put it in Oracle or any application that you wanted on it.

So you've got to be able to do it.

We ship all the APIs required for it.

Oh, good.

So, actually, you know, first of all, you know, we've been talking about SLM right now.

It simplifies the consumption and everything.

But as Amit and Evan was talking about, all the functionality that SLM has has been exposed as REST APIs.

In other words, you can use it like a Lego block and fit into your any environment.