#Cluster selector or how to attach storage classes to separate ONTAP clusters?

1 messages · Page 1 of 1 (latest)

fierce urchin
#

I believe it's pretty obvious, but I still can't see it. Let's assume I've a TBC that says:

defaults:
exportPolicy: nfs_exports
snapshotPolicy: none
snapshotReserve: "0"
spaceReserve: none
labels:
cluster: ontap-cluster2

and then a storage class that goes:

parameters:
backendType: ontap-nas-fexgroup
provisioningType: thin
selector: cluster=ontap-cluster2

But when I try to create a volume the result is:

rpc error: code = Unknown desc = no available backends for storage class fg-storageclass

If selector is removed (which is the case with what would be ontap-cluster1) volume is being created.

Is it safe to assume those labels and selectors work only when storage pools are involved?

elder atlas
fierce urchin
#

Thank you very much, Scotty! It was all there, but I've a typo in backendType... shame you don't support fexgroups - it's a thing! 😄

elder atlas
jaunty girder
#

Fexgroups. Maybe thats what we should call configs for AFX? 😉

sly sorrel
#

In my case, IHAC with a 4-node cluster with an AFF-A250 and an AFF-C250, and we wanted to be able to specify from which to provision. I used that KB and setup a separate backend for every node. The A250 had performance=high and the C250 had performance=medium labels. What was confusing is that it seemed like you could also do this through the StoragePools parameter in the StorageClass? I couldn't find any examples though. Is this possible?

remote atlas
#

the storagePools parameter filters on backend name + aggregates
while the selector parameter filters on the backend label