The NetApp unified driver for ONTAP without share server management is a driver interface from OpenStack Manila to NetApp ONTAP storage controllers to accomplish provisioning and management of shared file systems within the scope of a single SVM (Vserver).
To set up the NetApp ONTAP driver without Share Server
management, the following stanza should be added to the Manila
configuration file (manila.conf):
[cdotSingleSVM]
share_backend_name=cdotSingleSVM
share_driver = manila.share.drivers.netapp.common.NetAppDriver
driver_handles_share_servers=False
netapp_storage_family=ontap_cluster
netapp_server_hostname=hostname
netapp_server_port=80
netapp_login=admin_username
netapp_password=admin_password
netapp_vserver=svm_name
netapp_transport_type=https
netapp_aggregate_name_search_pattern=^((?!aggr0).)*$
Be sure that the value of the enabled_share_backends option in
the [DEFAULT] stanza includes the name of the stanza you chose
for the backend.
The value of driver_handles_share_servers MUST be set to
False if you want the driver to operate without managing share
servers.
Table 6.15, “Configuration options for ONTAP without Share Server management” lists the configuration options available for the unified driver for an ONTAP deployment that does not manage share servers.
Option |
Type |
Default Value |
Description |
|---|---|---|---|
|
Required |
The name used by Manila to refer to the Manila backend |
|
|
Required |
manila.share.drivers.generic.GenericShareDriver |
Set the value to manila.share.drivers.netapp.common.NetAppDriver |
|
Required |
Denotes whether the driver should handle the responsibility of managing share servers. This must be set to |
|
|
Required |
The hostname or IP address for the storage system or proxy server. The value of this option should be the IP address of either the cluster management LIF or the SVM management LIF. |
|
|
Optional |
The TCP port to use for communication with the storage system or proxy server. If not specified, ONTAP drivers will use 80 for HTTP and 443 for HTTPS. |
|
|
Required |
Administrative user account name used to access the storage system. |
|
|
Required |
Password for the administrative user account specified in the |
|
|
Required |
|
Transport protocol for communicating with the storage system or proxy server. Valid options include |
|
Required |
This option specifies the storage virtual machine (previously called a Vserver) name on the storage cluster on which provisioning of shared file systems should occur. This parameter is required if the driver is to operate without managing share servers (that is, be limited to the scope of a single SVM). |
|
|
Required |
|
The storage family type used on the storage system; valid values are |
|
Optional |
|
This option specifies a string replacement template that is applied when naming FlexVol volumes that are created as a result of provisioning requests. |
|
Optional |
|
This option specifies a string replacement template that is applied when naming QoS policies created for FlexVol volumes created by Manila. |
|
Optional |
|
This option specifies the percentage of share space set aside as reserve for snapshot usage. Valid values range from 0 to 90. |
|
Optional |
|
This option specifies a regular expression that is applied against all available aggregates related to the SVM specified in the |
|
Optional |
This option specifies a string to identify a replication domain. Manila will allow all backends with the same replication domain to replicate to each other. If this is left blank, the backend will not support replication. If provided, all backends within the replication domain should have their configuration stanzas included in the backends configuration file. See “Sample manila.conf” for examples. Ensure all ONTAP clusters and SVMs within the replication domain are peered and have intercluster LIFs configured. See “Storage Virtual Machine Considerations” |
|
|
Optional |
|
This expression is used by the scheduler as a filter in determining share placement. Using this expression, the scheduler is instructed to NOT place volumes on storage controllers that may become overutilized. The default value is “capabilities.utilization < 70”. Capabilities.utilization refers to ONTAP storage node headroom. See “Manila scheduling and resource pool selection” for more information on filters and weighers. |
|
Optional |
|
This expression is used by the scheduler to assign weighting in determining share placement. Using this expression, the scheduler places shares on lesser-utilized storage controllers. The default value is “100 - capabilities.utilization”. Capabilities.utilization refers to ONTAP storage node headroom. See “Manila scheduling and resource pool selection” for more information on filters and weighers. |
|
Optional |
This option is a comma-separated list of options (valid values include |
|
|
Optional |
|
A regular expression to limit the API tracing. This option is honored only if enabling |
|
Optional |
|
This option specifies the time interval in seconds at which Manila polls the backend for the progress and health of an ongoing migration. |
|
Optional |
|
This option specifies the default file operations to apply to a FPolicy, when not provided with |
|
Optional |
|
This option specifies a string replacement template that is applied when naming FPolicy policies created by Manila. |
|
Optional |
|
This option specifies a string replacement template that is applied when naming FPolicy events created by Manila. |
Table 6.15. Configuration options for ONTAP without Share Server management
Caution
If you specify an account in the netapp_login option that only
has SVM administration privileges (rather than cluster
administration privileges), some advanced features of the NetApp
unified driver will not work and you may see warnings in the Manila
logs. See Account Permission Considerations
for more details on the required access level permissions for an SVM
admin account.
This document is licensed under Apache 2.0 license.