openstack/openstack-manuals
Code Issues Proposed changes

corrected sentences in shared file systems rst file

Browse Source 
added the where necessary in various places
added plural where necessary
added “a” where necessary

Change-Id: I3225f4ae683d4ea1c638920246669b33e70bafad
This commit is contained in:
Shilla Saebi 2015-11-11 23:29:36 -05:00
parent a59f55a30d
commit 594dce384f
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/admin-guide-cloud/source/shared_file_systems_troubleshoot.rst
View File

@ -24,15 +24,15 @@ No valid host was found
~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~
You should manage share types very carefully. If share type contains invalid 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 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 debug mode, try to create a new share and look for message ``Failed to
schedule create_share: No valid host was found.`` in schedule create_share: No valid host was found.`` in
``/etc/var/log/manila-scheduler.log``. ``/etc/var/log/manila-scheduler.log``.
To solve this issue look carefully through list of extra specs in share type To solve this issue look carefully through the list of extra specs in the
and list of share service reported capabilities and make sure that extra specs share type and list of share services reported capabilities. Make sure
are pointed in the right way. that extra specs are pointed in the right way.
Created share is unreachable 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 After upgrading the Shared File Systems service from version v1 to version
v2.x, please be attentive to update service endpoint in OpenStack Identity v2.x, please be attentive to update the service endpoint in the OpenStack
Service. Use :command:`keystone service-list` to get service type related to Identity service. Use :command:`keystone service-list` to get service
Shared File Systems service and then :command:`keystone service-list --service type related to Shared File Systems service and then :command:`keystone
<share-service-type>` command. You will get endpoints expected from running service-list --service <share-service-type>` command. You will get the
Shared File Systems service. Make sure that these endpoints are updated. endpoints expected from running the Shared File Systems service. Make sure
If it is not true, you need to delete outdated endpoints and create new ones. 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 Failures during management of internal resources
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Some drivers in Shared File Systems service can create service entities, like Some drivers in the Shared File Systems service can create service entities,
servers and networks. If it is necessary to reach it you can log in to tenant like servers and networks. If it is necessary to reach it you can log in to
``service`` and get manual control over it. tenant ``service`` and get manual control over it.