Fix OpenStack capitalization
Reviewing the Placement API, I noticed wrong OpenStack capitalization. Fix the docs and some strings as well. Change-Id: I14a2443687a0d517ece80e794e7ef0d4e165af6f
This commit is contained in:
@@ -31,7 +31,7 @@ enable_guestfs_debug_opts = [
|
|||||||
help="""
|
help="""
|
||||||
Enable/disables guestfs logging.
|
Enable/disables guestfs logging.
|
||||||
|
|
||||||
This configures guestfs to debug messages and push them to Openstack
|
This configures guestfs to debug messages and push them to OpenStack
|
||||||
logging system. When set to True, it traces libguestfs API calls and
|
logging system. When set to True, it traces libguestfs API calls and
|
||||||
enable verbose debug messages. In order to use the above feature,
|
enable verbose debug messages. In order to use the above feature,
|
||||||
"libguestfs" package must be installed.
|
"libguestfs" package must be installed.
|
||||||
|
@@ -22,7 +22,7 @@ notifications_group = cfg.OptGroup(
|
|||||||
help="""
|
help="""
|
||||||
Most of the actions in Nova which manipulate the system state generate
|
Most of the actions in Nova which manipulate the system state generate
|
||||||
notifications which are posted to the messaging component (e.g. RabbitMQ) and
|
notifications which are posted to the messaging component (e.g. RabbitMQ) and
|
||||||
can be consumed by any service outside the Openstack. More technical details
|
can be consumed by any service outside the OpenStack. More technical details
|
||||||
at https://docs.openstack.org/nova/latest/reference/notifications.html
|
at https://docs.openstack.org/nova/latest/reference/notifications.html
|
||||||
""")
|
""")
|
||||||
|
|
||||||
|
@@ -4,8 +4,8 @@
|
|||||||
Placement API
|
Placement API
|
||||||
===============
|
===============
|
||||||
|
|
||||||
This is a reference for the Openstack Placement API. To learn more about
|
This is a reference for the OpenStack Placement API. To learn more about
|
||||||
Openstack Placement API concepts, please refer to the
|
OpenStack Placement API concepts, please refer to the
|
||||||
`Placement Introduction <https://docs.openstack.org/nova/latest/user/placement.html>`_.
|
`Placement Introduction <https://docs.openstack.org/nova/latest/user/placement.html>`_.
|
||||||
|
|
||||||
The Placement API uses JSON for data exchange. As such, the ``Content-Type``
|
The Placement API uses JSON for data exchange. As such, the ``Content-Type``
|
||||||
|
@@ -7,7 +7,7 @@ supports microversioning. Microversions allow use of certain features on a
|
|||||||
per-request basis via the ``OpenStack-API-Version`` header. For example, to
|
per-request basis via the ``OpenStack-API-Version`` header. For example, to
|
||||||
request microversion 1.10, specify the header::
|
request microversion 1.10, specify the header::
|
||||||
|
|
||||||
Openstack-API-Version: placement 1.10
|
OpenStack-API-Version: placement 1.10
|
||||||
|
|
||||||
For more details about Microversions, please reference:
|
For more details about Microversions, please reference:
|
||||||
`Microversions
|
`Microversions
|
||||||
|
@@ -74,7 +74,7 @@ Update traits
|
|||||||
Insert a new custom trait. If traits already exists 204 will be returned.
|
Insert a new custom trait. If traits already exists 204 will be returned.
|
||||||
|
|
||||||
There are two kinds of traits: the standard traits and the custom traits.
|
There are two kinds of traits: the standard traits and the custom traits.
|
||||||
The standard traits are interoperable across different Openstack cloud
|
The standard traits are interoperable across different OpenStack cloud
|
||||||
deployments. The definition of standard traits comes from the `os-traits`
|
deployments. The definition of standard traits comes from the `os-traits`
|
||||||
library. The standard traits are read-only in the placement API which means
|
library. The standard traits are read-only in the placement API which means
|
||||||
that the user can't modify any standard traits through API.
|
that the user can't modify any standard traits through API.
|
||||||
|
Reference in New Issue
Block a user