Fix some typos in nova doc

There are some typos in nova doc:
  affinty
  runnning
  containts
  abolute

This is to fix them.

Change-Id: I18e61e41fd31af4885b449dff3f6988b4bc3065b
changes/56/527856/1
zhufl 5 years ago
parent e599b13e49
commit 915bd8f829
  1. 4
      doc/source/admin/common/nova-show-usage-statistics-for-hosts-instances.rst
  2. 2
      doc/source/admin/cpu-topologies.rst
  3. 2
      doc/source/user/cellsv2-layout.rst

@ -133,9 +133,9 @@ Show instance usage statistics
``hypervisor`` indicates the current hypervisor on which the VM is running.
``nic_details`` containts a list of details per vNIC.
``nic_details`` contains a list of details per vNIC.
``uptime`` is the amount of time in seconds that the VM has been runnning.
``uptime`` is the amount of time in seconds that the VM has been running.
|

@ -350,7 +350,7 @@ maximum of one thread, run:
--property hw_cpu_max_sockets=2 \
--property hw_cpu_max_threads=1
The value specified in the flavor is treated as the abolute limit. The image
The value specified in the flavor is treated as the absolute limit. The image
limits are not permitted to exceed the flavor limits, they can only be equal
to or lower than what the flavor defines. By setting a ``max`` value for
sockets, cores, or threads, administrators can prevent users configuring

@ -331,7 +331,7 @@ affect you. To ensure you do not make futile attempts at rescheduling,
you should set ``[scheduler]/max_attempts=1`` in ``nova.conf``.
The second two are related. The summary is that some of the facilities
that Nova has for ensuring that affinty/anti-affinity is preserved
that Nova has for ensuring that affinity/anti-affinity is preserved
between instances does not function in Pike with a multi-cell
layout. If you don't use affinity operations, then this will not
affect you. To make sure you don't make futile attempts at the

Loading…
Cancel
Save