Trident and SIS

[Nate-Itkin]

Does anyone know if Trident supports ONTAP 9 volume efficiency. I.e. configuring dedup, compression, compaction, etc on a volume when it's created?

I couldn't find anything about it.

Thanks,

Nate Itkin

[elementx]

Storage efficiencies happen "below" Trident - they work as they would with any other NFS or iSCSI shares (not just Trident)

There are some settings that can help you optimize how you use certain features (thin clones, snapshots)

https://netapp-trident.readthedocs.io/en/stable-v19.07/docker/use/backends/ontap_options.html#ontap-volume-options

[Nate-Itkin]

Except with AFF where some amount of SIS default behavior is a possibility, you would need to login to the controller to configure SIS after volume creation. Doesn't that leave a gap in automated storage provisioning?

[paul_stejskal]

By default all inline features are enabled with AFF. You can get good performance with Trident (I have seen where a certain auto manufacturer uses it quite successfully on AFF). If you create a volume unless the script does something funky or inline features are disabled, it should work just fine.

[Nate-Itkin]

Yes, but what about provisioning and managing efficiency on non-AFF?

[paul_stejskal]

I'm not sure if the API does configure dedupe or can. You might try https://github.com/NetApp/trident/issues and see if one of the Trident guys is available. I think they also are on Freenode IRC.

[elementx]

You could use the regular Trident or K8S tools to identify those volumes, and then ONTAP API or CLI to modify efficiency settings for them. I'm not aware of a built-in way.

For non-AFF storage, Trident volumes often come and go faster than you can deduplicate data, so maybe it'd work well for very static environments with lots of duplicate data.