openstack-manuals/doc/admin-guide-cloud/source/shared_file_systems_multi_backend.rst
Joseph Robinson 856316c7dc [User Guides] Shared File Systems Section Editing
Editing the Shared File Systems Section for the
Cloud Admin Guide.

1. Reviewing the shared_file_system.rst files for
sentence length, articles, and repetition.
2. Incorporating Admin User Guide content by changing file names and
editing content:
-cli_manage_shares.rst > shared_file_systems_manage_shares_cli.rst
-dashboard_manage_shares.rst > shared_file_systems_manage_shares_dashboard.rst

Change-Id: Ibe4ced6cc6ab20196c7de16b38aa9c550ffab1b2
Implements: blueprint user-guides-reorganised
2016-01-23 18:55:52 +00:00

62 lines
2.1 KiB
ReStructuredText

.. _shared_file_systems_multi_backend:
===========================
Multi-storage configuration
===========================
The Shared File Systems service can provide access to multiple file storage
back ends. In general, the workflow with multiple back ends looks similar
to the Block Storage service one, see :ref:`Configure multiple-storage back
ends in Openstack Block Storage service <multi_backend>`.
Using ``manila.conf``, you can spawn multiple share services. To do it, you
should set the `enabled_share_backends` flag in the ``manila.conf`` file. This
flag defines the comma-separated names of the configuration stanzas for the
different back ends. One name is associated to one configuration group for a
back end.
The following example runs three configured share services:
.. code-block:: ini
:linenos:
[DEFAULT]
enabled_share_backends=backendEMC2,backendGeneric1,backendNetApp
[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
[backendEMC2]
share_driver=manila.share.drivers.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"
[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
To spawn separate groups of share services, you can use separate configuration
files. If it is necessary to control each back end in a separate way, you
should provide a single configuration file per each back end.
.. toctree::
shared_file_systems_scheduling.rst
shared_file_systems_services_manage.rst