Use https instead of http for developer.o.o

Change-Id: Iec2c2cebb5e5b7e0cdb760d8d3aafffc6f03602a
This commit is contained in:
KATO Tomoyuki 2017-01-28 11:50:17 +09:00
parent ba0bf068d4
commit 89b722d36a
15 changed files with 21 additions and 21 deletions

View File

@ -162,6 +162,6 @@ old password.
.. _Security Hardening PCI-DSS: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/newton/pci-dss.html .. _Security Hardening PCI-DSS: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/newton/pci-dss.html
.. _v2.0: http://developer.openstack.org/api-ref/identity/v2-admin/index.html?expanded=update-user-admin-endpoint-detail#update-user-admin-endpoint .. _v2.0: https://developer.openstack.org/api-ref/identity/v2-admin/index.html?expanded=update-user-admin-endpoint-detail#update-user-admin-endpoint
.. _v3: http://developer.openstack.org/api-ref/identity/v3/index.html#update-user .. _v3: https://developer.openstack.org/api-ref/identity/v3/index.html#update-user

View File

@ -11,7 +11,7 @@ to the Networking service must provide an authentication token in
authenticating with the Identity service endpoint. For more information authenticating with the Identity service endpoint. For more information
about authentication with the Identity service, see `OpenStack Identity about authentication with the Identity service, see `OpenStack Identity
service API v2.0 service API v2.0
Reference <http://developer.openstack.org/api-ref/identity/v2/>`__. Reference <https://developer.openstack.org/api-ref/identity/v2/>`__.
When the Identity service is enabled, it is not mandatory to specify the When the Identity service is enabled, it is not mandatory to specify the
project ID for resources in create requests because the project ID is project ID for resources in create requests because the project ID is
derived from the authentication token. derived from the authentication token.

View File

@ -12,7 +12,7 @@ firewalls, and IPsec VPN.
For a detailed description of the Networking API abstractions and their For a detailed description of the Networking API abstractions and their
attributes, see the `OpenStack Networking API v2.0 attributes, see the `OpenStack Networking API v2.0
Reference <http://developer.openstack.org/api-ref/networking/v2/>`__. Reference <https://developer.openstack.org/api-ref/networking/v2/>`__.
.. note:: .. note::

View File

@ -6,7 +6,7 @@ Manage shares services
The Shared File Systems service provides API that allows to manage running The Shared File Systems service provides API that allows to manage running
share services (`Share services API share services (`Share services API
<http://developer.openstack.org/api-ref/shared-file-systems/>`_). <https://developer.openstack.org/api-ref/shared-file-systems/>`_).
Using the :command:`manila service-list` command, it is possible to get a list Using the :command:`manila service-list` command, it is possible to get a list
of all kinds of running services. To select only share services, you can pick of all kinds of running services. To select only share services, you can pick
items that have field ``binary`` equal to ``manila-share``. Also, you can items that have field ``binary`` equal to ``manila-share``. Also, you can

View File

@ -28,7 +28,7 @@ retrieve data, as described in :ref:`telemetry-users-roles-projects`.
Further information about the available API endpoints can be found in Further information about the available API endpoints can be found in
the `Telemetry API Reference the `Telemetry API Reference
<http://developer.openstack.org/api-ref-telemetry-v2.html>`__. <https://developer.openstack.org/api-ref-telemetry-v2.html>`__.
Query Query
----- -----

View File

@ -250,7 +250,7 @@ Application Programming Interface (API)
All public access, whether direct, through a command-line client, or All public access, whether direct, through a command-line client, or
through the web-based dashboard, uses the API service. Find the API through the web-based dashboard, uses the API service. Find the API
reference at `Development resources for OpenStack clouds reference at `Development resources for OpenStack clouds
<http://developer.openstack.org/>`_. <https://developer.openstack.org/>`_.
You must choose whether you want to support the Amazon EC2 compatibility You must choose whether you want to support the Amazon EC2 compatibility
APIs, or just the OpenStack APIs. One issue you might encounter when APIs, or just the OpenStack APIs. One issue you might encounter when
@ -276,7 +276,7 @@ Extensions
~~~~~~~~~~ ~~~~~~~~~~
The `API The `API
Specifications <http://developer.openstack.org/api-guide/quick-start/index.html>`_ define Specifications <https://developer.openstack.org/api-guide/quick-start/index.html>`_ define
the core actions, capabilities, and mediatypes of the OpenStack API. A the core actions, capabilities, and mediatypes of the OpenStack API. A
client can always depend on the availability of this core API, and client can always depend on the availability of this core API, and
implementers are always required to support it in its entirety. implementers are always required to support it in its entirety.

View File

@ -77,7 +77,7 @@ command-line clients:
The following documentation provides reference and guidance information The following documentation provides reference and guidance information
for the OpenStack APIs: for the OpenStack APIs:
* `API Guide <http://developer.openstack.org/api-guide/quick-start/>`__ * `API Guide <https://developer.openstack.org/api-guide/quick-start/>`__
The following guide provides how to contribute to OpenStack documentation: The following guide provides how to contribute to OpenStack documentation:

View File

@ -27,7 +27,7 @@ Users can access OpenStack via the web-based user interface implemented
by :doc:`Dashboard <get-started-dashboard>`, via `command-line by :doc:`Dashboard <get-started-dashboard>`, via `command-line
clients <https://docs.openstack.org/cli-reference/>`__ and by clients <https://docs.openstack.org/cli-reference/>`__ and by
issuing API requests through tools like browser plug-ins or :command:`curl`. issuing API requests through tools like browser plug-ins or :command:`curl`.
For applications, `several SDKs <http://developer.openstack.org/#sdk>`__ For applications, `several SDKs <https://developer.openstack.org/#sdk>`__
are available. Ultimately, all these access methods issue REST API calls are available. Ultimately, all these access methods issue REST API calls
to the various OpenStack services. to the various OpenStack services.

View File

@ -148,9 +148,9 @@ documentation, patch the ``reference/projects.yaml`` file in the
.. _`developer.openstack.org`: http://developer.openstack.org .. _`developer.openstack.org`: https://developer.openstack.org
.. _`wadl2rst`: http://github.com/annegentle/wadl2rst .. _`wadl2rst`: http://github.com/annegentle/wadl2rst
.. _`Compute API Guide`: http://developer.openstack.org/api-guide/compute .. _`Compute API Guide`: https://developer.openstack.org/api-guide/compute
.. _`example patch`: https://review.openstack.org/#/c/233446/ .. _`example patch`: https://review.openstack.org/#/c/233446/
.. _`API documentation guidelines`: http://specs.openstack.org/openstack/api-wg/guidelines/api-docs.html .. _`API documentation guidelines`: http://specs.openstack.org/openstack/api-wg/guidelines/api-docs.html
.. _`nova example`: https://github.com/openstack/nova/blob/master/api-ref/source/conf.py .. _`nova example`: https://github.com/openstack/nova/blob/master/api-ref/source/conf.py

View File

@ -190,7 +190,7 @@ Guides for end users
Shows OpenStack end users how to create and manage resources in an Shows OpenStack end users how to create and manage resources in an
OpenStack cloud with the OpenStack dashboard and OpenStack client commands. OpenStack cloud with the OpenStack dashboard and OpenStack client commands.
* `OpenStack API Guide * `OpenStack API Guide
<http://developer.openstack.org/api-guide/quick-start/>`_: <https://developer.openstack.org/api-guide/quick-start/>`_:
A brief overview of how to send REST API requests to endpoints for A brief overview of how to send REST API requests to endpoints for
OpenStack services. OpenStack services.
* `OpenStack Command-Line Interface Reference * `OpenStack Command-Line Interface Reference
@ -210,7 +210,7 @@ Guides for end users
* - OpenStack API Guide * - OpenStack API Guide
- http://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start - http://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start
- http://developer.openstack.org/api-guide/quick-start/ - https://developer.openstack.org/api-guide/quick-start/
* - OpenStack Command-Line Interface Reference * - OpenStack Command-Line Interface Reference
- http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/cli-reference - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/cli-reference
@ -219,7 +219,7 @@ Guides for end users
API documentation API documentation
----------------- -----------------
* `Complete API Reference <http://developer.openstack.org/api-guide/quick-start/index.html>`_: * `Complete API Reference <https://developer.openstack.org/api-guide/quick-start/index.html>`_:
Complete reference listing of OpenStack REST APIs Complete reference listing of OpenStack REST APIs
with example requests and responses. with example requests and responses.
* `API specifications <http://specs.openstack.org/>`_: * `API specifications <http://specs.openstack.org/>`_:

View File

@ -67,7 +67,7 @@ Health monitor
LBaaS v2 has multiple implementations via different service plug-ins. The two LBaaS v2 has multiple implementations via different service plug-ins. The two
most common implementations use either an agent or the Octavia services. Both most common implementations use either an agent or the Octavia services. Both
implementations use the `LBaaS v2 API <http://developer.openstack.org/api-ref/networking/v2/#lbaas-2-0-stable>`_. implementations use the `LBaaS v2 API <https://developer.openstack.org/api-ref/networking/v2/#lbaas-2-0-stable>`_.
Configurations Configurations
~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~

View File

@ -84,7 +84,7 @@ provider networks. We recommend using the following procedure:
* Segmentation ID * Segmentation ID
For example, ``provider1``, ``VLAN``, and ``2016``. See the For example, ``provider1``, ``VLAN``, and ``2016``. See the
`API reference <http://developer.openstack.org/api-ref/networking/v2/#id57>`__ `API reference <https://developer.openstack.org/api-ref/networking/v2/#id57>`__
for more information. for more information.
Within a network, use a unique physical network name for each segment which Within a network, use a unique physical network name for each segment which

View File

@ -247,7 +247,7 @@ Application Programming Interface (API)
All public access, whether direct, through a command-line client, or All public access, whether direct, through a command-line client, or
through the web-based dashboard, uses the API service. Find the API through the web-based dashboard, uses the API service. Find the API
reference at `Development resources for OpenStack clouds reference at `Development resources for OpenStack clouds
<http://developer.openstack.org/>`_. <https://developer.openstack.org/>`_.
You must choose whether you want to support the Amazon EC2 compatibility You must choose whether you want to support the Amazon EC2 compatibility
APIs, or just the OpenStack APIs. One issue you might encounter when APIs, or just the OpenStack APIs. One issue you might encounter when
@ -273,7 +273,7 @@ Extensions
~~~~~~~~~~ ~~~~~~~~~~
The `API The `API
Specifications <http://developer.openstack.org/api-guide/quick-start/index.html>`_ define Specifications <https://developer.openstack.org/api-guide/quick-start/index.html>`_ define
the core actions, capabilities, and mediatypes of the OpenStack API. A the core actions, capabilities, and mediatypes of the OpenStack API. A
client can always depend on the availability of this core API, and client can always depend on the availability of this core API, and
implementers are always required to support it in its entirety. implementers are always required to support it in its entirety.

View File

@ -250,7 +250,7 @@ token.
http://203.0.113.10:8774/v2.0/98333aba48e756fa8f629c83a818ad57/servers | jq . http://203.0.113.10:8774/v2.0/98333aba48e756fa8f629c83a818ad57/servers | jq .
To discover how API requests should be structured, read the `OpenStack To discover how API requests should be structured, read the `OpenStack
API Reference <http://developer.openstack.org/api-guide/quick-start/index.html>`_. To chew API Reference <https://developer.openstack.org/api-guide/quick-start/index.html>`_. To chew
through the responses using jq, see the `jq through the responses using jq, see the `jq
Manual <http://stedolan.github.io/jq/manual/>`_. Manual <http://stedolan.github.io/jq/manual/>`_.

View File

@ -177,7 +177,7 @@ Installation Tutorials and Guides
This guide targets OpenStack administrators seeking to deploy and This guide targets OpenStack administrators seeking to deploy and
manage OpenStack Networking (neutron). manage OpenStack Networking (neutron).
`OpenStack API Guide <http://developer.openstack.org/api-guide/quick-start/>`_ `OpenStack API Guide <https://developer.openstack.org/api-guide/quick-start/>`_
A brief overview of how to send REST API requests to endpoints for A brief overview of how to send REST API requests to endpoints for
OpenStack services OpenStack services