Update api-ref location

The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.

Note that the location API location /shared-file-system and not
/shared-file-systems.

Note that redirects will be set up as well but let's point now to the
new location.

For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html

Change-Id: I86f50af83be699fa7e0fb064abb20324e2d87b86

api-ref/source/share-group-snapshots.inc

@@ -20,7 +20,7 @@ roles.
 .. note::
 
     Share Group Snapshot APIs are part of the `experimental APIs
-    <http://developer.openstack.org/api-ref/shared-file-systems/#experimental-apis>`_.
+    <https://docs.openstack.org/api-ref/shared-file-system/#experimental-apis>`_.
 
 List share group snapshots
 ==========================

api-ref/source/share-group-types.inc

@@ -17,7 +17,7 @@ different projects. You can add access, remove access, and get
 information about access for a private share group type.
 
 Administrators can specifies which `share type(s)
-<http://developer.openstack.org/api-ref/shared-file-systems/#experimental-apis>`_
+<https://docs.openstack.org/api-ref/shared-file-system/#experimental-apis>`_
 a given group type may contain. If Administrators does not specify it, then
 manila will use ``default`` share type. The scheduler then creates the group on
 one of the back ends that match the specified share type(s) and share group type.
@@ -32,7 +32,7 @@ share group type for the following purposes:
 .. note::
 
     Share Group Types APIs are part of the `experimental APIs
-    <http://developer.openstack.org/api-ref/shared-file-systems/#experimental-apis>`_.
+    <https://docs.openstack.org/api-ref/shared-file-system/#experimental-apis>`_.
 
 List share group types
 ======================

api-ref/source/share-groups.inc

@@ -19,7 +19,7 @@ share groups, and show information for delete a share group.
 .. note::
 
     Share Group APIs are part of the `experimental APIs
-    <http://developer.openstack.org/api-ref/shared-file-systems/#experimental-apis>`_.
+    <https://docs.openstack.org/api-ref/shared-file-system/#experimental-apis>`_.
     The ``availability_zone_id`` and ``consistent_snapshot_support`` fields were added
     to ``share_group`` object introduced in version 2.34.
 

api-ref/source/share-migration.inc

@@ -16,7 +16,7 @@ Possible use cases for data migration include:
 .. note::
 
     Share Migration APIs are part of the `experimental APIs
-    <http://developer.openstack.org/api-ref/shared-file-systems/
+    <https://docs.openstack.org/api-ref/shared-file-system/
     #experimental-apis>`_ .
 
 

doc/source/admin/shared-file-systems-services-manage.rst

@@ -6,7 +6,7 @@ Manage shares services
 
 The Shared File Systems service provides API that allows to manage running
 share services (`Share services API
-<https://developer.openstack.org/api-ref/shared-file-systems/>`_).
+<https://docs.openstack.org/api-ref/shared-file-system/>`_).
 Using the :command:`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`` equal to ``manila-share``. Also, you can

doc/source/contributor/documenting_your_work.rst

@@ -81,7 +81,7 @@ OpenStack API Reference
 - Since the Newton release, manila's API reference is maintained
   in-tree in custom YAML/JSON format files.
 - **Link**: `REST API reference of the Shared File Systems Project v2.0
-  <https://developer.openstack.org/api-ref/shared-file-system/>`_
+  <https://docs.openstack.org/api-ref/shared-file-system/>`_
 
 Manila Developer Reference
 --------------------------

doc/source/contributor/index.rst

@@ -65,7 +65,7 @@ API Reference
 .. toctree::
    :maxdepth: 3
 
-   Manila API v2 Reference <https://developer.openstack.org/api-ref/shared-file-system/>
+   Manila API v2 Reference <https://docs.openstack.org/api-ref/shared-file-system/>
    api_microversion_dev
    api_microversion_history
    experimental_apis

doc/source/index.rst

@@ -38,7 +38,7 @@ As an end user of Manila, you'll use Manila to create a remote file system with
 either tools or the API directly:
 `python-manilaclient <https://docs.openstack.org/python-manilaclient/latest/>`_,
 or by directly using the
-`REST API <https://developer.openstack.org/api-ref/shared-file-system/>`_.
+`REST API <https://docs.openstack.org/api-ref/shared-file-system/>`_.
 
 Tools for using Manila
 ~~~~~~~~~~~~~~~~~~~~~~
@@ -58,7 +58,7 @@ more complicated logic or automation with Manila. This can be consumed directly
 or via various SDKs. The following resources can help you get started consuming
 the API directly:
 
-* `Manila API <https://developer.openstack.org/api-ref/shared-file-system/>`_
+* `Manila API <https://docs.openstack.org/api-ref/shared-file-system/>`_
 * :doc:`Manila microversion history </contributor/api_microversion_history>`
 
 For operators

doc/source/user/API.rst

@@ -4,5 +4,5 @@ Manila API Documentation
 
 A full specification of the API for interacting with the shared file
 systems service may be found in the `API reference
-<https://developer.openstack.org/api-ref/shared-file-systems>`_.
+<https://docs.openstack.org/api-ref/shared-file-system>`_.
 

tox.ini

@@ -125,7 +125,7 @@ commands = bash ./tools/coding-checks.sh --pylint {posargs}
 [testenv:api-ref]
 basepython = python3
 # This environment is called from CI scripts to test and publish
-# the API Ref to developer.openstack.org.
+# the API Ref to docs.openstack.org.
 whitelist_externals = rm
 commands =
   rm -rf api-ref/build