#You should be able to use the `na ontap

1 messages · Page 1 of 1 (latest)

fallen tulip
#

The problem is that we have multiple clusters that volumes could exist on. So, rather than check each one for an existing volume, it was convenient to go to AIQUM and check one place for the volume.

pale hemlock
#

ahhhh, that a problem. outside of running the rest_info command on each cluster, i don't know of another way off the top of my head

fallen tulip
#

Thanks. We may need to search each cluster individually if no one else has a better idea. Maybe I just need to let go of the WFA methodology? 🙂

vapid dagger
#

There may be a way to use the API gateway in AIQUM to query them all rather than you having to do it for each cluster manually but I’ll have to go look at the documentation as I’ve not used it in a while

plush bough
#

are you thinking the datacenter api in aiqum?

GET /datacenter/storage/volumes

Retrieves volumes.

Examples
Retrieving a list of volumes in the datacenter sorted by "name":

GET "/api/datacenter/storage/volumes?order_by=name"

Retrieving a list of volumes in the datacenter filtered using "cluster.name":

GET "/api/datacenter/storage/volumes?cluster.name=cluster1"

Retrieving a list of volumes in the datacenter filtered using "svm.name":

GET "/api/datacenter/storage/volumes?svm.name=svm1"

#

looking at that again, i think that's just what's in um.

fallen tulip
#

I know how to query AIQUM for volumes... there is an Ansible module for that.
The problem is that once you create a new volume, AIQUM doesn't know about it until the next time it polls the cluster that the volume was created on (which, by default, is every 15 minutes). So, if you try to run the volume creation playbook again within that 15 minutes, it will try to create the same volume again so it will fail.