Update the documentation link for doc migration

This patch is proposed according to the Direction 10 of doc
migration(https://etherpad.openstack.org/p/doc-migration-tracking).

Change-Id: I55f4bbdda9671d766d90349d6d0cfccc5dba1741

CONTRIBUTING.rst

@@ -1,13 +1,13 @@
 If you would like to contribute to the development of OpenStack,
 you must follow the steps documented at:
 
-   http://docs.openstack.org/infra/manual/developers.html#development-workflow
+   https://docs.openstack.org/infra/manual/developers.html#development-workflow
 
 Once those steps have been completed, changes to OpenStack
 should be submitted for review via the Gerrit tool, following
 the workflow documented at:
 
-   http://docs.openstack.org/infra/manual/developers.html#development-workflow
+   https://docs.openstack.org/infra/manual/developers.html#development-workflow
 
 Pull requests submitted through GitHub will be ignored.
 
@@ -18,4 +18,4 @@ Bugs should be filed on Launchpad, not GitHub:
 Further documentation on feature request and bug report processes may be
 found here:
 
-   http://docs.openstack.org/developer/searchlight/feature-requests-bugs.html
+   https://docs.openstack.org/searchlight/latest/contributor/feature-requests-bugs.html

HACKING.rst

@@ -2,7 +2,7 @@ Searchlight Style Commandments
 ==============================
 
 - Step 1: Read the OpenStack Style Commandments
-  http://docs.openstack.org/developer/hacking/
+  https://docs.openstack.org/hacking/latest
 - Step 2: Read on
 
 Searchlight Specific Commandments
@@ -17,4 +17,4 @@ Searchlight Specific Commandments
 - [SL319] Validate that logs are not translated
 - [SL320] For python 3 compatibility, use six.text_type() instead of unicode()
 - [SL327] Prevent use of deprecated contextlib.nested
-- [SL343] Check for common double word typos
+- [SL343] Check for common double word typos

README.rst

@@ -22,4 +22,4 @@ querying combined with near real-time indexing.
 
 Use the following resources to learn more:
 
-* `Official Searchlight documentation <http://docs.openstack.org/developer/searchlight/>`_
+* `Official Searchlight documentation <https://docs.openstack.org/searchlight/latest>`_

devstack/README.rst

@@ -70,7 +70,7 @@ driver in each service's configuration.
 
 Please review the plugin documentation and add configuration appropriately:
 
- * `Searchlight Plugins <http://docs.openstack.org/developer/searchlight/plugins.html>`_
+ * `Searchlight Plugins <https://docs.openstack.org/searchlight/latest/configuration/plugins.html>`_
 
 3. Customize searchlight configuration
 

devstack/local.conf

@@ -241,7 +241,7 @@ enabled = True
 # for Swift after devstack has completed stacking. Please follow the
 # instructions in the docs:
 #
-# http://docs.openstack.org/developer/searchlight/plugins/swift.html
+# https://docs.openstack.org/searchlight/latest/admin/plugins/swift.html
 #
 # Notifications must be configured properly for searchlight to process
 # incremental updates. There is a middleware patch to provide Swift updates.

doc/source/configuration/plugins.rst

@@ -171,7 +171,7 @@ configured to use and then to allow Searchlight to consume messages from
 that topic using a pool, touched on in the `messaging documentation`_.
 Searchlight uses this configuration by default.
 
-.. _`messaging documentation`: http://docs.openstack.org/developer/oslo.messaging/notification_listener.html
+.. _`messaging documentation`: https://docs.openstack.org/oslo.messaging/latest/configration/opts.html
 
 **Topics**
 

doc/source/contributor/feature-requests-bugs.rst

@@ -171,7 +171,7 @@ If any of the following applies to the patch, a release note is required:
 A release note is suggested if a long-standing or important bug is fixed.
 Otherwise, a release note is not required.
 
-Searchlight uses `reno <http://docs.openstack.org/developer/reno/usage.html>`_ to
+Searchlight uses `reno <https://docs.openstack.org/reno/latest/user/usage.html>`_ to
 generate release notes. Please read the docs for details. In summary, use
 the following: