Merge "Update the documentation link for doc migration"

HACKING.rst

@@ -2,7 +2,7 @@ Nova-DPM Style Commandments
 ===============================
 
 - Step 1: Read the OpenStack Style Commandments
-  http://docs.openstack.org/developer/hacking/
+  https://docs.openstack.org/hacking/latest/
 - Step 2: Nova-DPM commandments as specified below:
 
 Creating Unit Tests

devstack/README.rst

@@ -7,7 +7,7 @@ What is DevStack?
 
 DevStack is a script to quickly create an OpenStack development environment.
 
-Find out more `here <http://docs.openstack.org/developer/devstack/>`_.
+Find out more `here <https://docs.openstack.org/devstack/latest/>`_.
 
 
 What are DevStack plugins?
@@ -19,7 +19,7 @@ part of the normal local.conf and stack.sh execution. The devstack plugin setup
 is for nova-dpm. Without any additional scripting required the nova-dpm plugin would be plugged
 to devstack environment.
 
-More details can be `found here. <http://docs.openstack.org/developer/devstack/plugins.html>`_
+More details can be `found here. <https://docs.openstack.org/devstack/latest/plugins.html>`_
 
 
 How to use the nova-dpm DevStack plugins:

doc/source/devref.rst

@@ -43,7 +43,7 @@ To build the release notes::
    in your local repository of this project.
 
 More information about *reno* can be found at:
-http://docs.openstack.org/developer/reno/index.html
+https://docs.openstack.org/reno/latest/index.html
 
 
 Release Management

doc/source/history.rst

@@ -1,4 +1,4 @@
 .. Documentation for this reno sphinx ext can be found at
-   http://docs.openstack.org/developer/reno/sphinxext.html
+   https://docs.openstack.org/reno/latest/user/sphinxext.html
 
 .. release-notes:: Release Notes

doc/source/specs/ocata/template.rst

@@ -20,7 +20,7 @@ respectively.
 Some notes about the nova-spec and blueprint process:
 
 * Not all blueprints need a spec. For more information see
-  http://docs.openstack.org/developer/nova/devref/kilo.blueprints.html#when-is-a-blueprint-needed
+  https://docs.openstack.org/nova/latest/blueprints.html
 
 * The aim of this document is first to define the problem we need to solve,
   and second agree the overall approach to solve that problem.

doc/source/specs/pike/template.rst

@@ -20,7 +20,7 @@ respectively.
 Some notes about the nova-spec and blueprint process:
 
 * Not all blueprints need a spec. For more information see
-  http://docs.openstack.org/developer/nova/devref/kilo.blueprints.html#when-is-a-blueprint-needed
+  https://docs.openstack.org/nova/latest/blueprints.html
 
 * The aim of this document is first to define the problem we need to solve,
   and second agree the overall approach to solve that problem.

doc/source/specs/queens/template.rst

@@ -20,7 +20,7 @@ respectively.
 Some notes about the nova-spec and blueprint process:
 
 * Not all blueprints need a spec. For more information see
-  http://docs.openstack.org/developer/nova/devref/kilo.blueprints.html#when-is-a-blueprint-needed
+  https://docs.openstack.org/nova/latest/blueprints.html
 
 * The aim of this document is first to define the problem we need to solve,
   and second agree the overall approach to solve that problem.