90060722a9
This patch introduces a new directory layout in doc/source in conformance with the OpenStack manuals project migration spec [1], moves the existing content in manila/doc/source into the new directories, and adjusts index files accordingly. This is the first step in the migration process as outlined in the spec. [1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html Partial-Bug: #1706181 Needed-By: I7924d94b82e7c8d9716bad7a219fc38c57970773 Depends-On: Ifc80fc56648cef74c85464321d1850e8c68449a0 Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454 Change-Id: Ieea33262101a1d2459492c1c8aaac5fe042279f6
3.5 KiB
Configure multiple back ends
An administrator can configure an instance of Manila to provision shares from one or more back ends. Each back end leverages an instance of a vendor-specific implementation of the Manila driver API.
The name of the back end is declared as a configuration option share_backend_name within a particular configuration stanza that contains the related configuration options for that back end.
Administrators can specify that a particular share type be explicitly associated with a single back end by including the extra spec share_backend_name with the name specified within the back end configuration stanza. When the Manila scheduler receives a provisioning request for a share type with this extra spec set, it will fulfill the share provisioning request on the specified back end (assuming all other scheduling criteria including available capacity are met).
Enable multiple back ends
To enable multiple share back ends, you must set the enabled_share_backends flag in the manila.conf file. This flag defines the names (separated by a comma) of the configuration stanzas for the different back ends: one name is associated to one configuration group for a back end.
The following example shows five configured back ends:
[DEFAULT]
enabled_share_backends=backendEMC1,backendEMC2,backendGeneric1,backendGeneric2,backendNetApp
[backendEMC1]
share_driver=manila.share.drivers.dell_emc.driver.EMCShareDriver
share_backend_name=backendEMC1
emc_share_backend=vnx
emc_nas_server=1.1.1.1
emc_nas_password=password
emc_nas_login=user
emc_nas_server_container=server_2
emc_nas_pool_name="Pool 1"
[backendEMC2]
share_driver=manila.share.drivers.dell_emc.driver.EMCShareDriver
share_backend_name=backendEMC2
emc_share_backend=vnx
emc_nas_server=1.1.1.1
emc_nas_password=password
emc_nas_login=user
emc_nas_server_container=server_3
emc_nas_pool_name="Pool 2"
[backendGeneric1]
share_driver=manila.share.drivers.generic.GenericShareDriver
share_backend_name=one_name_for_two_backends
service_instance_user=ubuntu_user
service_instance_password=ubuntu_user_password
service_image_name=ubuntu_image_name
path_to_private_key=/home/foouser/.ssh/id_rsa
path_to_public_key=/home/foouser/.ssh/id_rsa.pub
[backendGeneric2]
share_driver=manila.share.drivers.generic.GenericShareDriver
share_backend_name=one_name_for_two_backends
service_instance_user=centos_user
service_instance_password=centos_user_password
service_image_name=centos_image_name
path_to_private_key=/home/baruser/.ssh/id_rsa
path_to_public_key=/home/baruser/.ssh/id_rsa.pub
[backendNetApp]
share_driver = manila.share.drivers.netapp.common.NetAppDriver
driver_handles_share_servers = True
share_backend_name=backendNetApp
netapp_login=user
netapp_password=password
netapp_server_hostname=1.1.1.1
netapp_root_volume_aggregate=aggr01