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
745 B
745 B
Manage shares services
The Shared File Systems service provides API that allows to manage
running share services (Share
services API). Using manila service-list command, it is
possible to get a list of all kinds of running services. To select only
share services, you can pick items that have field binary
equals to manila-share. Also, you can enable or disable
share services using raw API requests. Disabling means that share
service excludes from scheduler cycle and new shares will not be placed
on disabled back end, but shares from this service stay available.