Replace http with https for doc links in nova

Update doc links according to OpenStack document migration,
Use https instead of http for docs links, and update.

Change-Id: Ia4c58ffd799444b939175603bdf511622def75cc

doc/source/contributor/policies.rst

@@ -33,7 +33,7 @@ Public Contractual APIs
 Although nova has many internal APIs, they are not all public contractual
 APIs. Below is a link of our public contractual APIs:
 
-* http://developer.openstack.org/api-ref/compute/
+* https://developer.openstack.org/api-ref/compute/
 
 Anything not in this list is considered private, not to be used outside of
 nova, and should not be considered stable.
@@ -59,7 +59,7 @@ As a patch author, you should try to offset the reviewer resources
 spent on your patch by reviewing other patches. If no one does this, the review
 team (cores and otherwise) become spread too thin.
 
-For review guidelines see: http://docs.openstack.org/infra/manual/developers.html#peer-review
+For review guidelines see: https://docs.openstack.org/infra/manual/developers.html#peer-review
 
 Reverts for Retrospective Vetos
 ===============================
@@ -127,6 +127,6 @@ replacement, the deprecation is open-ended, but serves as a signal that new
 deployments should not rely on the metrics that Nova gathers and should instead
 focus their efforts on alternative solutions for placement.
 
-.. _Ceilometer: http://docs.openstack.org/developer/ceilometer/
-.. _Watcher: http://docs.openstack.org/developer/watcher/
+.. _Ceilometer: https://docs.openstack.org/ceilometer/latest/
+.. _Watcher: https://docs.openstack.org/watcher/latest/
 .. _Newton midcycle: http://lists.openstack.org/pipermail/openstack-dev/2016-August/100600.html

doc/source/contributor/process.rst

@@ -28,8 +28,8 @@ OpenStack Wide Patterns
 Nova follows most of the generally adopted norms for OpenStack projects.
 You can get more details here:
 
-* http://docs.openstack.org/infra/manual/developers.html
-* http://docs.openstack.org/project-team-guide/
+* https://docs.openstack.org/infra/manual/developers.html
+* https://docs.openstack.org/project-team-guide/
 
 If you are new to Nova, please read this first: :ref:`getting_involved`.
 
@@ -53,7 +53,7 @@ and packagers to perform tests (automated, and manual) on the release, to
 spot any major bugs.
 
 The Nova release process is aligned with the `development cycle schedule
-<http://docs.openstack.org/project-team-guide/release-management.html#typical-development-cycle-schedule>`_
+<https://docs.openstack.org/project-team-guide/release-management.html#typical-development-cycle-schedule>`_
 used by many OpenStack projects, including the following steps.
 
 - Feature Proposal Freeze
@@ -190,7 +190,7 @@ implement. How do I make that happen?
 
 You can get most of your questions answered here:
 
--  http://docs.openstack.org/infra/manual/developers.html
+-  https://docs.openstack.org/infra/manual/developers.html
 
 But let's put a Nova specific twist on things...
 
@@ -205,7 +205,7 @@ Where do you track bugs?
 
 We track bugs here:
 
--  http://bugs.launchpad.net/nova
+-  https://bugs.launchpad.net/nova
 
 If you fix an issue, please raise a bug so others who spot that issue
 can find the fix you kindly created for them.
@@ -219,7 +219,7 @@ When do I need a blueprint vs a spec?
 
 For more details see:
 
--  http://docs.openstack.org/developer/nova/blueprints.html
+-  https://docs.openstack.org/nova/latest/contributor/blueprints.html 
 
 To understand this question, we need to understand why blueprints and
 specs are useful.
@@ -248,7 +248,7 @@ So you need your blueprint approved? Here is how:
       review in that meeting.
 
 -  if you need a spec, then please submit a nova-spec for review, see:
-   http://docs.openstack.org/infra/manual/developers.html
+   https://docs.openstack.org/infra/manual/developers.html
 
 Got any more questions? Contact johnthetubaguy or one of the other
 nova-specs-core who are awake at the same time as you. IRC is best as
@@ -421,7 +421,7 @@ Interoperable API, supporting a vibrant ecosystem
 
 An interoperable API that gives users on-demand access to compute
 resources is at the heart of Nova's mission:
-http://docs.openstack.org/developer/nova/project_scope.html#mission
+https://docs.openstack.org/nova/latest/contributor/project-scope.html#mission
 
 Nova has a vibrant ecosystem of tools built on top of the current Nova
 API. All features should be designed to work with all technology
@@ -906,7 +906,7 @@ Feature Classification
 
 This is a look at moving forward this effort:
 
--  http://docs.openstack.org/developer/nova/support-matrix.html
+-  https://docs.openstack.org/nova/latest/user/support-matrix.html
 
 The things we need to cover: