From 771e527fa2a6e70e4377f2f8a86e72e5d595ea97 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Thu, 12 Nov 2015 00:19:43 -0500 Subject: [PATCH] cleanup of shared file systems scheduling file changed sentences added the and a where necessary reworded sentences Change-Id: I2b5f913b223f63b12d5d14656a7aa966ac7fd7c7 --- .../source/shared_file_systems_scheduling.rst | 35 +++++++++---------- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/doc/admin-guide-cloud/source/shared_file_systems_scheduling.rst b/doc/admin-guide-cloud/source/shared_file_systems_scheduling.rst index 833de32d8c..a8de9fe407 100644 --- a/doc/admin-guide-cloud/source/shared_file_systems_scheduling.rst +++ b/doc/admin-guide-cloud/source/shared_file_systems_scheduling.rst @@ -4,30 +4,29 @@ Scheduling ========== -The Shared File Systems service provides unified access for variety of +The Shared File Systems service provides unified access for a variety of different types of shared file systems. To achieve this, the Shared File Systems service uses a scheduler. The scheduler collects information from -active share services and takes decisions, what share service will be used to -create a new share. To manage this process, the Shared File Systems service -provides Share types API. +the active shared services and makes decisions such as what shared services +will be used to create a new share. To manage this process, the Shared +File Systems service provides Share types API. A share type is a list from key-value pairs called extra-specs. Some of them, -called required and un-scoped extra-specs, scheduler uses for lookup the -share service suitable for new share with specified share type. For more -information about extra-specs and their type, see `Capabilities and Extra-Specs -`_ section in developer documentation. +called required and un-scoped extra-specs, the scheduler uses for lookup of +the shared service suitable for a new share with the specified share type. +For more information about extra-specs and their type, see `Capabilities +and Extra-Specs `_ section in developer documentation. -The general scheduler workflow in described below. +The general scheduler workflow is described below. -#. Share services report information about number of existing pools, their +#. Share services report information about the number of existing pools, their capacities and capabilities. -#. When request on share creation comes in, scheduler picks a service and pool - that fits the need best to serve the request, using share type filters and - back end capabilities. If back end capabilities passes thought all filters - request to the selected back end where the target pool resides. +#. When a request on share creation comes in, the scheduler picks a service + and pool that fits the need best to serve the request, using share type + filters and back end capabilities. If back end capabilities pass through, + all filters request to the selected back end where the target pool resides. -#. Share driver gets the message and lets the target pool serve the request - as scheduler instructed. The scoped and un-scoped share type extra-specs - are available for the driver implementation to use as needed. +#. The share driver gets the message and lets the target pool serve the + request as the scheduler instructs. The scoped and un-scoped share type + extra-specs are available for the driver implementation to use as needed.