Fix inconsistency of 'NOTE:' description
Use the 'note' directive. TrivialFix Change-Id: If342940f8cc64591778ad21ce6cccbe006c0145b
This commit is contained in:
parent
ae4b5d0147
commit
48eb371e62
@ -1021,7 +1021,9 @@ To customize the VMware driver, use the configuration option settings below.
|
||||
|
||||
This is not the full path - just a folder prefix. This should only be used when a datastore cache is shared between compute nodes.
|
||||
|
||||
Note: This should only be used when the compute nodes are running on same host or they have a shared file system.
|
||||
.. note::
|
||||
|
||||
This should only be used when the compute nodes are running on same host or they have a shared file system.
|
||||
|
||||
Possible values:
|
||||
|
||||
@ -1035,7 +1037,9 @@ To customize the VMware driver, use the configuration option settings below.
|
||||
|
||||
The datastore_regex setting specifies the datastores to use with Compute. For example, datastore_regex="nas.*" selects all the data stores that have a name starting with "nas".
|
||||
|
||||
NOTE: If no regex is given, it just picks the datastore with the most freespace.
|
||||
.. note::
|
||||
|
||||
If no regex is given, it just picks the datastore with the most freespace.
|
||||
|
||||
Possible values:
|
||||
|
||||
|
@ -217,9 +217,11 @@ Nova Cells v2
|
||||
the properties cannot be set, this will return 2. Otherwise, the exit
|
||||
code will be 0.
|
||||
|
||||
NOTE: Updating the transport_url or database_connection fields on
|
||||
a running system will NOT result in all nodes immediately using the
|
||||
new values. Use caution when changing these values.
|
||||
.. note::
|
||||
|
||||
Updating the transport_url or database_connection fields on
|
||||
a running system will NOT result in all nodes immediately using the
|
||||
new values. Use caution when changing these values.
|
||||
|
||||
Nova Logs
|
||||
~~~~~~~~~
|
||||
|
@ -69,7 +69,10 @@ used by many OpenStack projects, including the following steps.
|
||||
- String Freeze
|
||||
|
||||
- give translators time to translate all our strings
|
||||
- Note: debug logs are no longer translated
|
||||
|
||||
.. note::
|
||||
|
||||
debug logs are no longer translated
|
||||
|
||||
- Dependency Freeze
|
||||
|
||||
@ -104,12 +107,15 @@ https://blueprints.launchpad.net/nova/queens and specs at
|
||||
https://specs.openstack.org/openstack/nova-specs/specs/queens/index.html
|
||||
|
||||
Starting with Liberty, we are keeping a backlog open for submission at all
|
||||
times. Note: the focus is on accepting and agreeing problem statements
|
||||
as being in scope, rather than queueing up work items for the next
|
||||
release. We are still working on a new lightweight process to get out of
|
||||
the backlog and approved for a particular release. For more details on
|
||||
backlog specs, please see:
|
||||
http://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html
|
||||
times.
|
||||
|
||||
.. note::
|
||||
|
||||
The focus is on accepting and agreeing problem statements as being in scope,
|
||||
rather than queueing up work items for the next release. We are still
|
||||
working on a new lightweight process to get out of the backlog and approved
|
||||
for a particular release. For more details on backlog specs, please see:
|
||||
http://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html
|
||||
|
||||
There can be exceptions, usually it's an urgent feature request that
|
||||
comes up after the initial deadline. These will generally be discussed
|
||||
|
@ -181,7 +181,9 @@ An example of online data migrations are the flavor migrations done as part
|
||||
of Nova object version 1.18. This included a transient migration of flavor
|
||||
storage from one database location to another.
|
||||
|
||||
:emphasis:`Note: Database downgrades are not supported.`
|
||||
.. note::
|
||||
|
||||
Database downgrades are not supported.
|
||||
|
||||
Migration policy:
|
||||
'''''''''''''''''
|
||||
@ -279,8 +281,11 @@ Graceful service shutdown
|
||||
new workers before the graceful shutdown of the old workers. In the case
|
||||
of singleton services, like nova-compute, some actions could be delayed
|
||||
during the restart, but ideally no actions should fail due to the restart.
|
||||
NOTE: while this is true for the RabbitMQ RPC backend, we need to confirm
|
||||
what happens for other RPC backends.
|
||||
|
||||
.. note::
|
||||
|
||||
While this is true for the RabbitMQ RPC backend, we need to confirm
|
||||
what happens for other RPC backends.
|
||||
|
||||
API load balancer draining
|
||||
When upgrading API nodes, you can make your load balancer only send new
|
||||
|
Loading…
x
Reference in New Issue
Block a user