NetApp Clustered Data ONTAP

The Shared File Systems service can be configured to use NetApp Clustered Data ONTAP (cDOT) version 8.2 and later.

The driver can work with two types of pools: FlexGroup and FlexVol. By default, it only works with FlexVol, if desired, the FlexGroup pool can be enabled together or standalone.

FlexGroup pool requires ONTAP version 9.8 or later.

Supported Operations

The following operations are supported on Clustered Data ONTAP:

• Create CIFS/NFS Share

• Delete CIFS/NFS Share

• Allow NFS Share access

  • IP access type is supported for NFS.

  • Read/write and read-only access are supported for NFS.

• Allow CIFS Share access

  • User access type is supported for CIFS.

  • Read/write access is supported for CIFS.

• Deny CIFS/NFS Share access

• Create snapshot

• Delete snapshot

• Create share from snapshot

• Extend share

• Shrink share

• Manage share

• Unmanage share

• Create consistency group

• Delete consistency group

• Create consistency group from CG snapshot

• Create CG snapshot

• Delete CG snapshot

• Create a replica (DHSS=False)

• Promote a replica (DHSS=False)

• Delete a replica (DHSS=False)

• Update a replica (DHSS=False)

• Create a replicated snapshot (DHSS=False)

• Delete a replicated snapshot (DHSS=False)

• Update a replicated snapshot (DHSS=False)

• Migrate share

• Migrate share server

• Create share backup

• Restore share backup

• Delete share backup

Note

The operations are not fully supported configuring FlexGroup pool:

• Consistency group operations are only supported configuring the driver without any FlexGroup pool.

• For FlexGroup share, create more than one replica is only allowed with ONTAP 9.9.1 and newer.

• Migration of FlexGroup shares is not allowed.

• Migration of share servers containing FlexGroup share is not allowed.

Note

DHSS is abbreviated from driver_handles_share_servers.

Supported Operating Modes

The cDOT driver supports both ‘driver_handles_share_servers’ (DHSS) modes.

If ‘driver_handles_share_servers’ is True, the driver will create a storage virtual machine (SVM, previously known as vServers) for each unique tenant network and provision each of a tenant’s shares into that SVM. This requires the user to specify both a share network as well as a share type with the DHSS extra spec set to True when creating shares.

If ‘driver_handles_share_servers’ is False, the manila admin must configure a single SVM, along with associated LIFs and protocol services, that will be used for provisioning shares. The SVM is specified in the manila config file.

Network approach

L3 connectivity between the storage cluster and manila host must exist, and VLAN segmentation may be configured. All of manila’s network plug-ins are supported with the cDOT driver.

Supported shared filesystems

• NFS (access by IP address or subnet)

• CIFS (authentication by user)

Required licenses

• NFS

• CIFS

• FlexClone

Known restrictions

• For CIFS shares an external Active Directory (AD) service is required. The AD details should be provided via a manila security service that is attached to the specified share network.

• Share access rules for CIFS shares may be created only for existing users in Active Directory.

• The time on external security services and storage must be synchronized. The maximum allowed clock skew is 5 minutes.

• cDOT supports only flat and VLAN network segmentation types.

How to take backup for NetApp shares

Starting from 2024.1, a concept named backup_type has been introduced. At present, it has been implemented for NetApp driver. The backup_type is a construct which consists of backup specific configuration parameters such as backup_type_name, netapp_backup_backend_section_name, netapp_backup_vserver, netapp_backup_share, netapp_snapmirror_job_timeout.

Note

The sample config will look like this: eng_data_backup is the backup_type here.:

[eng_data_backup]
netapp_backup_backend_section_name = ontap2
netapp_backup_vserver = backup_vserver_name
netapp_backup_volume = backup_volume_name_inside_vserver
netapp_snapmirror_job_timeout = 180

[nas_storage]
vendor_name = NetApp
share_driver = manila.share.drivers.netapp.common.NetAppDriver
driver_handles_share_servers = False
netapp_login = admin
....
....
enabled_backup_types = eng_data_backup

If the option netapp_backup_volume is not specified, the backup volume (destination volume) would be created automatically by the driver inside the vserver.

The options “netapp_backup_vserver” and “netapp_backup_volume” are optional and it works as below:

In case of “driver_handles_share_servers=true”, “netapp_backup_vserver” and “netapp_backup_volume” will be created by driver on “backend” mentioned under backup type stanza. In case of “driver_handles_share_servers=false”, it will use the existing vserver of the “backend” mentioned under backup type stanza and will create the new volume.

The manila.share.drivers.netapp.common.py Module

Unified driver for NetApp storage systems.

Supports multiple storage systems of different families and driver modes.

class NetAppDriver(*args, **kwargs)

Bases: object

“NetApp unified share storage driver.

Acts as a factory to create NetApp storage drivers based on the storage family and driver mode configured.

REQUIRED_FLAGS = ['netapp_storage_family', 'driver_handles_share_servers']