doc: move stuff from contributor to admin

As agreed in weekly manila community meetings and at the
Queens PTG, several documents currently presented to contributors
are really of general interest to cloud administrators and should
be presented accordingly.

Move the docs on manila back ends, the feature support mapping,
capabilities and extra specs, and export locations and metatdata
to the admin section.

Change-Id: I6d9dec56890fb3a9bc0539c45c43233517cea048

doc/source/admin/export_location_metadata.rst

@@ -12,7 +12,7 @@ in the database and they are available to the API service, which may expose
 them through the REST API or use them for filtering.
 
 Metadata Keys
-=============
+-------------
 Only keys defined in this document are valid. Arbitrary driver-defined keys
 are not allowed. The following keys are defined:
 

doc/source/admin/glusterfs_driver.rst

@@ -80,10 +80,6 @@ back to key based authentication, using the key specified by
 ``glusterfs_path_to_private_key``, or, in lack of that, a key at
 one of the OpenSSH-style default key locations (*~/.ssh/id_{r,d,ecd}sa*).
 
-For further (non driver specific) configuration of Ganesha, see
-:doc:`ganesha`. It is recommended to consult with :doc:`ganesha`:
-:ref:`ganesha_known_issues` too.
-
 Layouts have also their set of parameters, see :ref:`glusterfs_layouts` about
 that.
 

doc/source/admin/index.rst

@@ -53,5 +53,37 @@ deployment.
    shared-file-systems-multi-backend.rst
    shared-file-systems-networking.rst
    shared-file-systems-troubleshoot.rst
+   share_back_ends_feature_support_mapping
+   capabilities_and_extra_specs
+   export_location_metadata
 
+Supported share back ends
+-------------------------
+
+The manila share service must be configured to use drivers for one or
+more storage back ends, as described in general terms below.  See the
+drivers section in the `Configuration Reference
+<https://docs.openstack.org/manila/latest/configuration/shared-file-systems/drivers.html>`_
+for detailed configuration options for
+each back end.
+
+.. toctree::
+   :maxdepth: 3
+
+   container_driver
+   zfs_on_linux_driver
+   netapp_cluster_mode_driver
+   emc_isilon_driver
+   emc_vnx_driver
+   emc_unity_driver
+   generic_driver
+   glusterfs_driver
+   glusterfs_native_driver
+   cephfs_driver
+   gpfs_driver
+   huawei_nas_driver
+   hdfs_native_driver
+   hitachi_hnas_driver
+   hpe_3par_driver
+   tegile_driver
 

doc/source/admin/shared-file-systems-share-migration.rst

@@ -237,7 +237,7 @@ each one below:
   * export: The export path of the share. Automatically formatted by the Data
     Service with the share's ``admin_only`` export location.
   * path: The path to mount the share. Automatically formatted by the Data
-    Serivce according to the mount_tmp_location config option.
+    Service according to the mount_tmp_location config option.
 
   The default value for this config option is::
 

doc/source/contributor/index.rst

@@ -36,6 +36,7 @@ Programming HowTos and Tutorials
     commit_message_tags
     guru_meditation_report
     user_messages
+    ganesha
 
 
 Background Concepts for manila
@@ -83,48 +84,10 @@ Module Reference
    scheduler
    fakes
    manila
-   ganesha
    share_replication
    driver_filter_goodness_weigher
    share_migration
 
-Capabilities and Extra-Specs
-----------------------------
-.. toctree::
-   :maxdepth: 3
-
-   capabilities_and_extra_specs
-   export_location_metadata
-
-Share backends feature support mapping
---------------------------------------
-.. toctree::
-   :maxdepth: 3
-
-   share_back_ends_feature_support_mapping
-
-Share backends
---------------
-.. toctree::
-   :maxdepth: 3
-
-   container_driver
-   zfs_on_linux_driver
-   netapp_cluster_mode_driver
-   emc_isilon_driver
-   emc_vnx_driver
-   emc_unity_driver
-   generic_driver
-   glusterfs_driver
-   glusterfs_native_driver
-   cephfs_driver
-   gpfs_driver
-   huawei_nas_driver
-   hdfs_native_driver
-   hitachi_hnas_driver
-   hpe_3par_driver
-   tegile_driver
-
 Indices and tables
 ------------------