Does Trident CSI support simultaneous dual ontap-san driver? | NetApp | Page 1

gleaming forge Nov 30, 2024, 8:10 AM

#

Each storage class should point to a dedicated NetApp storage/Trident backend, on the storage class config both use "backendType: ontap-san" which is identical for both Trident backends. How do I differentiate between them, using backendName: on second storage class didn't work. Should I set both backendType and backendName on all storge classes?
./tridentctl -n trident get backend
+-----------------------+----------------+--------------------------------------+--------+------------+---------+
| NAME | STORAGE DRIVER | UUID | STATE | USER-STATE | VOLUMES |
+-----------------------+----------------+--------------------------------------+--------+------------+---------+
| ontap-sim-san-backend | ontap-san | 68590ae9-0611-45e1-9307-b5b32a732876 | online | normal | 0 |
| ontap-san-backend | ontap-san | 99e28d8f-097e-4a68-8610-d0c57ff0d6b1 | online | normal | 6 |
+-----------------------+----------------+--------------------------------------+--------+------------+---------+

[kni@provisionhost-0-0 ~]$ ./tridentctl get -n trident backend -o json | jq '[.items[] | {backend: .name, storageClasses: [.storage[].storageClasses]|unique}]'

"backend": "ontap-san-backend",
"storageClasses": [
  [
    "ontap-san-storage",
    "ontap-san-storage-rwx"

"backend": "ontap-sim-san-backend", 
"storageClasses": [
  [
    "ontap-san-storage",   
    "ontap-san-storage-rwx"

^ On the last backend "ontap-sim-san-backend" I should only see a storage class called "ontap-sim-storage" instead I see two storage classes which ideally would belong only to the "ontap-san-backend".
Thanks

compact fossil Nov 30, 2024, 12:54 PM

#

You can work with labels on your backend config and put a matching selector in the StorageClass

compact fossil Dec 2, 2024, 9:02 AM

#

just to elaborate on that a bit. If you have a backend config that looks something like this:

kind: TridentBackendConfig
metadata:
  name: backend-cl1-sata
  namespace: trident
spec:
  ...
  labels:
    cluster: cl1
    disktype: sata
  ...

then you can create a matching StorageClass that looks like this:

kind: StorageClass
metadata:
  name: cl1-sata
provisioner: csi.trident.netapp.io
parameters:
  backendType: "ontap-nas"
  selector: "cluster=cl1; disktype=sata"

i.e. the selector parameter matches the corresponding labels on the backend as described here

gleaming forge Dec 2, 2024, 9:03 AM

#

Thanks for example, will check and report back with results.

#Does Trident CSI support simultaneous dual ontap-san driver?