Update and replace http with https for doc links in zaqar-specs

1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links

Change-Id: I9f6943d01b4e408d8873d1dfb0afd2a3032f7fc7
This commit is contained in:
shangxiaobj 2017-09-07 23:30:58 -07:00
parent c7da52e084
commit 96358f7814
4 changed files with 10 additions and 10 deletions

View File

@ -5,13 +5,13 @@ Contributing to: zaqar-specs
If you would like to contribute to the development of OpenStack, If you would like to contribute to the development of OpenStack,
you must follow the steps in this page: you must follow the steps in this page:
http://docs.openstack.org/infra/manual/developers.html https://docs.openstack.org/infra/manual/developers.html
Once those steps have been completed, changes to OpenStack Once those steps have been completed, changes to OpenStack
should be submitted for review via the Gerrit tool, following should be submitted for review via the Gerrit tool, following
the workflow documented at: 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. Pull requests submitted through GitHub will be ignored.

View File

@ -2,8 +2,8 @@
Team and repository tags Team and repository tags
======================== ========================
.. image:: http://governance.openstack.org/badges/zaqar-specs.svg .. image:: https://governance.openstack.org/tc/badges/zaqar-specs.svg
:target: http://governance.openstack.org/reference/tags/index.html :target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on .. Change things from this point on

View File

@ -16,7 +16,7 @@ Authorization Policy Support
OpenStack components are supposed to check user privileges to perform any OpenStack components are supposed to check user privileges to perform any
action. Generally these checks are role-based. See action. Generally these checks are role-based. See
http://docs.openstack.org/developer/keystone/architecture.html#approach-to-authorization-policy. https://docs.openstack.org/keystone/latest/#approach-to-authorization-policy.
Zaqar needs to support policies as well. Zaqar needs to support policies as well.
Problem description Problem description
@ -125,6 +125,6 @@ Dependencies
============ ============
* oslo.policy * oslo.policy
* http://docs.openstack.org/developer/keystone/architecture.html#approach-to-authorization-policy * https://docs.openstack.org/keystone/latest/#approach-to-authorization-policy
* http://docs.openstack.org/developer/keystone/api/keystone.openstack.common.policy.html * https://docs.openstack.org/keystone/latest/configuration/config-options.html#policy
* http://docs.openstack.org/developer/keystone/configuration.html#keystone-api-protection-with-role-based-access-control-rbac * https://docs.openstack.org/keystone/latest/#keystone-api-protection-with-role-based-access-control-rbac

View File

@ -128,8 +128,8 @@ passed through unmodified.
While all the data is available to do a raw HTTP request, it is preferable if While all the data is available to do a raw HTTP request, it is preferable if
these calls are made through the python-mistralclient library. these calls are made through the python-mistralclient library.
.. _Execution: http://docs.openstack.org/developer/mistral/developer/webapi/v2.html#executions .. _Execution: https://docs.openstack.org/mistral/latest/#executions
.. _the one used by Aodh: http://docs.openstack.org/developer/aodh/architecture.html#trust-http .. _the one used by Aodh: https://docs.openstack.org/aodh/latest/#trust-http
Alternatives Alternatives
------------ ------------