From 594dce384f68e51aa9744c9cf9ca17877a84989e Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Wed, 11 Nov 2015 23:29:36 -0500 Subject: [PATCH] corrected sentences in shared file systems rst file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit added the where necessary in various places added plural where necessary added “a” where necessary Change-Id: I3225f4ae683d4ea1c638920246669b33e70bafad --- .../shared_file_systems_troubleshoot.rst | 28 ++++++++++--------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/doc/admin-guide-cloud/source/shared_file_systems_troubleshoot.rst b/doc/admin-guide-cloud/source/shared_file_systems_troubleshoot.rst index c976364635..da38a039f5 100644 --- a/doc/admin-guide-cloud/source/shared_file_systems_troubleshoot.rst +++ b/doc/admin-guide-cloud/source/shared_file_systems_troubleshoot.rst @@ -24,15 +24,15 @@ No valid host was found ~~~~~~~~~~~~~~~~~~~~~~~ You should manage share types very carefully. If share type contains invalid -extra spec scheduler will never find valid host for share of this type. +extra spec scheduler will never find a valid host for shares of this type. To diagnose this issue, make sure that scheduler service is running in debug mode, try to create a new share and look for message ``Failed to schedule create_share: No valid host was found.`` in ``/etc/var/log/manila-scheduler.log``. -To solve this issue look carefully through list of extra specs in share type -and list of share service reported capabilities and make sure that extra specs -are pointed in the right way. +To solve this issue look carefully through the list of extra specs in the +share type and list of share services reported capabilities. Make sure +that extra specs are pointed in the right way. Created share is unreachable ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -45,16 +45,18 @@ Service becomes unavailable after upgrade ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After upgrading the Shared File Systems service from version v1 to version -v2.x, please be attentive to update service endpoint in OpenStack Identity -Service. Use :command:`keystone service-list` to get service type related to -Shared File Systems service and then :command:`keystone service-list --service -` command. You will get endpoints expected from running -Shared File Systems service. Make sure that these endpoints are updated. -If it is not true, you need to delete outdated endpoints and create new ones. +v2.x, please be attentive to update the service endpoint in the OpenStack +Identity service. Use :command:`keystone service-list` to get service +type related to Shared File Systems service and then :command:`keystone +service-list --service ` command. You will get the +endpoints expected from running the Shared File Systems service. Make sure +that these endpoints are updated. +If it is not true, you need to delete the outdated endpoints and create +new ones. Failures during management of internal resources ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Some drivers in Shared File Systems service can create service entities, like -servers and networks. If it is necessary to reach it you can log in to tenant -``service`` and get manual control over it. +Some drivers in the Shared File Systems service can create service entities, +like servers and networks. If it is necessary to reach it you can log in to +tenant ``service`` and get manual control over it.