From 7643832b90c88834833cb1a1a9694122a063949c Mon Sep 17 00:00:00 2001 From: zhouxinyong Date: Wed, 14 Nov 2018 11:00:06 +0800 Subject: [PATCH] Advancing the protocal of the website to HTTPS in rolling-upgrade.rst. Change-Id: I97a01744383c1d7a8c07b9536244cd487b81190f --- specs/juno/client-refactor-models.rst | 6 +++--- specs/juno/consume-keystone-events.rst | 6 +++--- specs/juno/template.rst | 2 +- specs/kilo/add-worker-retry-update-support.rst | 2 +- specs/liberty/audit-cadf-events.rst | 4 ++-- specs/liberty/fix-version-api.rst | 12 ++++++------ specs/mitaka/add-barbican-manage-cmd.rst | 6 +++--- specs/newton/date-filters.rst | 4 ++-- specs/stein/template.rst | 2 +- specs/template.rst | 2 +- 10 files changed, 23 insertions(+), 23 deletions(-) diff --git a/specs/juno/client-refactor-models.rst b/specs/juno/client-refactor-models.rst index 0b3ab25..b1d799b 100644 --- a/specs/juno/client-refactor-models.rst +++ b/specs/juno/client-refactor-models.rst @@ -21,7 +21,7 @@ The Entity Models in ``barbicanclient`` should be refactored to provide a more Pythonic api. This refactor will make the existing Entities consistent with the recently approved Containers blueprint. [1]_ -.. [1] http://specs.openstack.org/openstack/barbican-specs/specs/juno/client-add-containers.html +.. [1] https://specs.openstack.org/openstack/barbican-specs/specs/juno/client-add-containers.html Proposed Change =============== @@ -110,7 +110,7 @@ We could continue to use the objects as they currently exist. Also note that the Orders functionality will need to be revisited once the Typed Orders implementation lands. [2]_ -.. [2] http://specs.openstack.org/openstack/barbican-specs/specs/juno/api-orders-add-more-types.html +.. [2] https://specs.openstack.org/openstack/barbican-specs/specs/juno/api-orders-add-more-types.html Data model impact ----------------- @@ -188,4 +188,4 @@ References ========== Containers in the Client etherpad: https://etherpad.openstack.org/p/python-barbicanclient-containers -Containers Blueprint: http://specs.openstack.org/openstack/barbican-specs/specs/juno/client-add-containers.html +Containers Blueprint: https://specs.openstack.org/openstack/barbican-specs/specs/juno/client-add-containers.html diff --git a/specs/juno/consume-keystone-events.rst b/specs/juno/consume-keystone-events.rst index 1528868..26a18cb 100644 --- a/specs/juno/consume-keystone-events.rst +++ b/specs/juno/consume-keystone-events.rst @@ -256,8 +256,8 @@ https://github.com/cloudkeep/barbican/wiki/Barbican-Options:-authentication-with References ========== -* http://docs.openstack.org/developer/oslo.messaging/notification_listener.html +* https://docs.openstack.org/developer/oslo.messaging/notification_listener.html -* http://docs.openstack.org/developer/oslo.messaging/index.html +* https://docs.openstack.org/developer/oslo.messaging/index.html -* http://docs.openstack.org/developer/oslo.messaging/notification_listener.html#oslo.messaging.MessageHandlingServer +* https://docs.openstack.org/developer/oslo.messaging/notification_listener.html#oslo.messaging.MessageHandlingServer diff --git a/specs/juno/template.rst b/specs/juno/template.rst index f8b8422..3f31e4f 100644 --- a/specs/juno/template.rst +++ b/specs/juno/template.rst @@ -126,7 +126,7 @@ Each API method which is either added or changed should have the following think about when defining their policy. Example JSON schema definitions can be found in the Nova tree -http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 +https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 Note that the schema should be defined as restrictively as possible. Parameters which are required should be marked as such and diff --git a/specs/kilo/add-worker-retry-update-support.rst b/specs/kilo/add-worker-retry-update-support.rst index ca6f9a3..c66254b 100644 --- a/specs/kilo/add-worker-retry-update-support.rst +++ b/specs/kilo/add-worker-retry-update-support.rst @@ -105,7 +105,7 @@ attempt. To implement this scheduling process, this blueprint proposes using the Oslo periodic task feature, described here: -http://docs.openstack.org/developer/oslo-incubator/api/openstack.common.periodic_task.html +https://docs.openstack.org/developer/oslo-incubator/api/openstack.common.periodic_task.html A working example implementation with an older code base is shown here: diff --git a/specs/liberty/audit-cadf-events.rst b/specs/liberty/audit-cadf-events.rst index 9437916..49a0e66 100644 --- a/specs/liberty/audit-cadf-events.rst +++ b/specs/liberty/audit-cadf-events.rst @@ -245,10 +245,10 @@ References http://www.dmtf.org/sites/default/files/standards/documents/DSP2038_1.0.0.pdf * Audit Middleware - http://docs.openstack.org/developer/keystonemiddleware/audit.html + https://docs.openstack.org/developer/keystonemiddleware/audit.html * PyCADF developer docs - http://docs.openstack.org/developer/pycadf/ + https://docs.openstack.org/developer/pycadf/ * CADF event model and taxonomies https://wiki.openstack.org/w/images/e/e1/Introduction_to_Cloud_Auditing_using_CADF_Event_Model_and_Taxonomy_2013-10-22.pdf diff --git a/specs/liberty/fix-version-api.rst b/specs/liberty/fix-version-api.rst index f786574..f654875 100644 --- a/specs/liberty/fix-version-api.rst +++ b/specs/liberty/fix-version-api.rst @@ -32,7 +32,7 @@ Keystone and Barbican The following is an example of implementing a json-home type of response from Keystone (documented here: -http://docs.openstack.org/api/openstack-identity-service/2.0/content/\ +https://docs.openstack.org/api/openstack-identity-service/2.0/content/\ Versions-d1e472.html):: { @@ -43,7 +43,7 @@ Versions-d1e472.html):: "links": [ { "rel": "self", - "href": "http://identity.api.openstack.org/v1.0" + "href": "https://identity.api.openstack.org/v1.0" } ], "media-types": { @@ -65,7 +65,7 @@ Versions-d1e472.html):: "links": [ { "rel": "self", - "href": "http://identity.api.openstack.org/v1.1" + "href": "https://identity.api.openstack.org/v1.1" } ], "media-types": { @@ -87,7 +87,7 @@ Versions-d1e472.html):: "links": [ { "rel": "self", - "href": "http://identity.api.openstack.org/v2.0" + "href": "https://identity.api.openstack.org/v2.0" } ], "media-types": { @@ -131,12 +131,12 @@ provided in response such as per this Keystone example:: "rel": "self" }, { - "href": "http://docs.openstack.org/api/openstack-identity-service/2.0/content/", + "href": "https://docs.openstack.org/api/openstack-identity-service/2.0/content/", "type": "text/html", "rel": "describedby" }, { - "href": "http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf", + "href": "https://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf", "type": "application/pdf", "rel": "describedby" } diff --git a/specs/mitaka/add-barbican-manage-cmd.rst b/specs/mitaka/add-barbican-manage-cmd.rst index 7c0734c..8ece58a 100644 --- a/specs/mitaka/add-barbican-manage-cmd.rst +++ b/specs/mitaka/add-barbican-manage-cmd.rst @@ -198,12 +198,12 @@ Documentation Impact A new barbican-manage command user guide will be added, which should include new user guide for database migration subcommands and user guide of pkcs11-related subcommands modified from existing -http://docs.openstack.org/developer/barbican/api/userguide/pkcs11keygeneration.html +https://docs.openstack.org/developer/barbican/api/userguide/pkcs11keygeneration.html References ========== -.. [#] http://docs.openstack.org/developer/keystone/man/keystone-manage.html -.. [#] http://docs.openstack.org/developer/nova/man/nova-manage.html +.. [#] https://docs.openstack.org/developer/keystone/man/keystone-manage.html +.. [#] https://docs.openstack.org/developer/nova/man/nova-manage.html .. [#] https://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html diff --git a/specs/newton/date-filters.rst b/specs/newton/date-filters.rst index bec6681..8adf0a8 100644 --- a/specs/newton/date-filters.rst +++ b/specs/newton/date-filters.rst @@ -52,7 +52,7 @@ not include the zone designation will result in an error response with status code 400. Values that specify a time offset from UTC will also result in a 400 error response even if the offset is zero to specify UTC. -.. _Pagination, Filtering, and Sorting: http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst +.. _Pagination, Filtering, and Sorting: https://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst Alternatives ------------ @@ -178,7 +178,7 @@ References API Working Group's Guideline for Pagination, Filtering and Sorting: -http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst +https://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst ISO 8601 in Wikipedia: diff --git a/specs/stein/template.rst b/specs/stein/template.rst index 663627d..3a3e663 100644 --- a/specs/stein/template.rst +++ b/specs/stein/template.rst @@ -139,7 +139,7 @@ Each API method which is either added or changed should have the following think about when defining their policy. Example JSON schema definitions can be found in the Nova tree -http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 +https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 Note that the schema should be defined as restrictively as possible. Parameters which are required should be marked as such and diff --git a/specs/template.rst b/specs/template.rst index 663627d..3a3e663 100644 --- a/specs/template.rst +++ b/specs/template.rst @@ -139,7 +139,7 @@ Each API method which is either added or changed should have the following think about when defining their policy. Example JSON schema definitions can be found in the Nova tree -http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 +https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 Note that the schema should be defined as restrictively as possible. Parameters which are required should be marked as such and