Merge "[codespell] doc,devstack and gate typos"
This commit is contained in:
commit
051d95b377
|
@ -5,7 +5,7 @@
|
||||||
# only test advanced neutron features, unrelated to multi-cell testing.
|
# only test advanced neutron features, unrelated to multi-cell testing.
|
||||||
^tempest.scenario.test_network
|
^tempest.scenario.test_network
|
||||||
|
|
||||||
# Also exlude resize and migrate tests with qos ports as qos is currently
|
# Also exclude resize and migrate tests with qos ports as qos is currently
|
||||||
# not supported in cross cell resize case . See
|
# not supported in cross cell resize case . See
|
||||||
# https://bugs.launchpad.net/nova/+bug/1907511 for details
|
# https://bugs.launchpad.net/nova/+bug/1907511 for details
|
||||||
test_migrate_with_qos_min_bw_allocation
|
test_migrate_with_qos_min_bw_allocation
|
||||||
|
|
|
@ -5,4 +5,5 @@ ned
|
||||||
deques
|
deques
|
||||||
affinitized
|
affinitized
|
||||||
noes
|
noes
|
||||||
Wile
|
wile
|
||||||
|
usera
|
|
@ -778,7 +778,7 @@ governors on the fly, as explained below.
|
||||||
supports scaling govenors before modifying the configuration option.
|
supports scaling govenors before modifying the configuration option.
|
||||||
|
|
||||||
If the strategy is set to ``governor``, a couple of config options are provided
|
If the strategy is set to ``governor``, a couple of config options are provided
|
||||||
to define which exact CPU govenor to use for each of the up and down states :
|
to define which exact CPU governor to use for each of the up and down states :
|
||||||
|
|
||||||
- :oslo.config:option:`libvirt.cpu_power_governor_low` will define the governor
|
- :oslo.config:option:`libvirt.cpu_power_governor_low` will define the governor
|
||||||
to use for the powerdown state (defaults to ``powersave``)
|
to use for the powerdown state (defaults to ``powersave``)
|
||||||
|
|
|
@ -519,7 +519,7 @@ For the viommu attributes:
|
||||||
|
|
||||||
* ``intremap``, ``caching_mode``, and ``iotlb``
|
* ``intremap``, ``caching_mode``, and ``iotlb``
|
||||||
options for viommu (These attributes are driver attributes defined in
|
options for viommu (These attributes are driver attributes defined in
|
||||||
`Libvirt IOMMU Domain`_) will direcly enabled.
|
`Libvirt IOMMU Domain`_) will directly enabled.
|
||||||
|
|
||||||
* ``eim`` will directly enabled if machine type is Q35.
|
* ``eim`` will directly enabled if machine type is Q35.
|
||||||
``eim`` is driver attribute defined in `Libvirt IOMMU Domain`_.
|
``eim`` is driver attribute defined in `Libvirt IOMMU Domain`_.
|
||||||
|
|
|
@ -39,7 +39,7 @@ Libvirt enforces CPU limits in terms of *shares* and *quotas*, configured
|
||||||
via :nova:extra-spec:`quota:cpu_shares` and :nova:extra-spec:`quota:cpu_period`
|
via :nova:extra-spec:`quota:cpu_shares` and :nova:extra-spec:`quota:cpu_period`
|
||||||
/ :nova:extra-spec:`quota:cpu_quota`, respectively. Both are implemented using
|
/ :nova:extra-spec:`quota:cpu_quota`, respectively. Both are implemented using
|
||||||
the `cgroups cpu controller`__. Note that allowed values for *shares* are
|
the `cgroups cpu controller`__. Note that allowed values for *shares* are
|
||||||
platform dependant.
|
platform dependent.
|
||||||
|
|
||||||
CPU shares are a proportional weighted share of total CPU resources relative to
|
CPU shares are a proportional weighted share of total CPU resources relative to
|
||||||
other instances. It does not limit CPU usage if CPUs are not busy. There is no
|
other instances. It does not limit CPU usage if CPUs are not busy. There is no
|
||||||
|
@ -158,7 +158,7 @@ For example, to configure **outbound** traffic to an average of 262 Mbit/s
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
The speed limit values in above example are specified in kilobytes/second,
|
The speed limit values in above example are specified in kilobytes/second,
|
||||||
whle the burst value is in kilobytes.
|
while the burst value is in kilobytes.
|
||||||
|
|
||||||
VMWare
|
VMWare
|
||||||
~~~~~~
|
~~~~~~
|
||||||
|
|
|
@ -1077,7 +1077,7 @@ to a negative number and the weighing has the opposite effect of the default.
|
||||||
|
|
||||||
This weigher compares hosts and orders them based on their number of instances
|
This weigher compares hosts and orders them based on their number of instances
|
||||||
respectively. By default the weigher is doing nothing but you
|
respectively. By default the weigher is doing nothing but you
|
||||||
can change its behaviour by modifiying the value of
|
can change its behaviour by modifying the value of
|
||||||
:oslo.config:option:`filter_scheduler.num_instances_weight_multiplier`.
|
:oslo.config:option:`filter_scheduler.num_instances_weight_multiplier`.
|
||||||
A positive value will favor hosts with a larger number of instances (packing
|
A positive value will favor hosts with a larger number of instances (packing
|
||||||
strategy) while a negative value will follow a spread strategy that will
|
strategy) while a negative value will follow a spread strategy that will
|
||||||
|
|
|
@ -309,7 +309,7 @@ Parameter type
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
The parameters are defined in the parameter file (``parameters.yaml``).
|
The parameters are defined in the parameter file (``parameters.yaml``).
|
||||||
The type of parameters have to be one of followings:
|
The type of parameters have to be one of following:
|
||||||
|
|
||||||
* ``array``
|
* ``array``
|
||||||
|
|
||||||
|
|
|
@ -76,7 +76,7 @@ used by many OpenStack projects, including the following steps.
|
||||||
|
|
||||||
- Dependency Freeze
|
- Dependency Freeze
|
||||||
|
|
||||||
- time to co-ordinate the final list of dependencies, and give packagers
|
- time to coordinate the final list of dependencies, and give packagers
|
||||||
time to package them
|
time to package them
|
||||||
- generally it is also quite destabilising to take upgrades (beyond
|
- generally it is also quite destabilising to take upgrades (beyond
|
||||||
bug fixes) this late
|
bug fixes) this late
|
||||||
|
|
|
@ -160,7 +160,7 @@ the defaults from the :doc:`install guide </install/index>` will be sufficient.
|
||||||
* :doc:`Running nova-api on wsgi <user/wsgi>`: Considerations for using a real
|
* :doc:`Running nova-api on wsgi <user/wsgi>`: Considerations for using a real
|
||||||
WSGI container instead of the baked-in eventlet web server.
|
WSGI container instead of the baked-in eventlet web server.
|
||||||
|
|
||||||
.. # NOTE(amotoki): toctree needs to be placed at the end of the secion to
|
.. # NOTE(amotoki): toctree needs to be placed at the end of the section to
|
||||||
# keep the document structure in the PDF doc.
|
# keep the document structure in the PDF doc.
|
||||||
.. toctree::
|
.. toctree::
|
||||||
:hidden:
|
:hidden:
|
||||||
|
|
|
@ -181,7 +181,7 @@ would become:
|
||||||
provider_tree.update_inventory(nodename, inv_data)
|
provider_tree.update_inventory(nodename, inv_data)
|
||||||
|
|
||||||
When reporting inventory for the standard resource classes ``VCPU``,
|
When reporting inventory for the standard resource classes ``VCPU``,
|
||||||
``MEMORY_MB`` and ``DISK_GB``, implementors of ``update_provider_tree`` may
|
``MEMORY_MB`` and ``DISK_GB``, implementers of ``update_provider_tree`` may
|
||||||
need to set the ``allocation_ratio`` and ``reserved`` values in the
|
need to set the ``allocation_ratio`` and ``reserved`` values in the
|
||||||
``inv_data`` dict based on configuration to reflect changes on the compute
|
``inv_data`` dict based on configuration to reflect changes on the compute
|
||||||
for allocation ratios and reserved resource amounts back to the placement
|
for allocation ratios and reserved resource amounts back to the placement
|
||||||
|
|
|
@ -105,7 +105,7 @@ echo "Resource provider allocations were cleaned up properly."
|
||||||
|
|
||||||
function get_binding_profile_value
|
function get_binding_profile_value
|
||||||
{
|
{
|
||||||
# Returns the value of the key in the binding profile if exsits or return
|
# Returns the value of the key in the binding profile if exists or return
|
||||||
# empty.
|
# empty.
|
||||||
local port=${1}
|
local port=${1}
|
||||||
local key=${2}
|
local key=${2}
|
||||||
|
@ -253,7 +253,7 @@ if [[ "$my_key" == "" ]]; then
|
||||||
fi
|
fi
|
||||||
|
|
||||||
echo "Verifying online_data_migrations idempotence"
|
echo "Verifying online_data_migrations idempotence"
|
||||||
# We will re-use the server created earlier for this test. (A server needs to
|
# We will reuse the server created earlier for this test. (A server needs to
|
||||||
# be present during the run of online_data_migrations and archiving).
|
# be present during the run of online_data_migrations and archiving).
|
||||||
|
|
||||||
# Run the online data migrations before archiving.
|
# Run the online data migrations before archiving.
|
||||||
|
|
|
@ -103,6 +103,6 @@ check_untyped_defs = true
|
||||||
warn_unused_ignores = true
|
warn_unused_ignores = true
|
||||||
|
|
||||||
[codespell]
|
[codespell]
|
||||||
skip = *.po,*.js,*.css,*.html,*.svg,HACKING.py,*build*,*_static*,doc/dictionary.txt,*.pyc,*.inv,*.gz,*.jpg,*.png,*.vsd,*.graffle
|
skip = *.po,*.js,*.css,*.html,*.svg,HACKING.py,*hacking*,*build*,*_static*,doc/dictionary.txt,*.pyc,*.inv,*.gz,*.jpg,*.png,*.vsd,*.graffle
|
||||||
count =
|
count =
|
||||||
quiet-level = 4
|
quiet-level = 4
|
Loading…
Reference in New Issue