openstack/nova
Code Issues Proposed changes

Merge "Fix typos in nova doc"

Browse Source
This commit is contained in:
Zuul
2020-01-10 23:27:11 +00:00
committed by Gerrit Code Review
parent b0cae0750c ea172ef85f
commit 67d9b5114e
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
api-guide/source/server_concepts.rst
View File

@@ -85,7 +85,7 @@ server status is one of the following values:
- ``VERIFY_RESIZE``: System is awaiting confirmation that the server is - ``VERIFY_RESIZE``: System is awaiting confirmation that the server is
operational after a move or resize. operational after a move or resize.
Server status is caculated from vm_state and task_state, which Server status is calculated from vm_state and task_state, which
are exposed to administrators: are exposed to administrators:
- vm_state describes a VM's current stable (not transition) state. That is, if - vm_state describes a VM's current stable (not transition) state. That is, if

2
doc/source/admin/availability-zones.rst
View File

@@ -252,7 +252,7 @@ associating it with an AZ in the process, and add host to it using the
.. note:: .. note::
While it is possible to add a host to multiple host aggregates, it is not While it is possible to add a host to multiple host aggregates, it is not
possile to add them to multiple availability zones. Attempting to add a possible to add them to multiple availability zones. Attempting to add a
host to multiple host aggregates associated with differing availability host to multiple host aggregates associated with differing availability
zones will result in a failure. zones will result in a failure.

8
nova/api/openstack/compute/rest_api_version_history.rst
View File

@@ -10,7 +10,7 @@ user documentation.
--- ---
This is the initial version of the v2.1 API which supports This is the initial version of the v2.1 API which supports
microversions. The V2.1 API is from the REST API users's point of microversions. The V2.1 API is from the REST API users' point of
view exactly the same as v2.0 except with strong input validation. view exactly the same as v2.0 except with strong input validation.
A user can specify a header in the API request:: A user can specify a header in the API request::
@@ -433,19 +433,19 @@ API endpoints as below::
The ``os-security-group-default-rules`` API was completely removed in the The ``os-security-group-default-rules`` API was completely removed in the
21.0.0 (Ussuri) release. On deployments newer than this, the APIs will 21.0.0 (Ussuri) release. On deployments newer than this, the APIs will
return HTTP 410 (Gone) regadless of the requested microversion. return HTTP 410 (Gone) regardless of the requested microversion.
.. versionchanged:: 21.0.0 .. versionchanged:: 21.0.0
The ``os-networks`` API was partially removed in the 21.0.0 (Ussuri) The ``os-networks`` API was partially removed in the 21.0.0 (Ussuri)
release. On deployments newer than this, some endpoints of the API will release. On deployments newer than this, some endpoints of the API will
return HTTP 410 (Gone) regadless of the requested microversion. return HTTP 410 (Gone) regardless of the requested microversion.
.. versionchanged:: 21.0.0 .. versionchanged:: 21.0.0
The ``os-tenant-networks`` API was partially removed in the 21.0.0 (Ussuri) The ``os-tenant-networks`` API was partially removed in the 21.0.0 (Ussuri)
release. On deployments newer than this, some endpoints of the API will release. On deployments newer than this, some endpoints of the API will
return HTTP 410 (Gone) regadless of the requested microversion. return HTTP 410 (Gone) regardless of the requested microversion.
2.37 2.37
---- ----