| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
NetApp drivers: NFS, iSCSI and FCP drivers have now the option to request |
| 5 |
ONTAP operations through REST API. The new option `netapp_use_legacy_client` |
| 6 |
switches between the old ZAPI client approach and new REST client. It is |
| 7 |
default to `True`, meaning that the drivers will keep working as before |
| 8 |
using ZAPI operations. If desired, this option can be set to `False` interacting |
| 9 |
with the storage using the new REST client. However, this new client still |
| 10 |
relies on ZAPI calls for consistency group snapshot operation. |
| 11 |
|
| 12 |
The drivers can only be configured with REST client when using ONTAP storage |
| 13 |
9.11.1 or newer. |
| 14 |
|
| 15 |
NOTE: Enabling ONTAP REST client changes the behavior of QoS specs. Earlier, |
| 16 |
QoS values could be represented in BPS (bytes per second), but now REST client |
| 17 |
only supports integer values represented in MBPS (Megabytes per second). |
| 18 |
It means that though the user specifies the value in BPS, it will be converted |
| 19 |
to MBPS and rounded up. |