openstack-manuals/doc/admin-guide/source/shared_file_systems_multi_backend.rst

62 lines
2.1 KiB
ReStructuredText
Raw Normal View History

.. _shared_file_systems_multi_backend:
===========================
Multi-storage configuration
===========================
Cloud Admin Guide: Shared File Systems updated information After the technical review the Shared File Systems service documentation in the Cloud Admin Guide needs to be updated. Read and fixed some typos and incorrect English constructions in the sentences of all sections. Fixed indentations in code, tip and note directives. Also updated the following info: * Removed references to the Generic driver, because it is default only on Devstack. And even for Devstack the default driver is going to be changed. * Divided 'Create share' subsection on 3 subsections: added general concepts and info of creating a share in 2 back end modes. * Added info that with StandaloneNetworkPlugin the Shared File Systems service can be configured without Networking and Compute services. * Added export paths for GlusterFS and HDFS. * Added notes what driver in what mode you use in examples and a noted what modes exist and can be configured. * Added a console sample for "manila rate-limits" command and described how to add API rate limits. * Removed information and samples about a quota classes because they are not used in the Shared File Systems service and are not working properly for the current moment (in Liberty release). * Added second purpose of the share types. * Removed '/etc/manila/' in manila.conf file, because its path can be customly changed. * Said that consistency groups is the experimental part of API starting with Liberty release. * Updated a sample in shared_file_systems_multi_backend.html file. * Removed 'Storage' from the Shared File Systems service official name according to [1] document. [1] http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Change-Id: I0530ea3c6bf74311e271cdabca26cd10afcddc92 Closes-Bug: #1508457
2015-10-21 16:11:00 +03:00
The Shared File Systems service can provide access to multiple file storage
back ends. In general, the workflow with multiple back ends looks similar
Cloud Admin Guide: Shared File Systems updated information After the technical review the Shared File Systems service documentation in the Cloud Admin Guide needs to be updated. Read and fixed some typos and incorrect English constructions in the sentences of all sections. Fixed indentations in code, tip and note directives. Also updated the following info: * Removed references to the Generic driver, because it is default only on Devstack. And even for Devstack the default driver is going to be changed. * Divided 'Create share' subsection on 3 subsections: added general concepts and info of creating a share in 2 back end modes. * Added info that with StandaloneNetworkPlugin the Shared File Systems service can be configured without Networking and Compute services. * Added export paths for GlusterFS and HDFS. * Added notes what driver in what mode you use in examples and a noted what modes exist and can be configured. * Added a console sample for "manila rate-limits" command and described how to add API rate limits. * Removed information and samples about a quota classes because they are not used in the Shared File Systems service and are not working properly for the current moment (in Liberty release). * Added second purpose of the share types. * Removed '/etc/manila/' in manila.conf file, because its path can be customly changed. * Said that consistency groups is the experimental part of API starting with Liberty release. * Updated a sample in shared_file_systems_multi_backend.html file. * Removed 'Storage' from the Shared File Systems service official name according to [1] document. [1] http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Change-Id: I0530ea3c6bf74311e271cdabca26cd10afcddc92 Closes-Bug: #1508457
2015-10-21 16:11:00 +03:00
to the Block Storage service one, see :ref:`Configure multiple-storage back
ends in 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
Cloud Admin Guide: Shared File Systems updated information After the technical review the Shared File Systems service documentation in the Cloud Admin Guide needs to be updated. Read and fixed some typos and incorrect English constructions in the sentences of all sections. Fixed indentations in code, tip and note directives. Also updated the following info: * Removed references to the Generic driver, because it is default only on Devstack. And even for Devstack the default driver is going to be changed. * Divided 'Create share' subsection on 3 subsections: added general concepts and info of creating a share in 2 back end modes. * Added info that with StandaloneNetworkPlugin the Shared File Systems service can be configured without Networking and Compute services. * Added export paths for GlusterFS and HDFS. * Added notes what driver in what mode you use in examples and a noted what modes exist and can be configured. * Added a console sample for "manila rate-limits" command and described how to add API rate limits. * Removed information and samples about a quota classes because they are not used in the Shared File Systems service and are not working properly for the current moment (in Liberty release). * Added second purpose of the share types. * Removed '/etc/manila/' in manila.conf file, because its path can be customly changed. * Said that consistency groups is the experimental part of API starting with Liberty release. * Updated a sample in shared_file_systems_multi_backend.html file. * Removed 'Storage' from the Shared File Systems service official name according to [1] document. [1] http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Change-Id: I0530ea3c6bf74311e271cdabca26cd10afcddc92 Closes-Bug: #1508457
2015-10-21 16:11:00 +03:00
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:
Cloud Admin Guide: Shared File Systems updated information After the technical review the Shared File Systems service documentation in the Cloud Admin Guide needs to be updated. Read and fixed some typos and incorrect English constructions in the sentences of all sections. Fixed indentations in code, tip and note directives. Also updated the following info: * Removed references to the Generic driver, because it is default only on Devstack. And even for Devstack the default driver is going to be changed. * Divided 'Create share' subsection on 3 subsections: added general concepts and info of creating a share in 2 back end modes. * Added info that with StandaloneNetworkPlugin the Shared File Systems service can be configured without Networking and Compute services. * Added export paths for GlusterFS and HDFS. * Added notes what driver in what mode you use in examples and a noted what modes exist and can be configured. * Added a console sample for "manila rate-limits" command and described how to add API rate limits. * Removed information and samples about a quota classes because they are not used in the Shared File Systems service and are not working properly for the current moment (in Liberty release). * Added second purpose of the share types. * Removed '/etc/manila/' in manila.conf file, because its path can be customly changed. * Said that consistency groups is the experimental part of API starting with Liberty release. * Updated a sample in shared_file_systems_multi_backend.html file. * Removed 'Storage' from the Shared File Systems service official name according to [1] document. [1] http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Change-Id: I0530ea3c6bf74311e271cdabca26cd10afcddc92 Closes-Bug: #1508457
2015-10-21 16:11:00 +03:00
[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