Add support for specifying volume efficiency features for ONTAP backends

[acsulli]

ONTAP's storage efficiency features are applied, in an automatic manner, unevenly across the platforms. For example, as of ONTAP 9.2, AFF systems will have inline deduplication, compression, and compaction enabled for all volumes by default. However, non-AFF systems do not have this same configuration.

Additionally, for non-AFF systems, without expressly enabling volume efficiency, no efficiency is realized.

At a minimum, it would be ideal to be able to specify the following storage efficiency features for volumes provisioned to ONTAP backends:

• Enable/disable efficiency, i.e. the equivalent of volume efficiency on|off
• The name of the efficiency policy to use
• Compression inline and/or post-process
• Deduplication inline and/or post-process
• Compaction

For AFF systems, being able to specify cross-volume deduplication inline and/or post-process would also be ideal.

Andrew

[appelding]

+1 My customers would love to be able to use this as well. ONTAP Select is a case where those are not enabled by default. So having the possibility to tune this is a requirement.

[naitkin]

+1 My customer is using Trident on non-AFF storage. They would like to have this.

[StevenBarre]

+1 Looking to roll out Trident to our production cluster and need a way to enable dedup

[alessio-torelli]

+1 We would like to leverage storage efficiency from config as well for FAS

[gniltaws]

We would also love to be able to turn on deduplication with OpenShift & Trident.