Merge "Change some URLs to point to better targets"

This commit is contained in:
Zuul 2019-05-13 06:38:17 +00:00 committed by Gerrit Code Review
commit 12ebe26823
4 changed files with 4 additions and 4 deletions

View File

@ -167,7 +167,7 @@ depending on the type of error. The following link contains a list of possible
elements along with their associated error codes.
For more information on possible error code, please see:
http://specs.openstack.org/openstack/api-wg/guidelines/http.html#http-response-codes
http://specs.openstack.org/openstack/api-wg/guidelines/http/response-codes.html
Asynchronous faults
===================

View File

@ -111,7 +111,7 @@ very long. So here are some key points:
* The field names contained in a request/response body should
use snake_case style, not CamelCase or Mixed_Case style.
* `HTTP Response Codes <http://specs.openstack.org/openstack/api-wg/guidelines/http.html#http-response-codes>`_
* `HTTP Response Codes <http://specs.openstack.org/openstack/api-wg/guidelines/http/response-codes.html>`_
* Synchronous resource creation: ``201 Created``
* Asynchronous resource creation: ``202 Accepted``

View File

@ -157,7 +157,7 @@ Running unit tests
See `Running Python Unit Tests`_.
.. _`Running Python Unit Tests`: http://docs.openstack.org/infra/manual/python.html#running-python-unit-tests
.. _`Running Python Unit Tests`: https://docs.openstack.org/project-team-guide/project-setup/python.html#running-python-unit-tests
Note that some unit and functional tests use a database. See the file
``tools/test-setup.sh`` on how the databases are set up in the

View File

@ -13,7 +13,7 @@ Setting up a devstack environment
For instructions on how to setup devstack with serial console support enabled
see `this guide
<http://docs.openstack.org/developer/devstack/guides/nova.html#nova-serialproxy>`_.
<https://docs.openstack.org/devstack/latest/guides/nova.html#nova-serialproxy>`_.
---------------
Testing the API