94a4d30901
This allows specifying functions that further optimize the scheduling of shares across backend stanzas. This is needed due to a netapp-driver specific problem when using SVM scoped accounts. It does not have enough permissions to obtain the total_capacity_gb information, so it cannot calculate utilization, and therefore the goodness_function always returns 50 and end up scheduling shares always to the same pool. Closes-bug: #2073537 Change-Id: Ia151c50421e75282f633e0b004c2e6c1bda638f3
142 lines
5.3 KiB
YAML
142 lines
5.3 KiB
YAML
options:
|
|
share-backend-name:
|
|
type: string
|
|
default: netapp-ontap
|
|
description: |
|
|
The name given to the backend. This is used to generate the backend
|
|
configuration section. If two different configurations of the same
|
|
backend type are needed, then this config option can be used to separate
|
|
them in the backend configuration.
|
|
driver-handles-share-servers:
|
|
type: boolean
|
|
description: |
|
|
Whether the Manila driver should manage the Vservers within the
|
|
NetApp ONTAP cluster.
|
|
default: False
|
|
root-volume-aggregate-name:
|
|
type: string
|
|
description: |
|
|
Name of aggregate to create Vserver root volumes on. This option only
|
|
applies when the option 'driver-handles-share-servers' is set to True.
|
|
enabled-share-protocols:
|
|
type: string
|
|
description: |
|
|
Comma-separated list of NFS protocol versions that will be enabled on
|
|
the Vservers from the NetApp ONTAP cluster.
|
|
The supported versions are:
|
|
* nfs3
|
|
* nfs4.0
|
|
* nfs4.1
|
|
This option only applies when the option 'driver-handles-share-servers'
|
|
is set to True.
|
|
default: nfs3,nfs4.0,nfs4.1
|
|
vserver-name:
|
|
type: string
|
|
description: |
|
|
The name of the Vserver already configured within the NetApp ONTAP
|
|
cluster. This option is used only when 'driver-handles-share-servers' is
|
|
set to False.
|
|
management-address:
|
|
type: string
|
|
description: |
|
|
The management address (IP or hostname) for the NetApp ONTAP cluster.
|
|
admin-name:
|
|
type: string
|
|
default: admin
|
|
description: |
|
|
Administrative user account name used to access the storage system.
|
|
admin-password:
|
|
type: string
|
|
description: |
|
|
Password for the administrative user account specified in the
|
|
'admin-name' option.
|
|
transport-type:
|
|
type: string
|
|
description: |
|
|
Transport protocol for communicating with the storage system or proxy
|
|
server. Valid options include http and https.
|
|
default: http
|
|
netapp-server-port:
|
|
type: string
|
|
description: |
|
|
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.
|
|
default: ''
|
|
backend-availability-zone:
|
|
type: string
|
|
description: |
|
|
Zone where backend shared server would be created.
|
|
default: 'nova'
|
|
root-volume-name:
|
|
type: string
|
|
description: |
|
|
This option specifies name of the root volume that will be created when
|
|
a new SVM is created to correspond to a Manila share server.
|
|
default: 'root'
|
|
aggregate-name-search-pattern:
|
|
type: string
|
|
description: |
|
|
This option specifies a regular expression that is applied against all
|
|
available aggregates related to the SVM specified in the netapp_vserver
|
|
option. This filtered list will be reported to the Manila scheduler as
|
|
valid pools for provisioning new shares.
|
|
default: '(.*)'
|
|
standalone-network:
|
|
type: boolean
|
|
description: |
|
|
Standalone Network Plugin Use this plugin in stand-alone deployments of
|
|
OpenStack Manila
|
|
default: False
|
|
standalone-network-network-type:
|
|
type: string
|
|
description: |
|
|
Specify the network type as one of flat or vlan. If unspecified, the
|
|
driver assumes the network is non-segmented. If using vlan, specify
|
|
the standalone_network_plugin_segmentation_id option as well.
|
|
default: flat
|
|
standalone-network-segmentation-id:
|
|
type: string
|
|
description: |
|
|
Specify the segmentation ID that should be assigned to data LIFs through
|
|
which shares can be exported. This option is not necessary if the
|
|
standalone_network_plugin_network_type is set to flat
|
|
default: ''
|
|
standalone-network-mtu:
|
|
type: string
|
|
description: |
|
|
Maximum Transmission unit (MTU) value of the network.
|
|
default: '1500'
|
|
standalone-network-allowed-ip-ranges:
|
|
type: string
|
|
description: |
|
|
Specify the range of IP addresses that can be used on data LIFs through
|
|
which shares can be exported. An example of a valid range would be
|
|
10.0.0.10-10.0.0.254. If this value is not specified, the entire range
|
|
of IP addresses within the network computed by applying the value of
|
|
standalone_network_plugin_mask to the value of
|
|
standalone_network_plugin_gateway. In this case, the broadcast,
|
|
network, and gateway addresses are automatically excluded.
|
|
default: ''
|
|
standalone-network-mask:
|
|
type: string
|
|
description: |
|
|
Specify the subnet mask that should be configured on the data LIF through
|
|
which the share is exported. You can specify the CIDR suffix (without the
|
|
slash, e.g. 24) or the full netmask (e.g. 255.255.255.0).
|
|
default: "24"
|
|
standalone-network-gateway:
|
|
type: string
|
|
description: |
|
|
Specify the gateway IP address that should be configured on the data
|
|
LIF through which the share is exported. A Vserver static route is
|
|
configured using this gateway.
|
|
default: "172.16.31.1"
|
|
goodness-function:
|
|
type: string
|
|
description: |
|
|
Specify an optional goodness function (as a string) that will be
|
|
run against the backend to determine its goodness score for scheduling.
|
|
Please refer to the Manila documentation for the function structure,
|
|
valid operands and operators.
|
|
default: ""
|