From 6314f09ed4574ca9d03a726c0cfd1d7108b1a12c Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 3 Oct 2023 01:17:21 +0100 Subject: [PATCH] [codespell] apply codespell to the releasenotes this change fixes the typos in the releasenotes """ codespell --ignore-words=doc/dictionary.txt -i 3 -w releasenotes/ """ Change-Id: I29cd5268cd129b194c43a9f6b08a2b7b1c254b65 --- .../add-spice-compression-support-e41676f445544e8d.yaml | 2 +- releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml | 2 +- .../bp-policy-defaults-refresh-b8e6e2d6b1a7bc21.yaml | 2 +- releasenotes/notes/bug-1581977-310e5f218ccb1d16.yaml | 2 +- releasenotes/notes/bug-1884231-16acf297d88b122e.yaml | 2 +- releasenotes/notes/bug-1911924-6e93d8a5038d18c1.yaml | 2 +- ...lt-zero-disk-flavor-to-admin-api-fd99e162812c2c7f.yaml | 2 +- .../notes/delete-dangling-volumes-2615100187fe29fb.yaml | 2 +- .../extra-sorting-for-host-cells-c03e37de1e57043b.yaml | 2 +- ...y-validation-with-deleted-groups-4f685fd1d6b84192.yaml | 2 +- releasenotes/notes/greendns-34df7f9fba952bcd.yaml | 2 +- .../notes/guest-iommu-device-4795c3a060aca424.yaml | 2 +- ...live_migration_wait_for_vif_plug-c9dcb034067890d8.yaml | 2 +- .../notes/microversion-2-90-59fb6d4ec420b9f4.yaml | 2 +- ...unplug-to-separate-os-vif-plugin-f7ee42da4ed9739b.yaml | 2 +- ...tiple-config-files-with-mod_wsgi-f114ea5fdd8b9a51.yaml | 8 ++++---- .../neutron-connection-retries-c276010afe238abc.yaml | 2 +- ...sthrough-whitelist-regex-support-5004c5db4fbe09c8.yaml | 2 +- .../notes/rbd-enhance-get-pool-info-14afc8eccab49dcf.yaml | 2 +- ...extensions-enable-config-options-d6b3d62a6cc1cbe5.yaml | 2 +- ...move-retry-and-aggregate-filters-f872a85d0b815982.yaml | 2 +- .../notes/remove-topic-config-opts-336f72bebf4e9141.yaml | 2 +- ..._deprecated_barbican_config_opts-7eb4e801d0ac252f.yaml | 2 +- ...sical_network_from_multi-segment-eec5a490c1ed8739.yaml | 2 +- .../notes/stable-compute-uuid-08663a0955616728.yaml | 4 ++-- .../support-sys.argv-in-wsgi-app-2dc5006f9e9e5f9e.yaml | 2 +- releasenotes/notes/ussuri-prelude-4b96f1244cefcdf4.yaml | 2 +- releasenotes/notes/vdpa-cc2300d2c46c150b.yaml | 8 ++++---- ...tification-interface-is-complete-06725d7d4d761849.yaml | 2 +- ...virtio-as-default-display-device-5341d3d5180036e2.yaml | 2 +- ...s-libvirt-rbd-host-block-devices-ca5e3c187342ab4d.yaml | 2 +- releasenotes/source/mitaka.rst | 4 ++-- 32 files changed, 40 insertions(+), 40 deletions(-) diff --git a/releasenotes/notes/add-spice-compression-support-e41676f445544e8d.yaml b/releasenotes/notes/add-spice-compression-support-e41676f445544e8d.yaml index b370889171ce..706ea3d6f049 100644 --- a/releasenotes/notes/add-spice-compression-support-e41676f445544e8d.yaml +++ b/releasenotes/notes/add-spice-compression-support-e41676f445544e8d.yaml @@ -13,7 +13,7 @@ features: These configuration options can be used to enable and set the SPICE compression settings for libvirt (QEMU/KVM) provisioned instances. Each configuration option is optional and can be set - explictly to configure the associated SPICE compression setting + explicitly to configure the associated SPICE compression setting for libvirt. If all configuration options are not set, then none of the SPICE compression settings will be configured for libvirt, which corresponds to the behavior before this change. In this case, diff --git a/releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml b/releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml index 66890684afd4..6a9f65094593 100644 --- a/releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml +++ b/releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml @@ -47,5 +47,5 @@ prelude: | stopped on the destination host until manually started. - Nova APIs now `by default support new RBAC policies ` - and scopes. See our `Policy Concepts documention ` + and scopes. See our `Policy Concepts documentation ` for further details. diff --git a/releasenotes/notes/bp-policy-defaults-refresh-b8e6e2d6b1a7bc21.yaml b/releasenotes/notes/bp-policy-defaults-refresh-b8e6e2d6b1a7bc21.yaml index b6be3955d72d..6e2e97990352 100644 --- a/releasenotes/notes/bp-policy-defaults-refresh-b8e6e2d6b1a7bc21.yaml +++ b/releasenotes/notes/bp-policy-defaults-refresh-b8e6e2d6b1a7bc21.yaml @@ -26,7 +26,7 @@ upgrade: * **New Defaults(Admin, Member and Reader)** Policies are default to Admin, Member and Reader roles. Old roles - are also supproted. You can switch to new defaults via config option + are also supported. You can switch to new defaults via config option ``[oslo_policy]enforce_new_defaults`` in ``nova.conf`` file. * **Policies granularity** diff --git a/releasenotes/notes/bug-1581977-310e5f218ccb1d16.yaml b/releasenotes/notes/bug-1581977-310e5f218ccb1d16.yaml index 8498b5c36e95..e40052b11827 100644 --- a/releasenotes/notes/bug-1581977-310e5f218ccb1d16.yaml +++ b/releasenotes/notes/bug-1581977-310e5f218ccb1d16.yaml @@ -1,7 +1,7 @@ --- fixes: - | - Nova will now replace periods (``.``) with dashes (``-``) when santizing an + Nova will now replace periods (``.``) with dashes (``-``) when sanitizing an instance's display name for use as a hostname. Nova publishes hostnames for instances via the metadata service and config diff --git a/releasenotes/notes/bug-1884231-16acf297d88b122e.yaml b/releasenotes/notes/bug-1884231-16acf297d88b122e.yaml index 7ed64a0c1637..285f42c2bfcc 100644 --- a/releasenotes/notes/bug-1884231-16acf297d88b122e.yaml +++ b/releasenotes/notes/bug-1884231-16acf297d88b122e.yaml @@ -11,6 +11,6 @@ features: ``hw:emulator_threads_policy`` extra spec. - | It is now possible to specify a mask in ``hw:cpu_realtime_mask`` without a - leading ``^``. When this is ommitted, the value will specify the cores that + leading ``^``. When this is omitted, the value will specify the cores that should be included in the set of realtime cores, as opposed to those that should be excluded. diff --git a/releasenotes/notes/bug-1911924-6e93d8a5038d18c1.yaml b/releasenotes/notes/bug-1911924-6e93d8a5038d18c1.yaml index ff27f936aa6b..cf342f8e900b 100644 --- a/releasenotes/notes/bug-1911924-6e93d8a5038d18c1.yaml +++ b/releasenotes/notes/bug-1911924-6e93d8a5038d18c1.yaml @@ -2,7 +2,7 @@ fixes: - | The `os-resetState`_ API will now log an instance action when called. The - resulting instance action being visable via the `os-instance-actions`_ API + resulting instance action being visible via the `os-instance-actions`_ API to users and admins, resolving `bug 1911924`_. .. _bug 1911924: https://launchpad.net/bugs/1911924 diff --git a/releasenotes/notes/default-zero-disk-flavor-to-admin-api-fd99e162812c2c7f.yaml b/releasenotes/notes/default-zero-disk-flavor-to-admin-api-fd99e162812c2c7f.yaml index e76921ecbba9..78f8e9b261c5 100644 --- a/releasenotes/notes/default-zero-disk-flavor-to-admin-api-fd99e162812c2c7f.yaml +++ b/releasenotes/notes/default-zero-disk-flavor-to-admin-api-fd99e162812c2c7f.yaml @@ -1,7 +1,7 @@ --- upgrade: - | - The defalut value for policy rule + The default value for policy rule ``os_compute_api:servers:create:zero_disk_flavor`` has changed from ``rule:admin_or_owner`` to ``rule:admin_api`` which means that by default, users without the admin role will not be allowed to create servers using diff --git a/releasenotes/notes/delete-dangling-volumes-2615100187fe29fb.yaml b/releasenotes/notes/delete-dangling-volumes-2615100187fe29fb.yaml index e758fb2e7f5f..c027b212905a 100644 --- a/releasenotes/notes/delete-dangling-volumes-2615100187fe29fb.yaml +++ b/releasenotes/notes/delete-dangling-volumes-2615100187fe29fb.yaml @@ -17,7 +17,7 @@ features: After Nova database cleanup, similarly Cinder database is checked for attachments related to instance. If attachments found in Cinder DB that - are not present in Nova DB, they will get deleted from Cinder databse. + are not present in Nova DB, they will get deleted from Cinder database. See `spec`__ for more details. diff --git a/releasenotes/notes/extra-sorting-for-host-cells-c03e37de1e57043b.yaml b/releasenotes/notes/extra-sorting-for-host-cells-c03e37de1e57043b.yaml index ea708053146b..6854c883e3eb 100644 --- a/releasenotes/notes/extra-sorting-for-host-cells-c03e37de1e57043b.yaml +++ b/releasenotes/notes/extra-sorting-for-host-cells-c03e37de1e57043b.yaml @@ -1,7 +1,7 @@ --- features: - | - Extra sortings were added to numa_fit_instance_to_host function + Extra sorting were added to numa_fit_instance_to_host function to balance usage of hypervisor's NUMA cells. Hypervisor's NUMA cells with more free resources (CPU, RAM, PCI if requested) will be used first (spread strategy) when configuration option diff --git a/releasenotes/notes/fix-group-policy-validation-with-deleted-groups-4f685fd1d6b84192.yaml b/releasenotes/notes/fix-group-policy-validation-with-deleted-groups-4f685fd1d6b84192.yaml index 7f7d42bd0e07..0a319016ce54 100644 --- a/releasenotes/notes/fix-group-policy-validation-with-deleted-groups-4f685fd1d6b84192.yaml +++ b/releasenotes/notes/fix-group-policy-validation-with-deleted-groups-4f685fd1d6b84192.yaml @@ -5,7 +5,7 @@ fixes: nova will assert that the policy is not violated on move operations and initial instance creation. As noted in `bug 1890244`_, if a server was created in a server group and that group was later deleted - the validation upcall would fail due to an uncaught excpetion if the + the validation upcall would fail due to an uncaught exception if the server group was deleted. This prevented evacuate and other move operations form functioning. This has now been fixed and nova will ignore deleted server groups. diff --git a/releasenotes/notes/greendns-34df7f9fba952bcd.yaml b/releasenotes/notes/greendns-34df7f9fba952bcd.yaml index d42795747c7e..deaf695fc468 100644 --- a/releasenotes/notes/greendns-34df7f9fba952bcd.yaml +++ b/releasenotes/notes/greendns-34df7f9fba952bcd.yaml @@ -5,7 +5,7 @@ fixes: monkey patching of greendns broke ipv6. https://bugs.launchpad.net/nova/+bug/1164822 Since then nova has been disabling eventlet monkey patching - of greendns. Eventlet adressed the ipv6 limitation in v0.17 + of greendns. Eventlet addressed the ipv6 limitation in v0.17 with the introduction of python 3 support in 2015. Nova however continued to disable it, which can result i slow dns queries blocking the entire nova api or other binary diff --git a/releasenotes/notes/guest-iommu-device-4795c3a060aca424.yaml b/releasenotes/notes/guest-iommu-device-4795c3a060aca424.yaml index 314c2c0ffe7c..db5819702ba6 100644 --- a/releasenotes/notes/guest-iommu-device-4795c3a060aca424.yaml +++ b/releasenotes/notes/guest-iommu-device-4795c3a060aca424.yaml @@ -15,7 +15,7 @@ features: neither X86 (Q35) or AArch64. Note that, enable vIOMMU might introduce significant performance overhead. - You can see performance comparision table from + You can see performance comparison table from `AMD vIOMMU session on KVM Forum 2021`_. For above reason, vIOMMU should only be enable for workflow that require it. .. _`AMD vIOMMU session on KVM Forum 2021`: https://static.sched.com/hosted_files/kvmforum2021/da/vIOMMU%20KVM%20Forum%202021%20-%20v4.pdf diff --git a/releasenotes/notes/live_migration_wait_for_vif_plug-c9dcb034067890d8.yaml b/releasenotes/notes/live_migration_wait_for_vif_plug-c9dcb034067890d8.yaml index b3f971b90304..2603e865b653 100644 --- a/releasenotes/notes/live_migration_wait_for_vif_plug-c9dcb034067890d8.yaml +++ b/releasenotes/notes/live_migration_wait_for_vif_plug-c9dcb034067890d8.yaml @@ -11,7 +11,7 @@ other: should do if you use the same networking backend universally, you do not have to worry about this. - This is disabled by default for backward compatibilty and because the + This is disabled by default for backward compatibility and because the compute service cannot reliably determine which types of virtual interfaces (``port.binding:vif_type``) will send ``network-vif-plugged`` events without an accompanying port ``binding:host_id`` change. diff --git a/releasenotes/notes/microversion-2-90-59fb6d4ec420b9f4.yaml b/releasenotes/notes/microversion-2-90-59fb6d4ec420b9f4.yaml index 0bc0b4d4be92..b6254a04bdf7 100644 --- a/releasenotes/notes/microversion-2-90-59fb6d4ec420b9f4.yaml +++ b/releasenotes/notes/microversion-2-90-59fb6d4ec420b9f4.yaml @@ -18,7 +18,7 @@ deprecations: - | The ``os_compute_api:os-extended-server-attributes`` policy controls which users a number of server extended attributes are shown to. - Configuring visiblity of the ``OS-EXT-SRV-ATTR:hostname`` attribute via + Configuring visibility of the ``OS-EXT-SRV-ATTR:hostname`` attribute via this policy has now been deprecated and will be removed in a future release. Upon removal, this attribute will be shown for all users regardless of policy configuration. diff --git a/releasenotes/notes/move-ivs-plug-unplug-to-separate-os-vif-plugin-f7ee42da4ed9739b.yaml b/releasenotes/notes/move-ivs-plug-unplug-to-separate-os-vif-plugin-f7ee42da4ed9739b.yaml index b3d29e2b44f3..b801cd322e3b 100644 --- a/releasenotes/notes/move-ivs-plug-unplug-to-separate-os-vif-plugin-f7ee42da4ed9739b.yaml +++ b/releasenotes/notes/move-ivs-plug-unplug-to-separate-os-vif-plugin-f7ee42da4ed9739b.yaml @@ -7,5 +7,5 @@ upgrade: driver. Releases are available on https://pypi.org/project/os-vif-bigswitch/. Major version for the package matches upstream neutron version number. Minor - version tracks compatiblity with Big Cloud Fabric (BCF) releases, and + version tracks compatibility with Big Cloud Fabric (BCF) releases, and typically is set to the lowest supported BCF release. diff --git a/releasenotes/notes/multiple-config-files-with-mod_wsgi-f114ea5fdd8b9a51.yaml b/releasenotes/notes/multiple-config-files-with-mod_wsgi-f114ea5fdd8b9a51.yaml index f4361477deb1..7b573dfa5f51 100644 --- a/releasenotes/notes/multiple-config-files-with-mod_wsgi-f114ea5fdd8b9a51.yaml +++ b/releasenotes/notes/multiple-config-files-with-mod_wsgi-f114ea5fdd8b9a51.yaml @@ -3,11 +3,11 @@ fixes: - | apache mod_wsgi does not support passing commandline arguments to the wsgi application that it hosts. As a result when the nova api or metadata api - where run under mod_wsgi it was not posible to use multiple config files + where run under mod_wsgi it was not possible to use multiple config files or non-default file names i.e. nova-api.conf - This has been adressed by the intoduction of a new, optional, envionment - varible ``OS_NOVA_CONFIG_FILES``. ``OS_NOVA_CONFIG_FILES`` is a ``;`` - seperated list fo file path relitive to ``OS_NOVA_CONFIG_DIR``. + This has been addressed by the intoduction of a new, optional, environment + variable ``OS_NOVA_CONFIG_FILES``. ``OS_NOVA_CONFIG_FILES`` is a ``;`` + separated list of file path relitive to ``OS_NOVA_CONFIG_DIR``. When unset the default ``api-paste.ini`` and ``nova.conf`` will be used form ``/etc/nova``. This is supported for the nova api and nova metadata wsgi applications. diff --git a/releasenotes/notes/neutron-connection-retries-c276010afe238abc.yaml b/releasenotes/notes/neutron-connection-retries-c276010afe238abc.yaml index 9a0871f557bf..9ebdbe0d8596 100644 --- a/releasenotes/notes/neutron-connection-retries-c276010afe238abc.yaml +++ b/releasenotes/notes/neutron-connection-retries-c276010afe238abc.yaml @@ -5,7 +5,7 @@ fixes: 3. It controls how many times to retry a Neutron API call in response to a HTTP connection failure. An example scenario where it will help is when a deployment is using HAProxy and connections get closed after idle time. If - an incoming request tries to re-use a connection that is simultaneously + an incoming request tries to reuse a connection that is simultaneously being torn down, a HTTP connection failure will occur and previously Nova would fail the entire request. With retries, Nova can be more resilient in this scenario and continue the request if a retry succeeds. Refer to diff --git a/releasenotes/notes/pci-passthrough-whitelist-regex-support-5004c5db4fbe09c8.yaml b/releasenotes/notes/pci-passthrough-whitelist-regex-support-5004c5db4fbe09c8.yaml index f11c7ff469ad..675270a747cb 100644 --- a/releasenotes/notes/pci-passthrough-whitelist-regex-support-5004c5db4fbe09c8.yaml +++ b/releasenotes/notes/pci-passthrough-whitelist-regex-support-5004c5db4fbe09c8.yaml @@ -2,4 +2,4 @@ features: - Enhance pci.passthrough_whitelist to support regular expression syntax. The 'address' field can be regular expression syntax. - The old pci.passthrough_whitelist, glob sytnax, is still valid config. \ No newline at end of file + The old pci.passthrough_whitelist, glob syntax, is still valid config. \ No newline at end of file diff --git a/releasenotes/notes/rbd-enhance-get-pool-info-14afc8eccab49dcf.yaml b/releasenotes/notes/rbd-enhance-get-pool-info-14afc8eccab49dcf.yaml index 4e4352e4bc06..ac9db8876c6c 100644 --- a/releasenotes/notes/rbd-enhance-get-pool-info-14afc8eccab49dcf.yaml +++ b/releasenotes/notes/rbd-enhance-get-pool-info-14afc8eccab49dcf.yaml @@ -1,7 +1,7 @@ --- other: - | - The reporting for bytes available for RBD has been enhanced to accomodate + The reporting for bytes available for RBD has been enhanced to accommodate `unrecommended `_ Ceph deployments where multiple OSDs are running on a single disk. The new diff --git a/releasenotes/notes/remove-deprecated-extensions-enable-config-options-d6b3d62a6cc1cbe5.yaml b/releasenotes/notes/remove-deprecated-extensions-enable-config-options-d6b3d62a6cc1cbe5.yaml index 17829e075018..f6f8d4e4d56d 100644 --- a/releasenotes/notes/remove-deprecated-extensions-enable-config-options-d6b3d62a6cc1cbe5.yaml +++ b/releasenotes/notes/remove-deprecated-extensions-enable-config-options-d6b3d62a6cc1cbe5.yaml @@ -3,5 +3,5 @@ upgrade: - | Deprecated config options to enable/disable extensions ``extensions_blacklist`` and ``extensions_whitelist`` have been removed. - This means all API extensions are always enabled. If you modifed policy, + This means all API extensions are always enabled. If you modified policy, please double check you have the correct policy settings for all APIs. \ No newline at end of file diff --git a/releasenotes/notes/remove-retry-and-aggregate-filters-f872a85d0b815982.yaml b/releasenotes/notes/remove-retry-and-aggregate-filters-f872a85d0b815982.yaml index af2a4a7c8e32..be2ec1f5f1dd 100644 --- a/releasenotes/notes/remove-retry-and-aggregate-filters-f872a85d0b815982.yaml +++ b/releasenotes/notes/remove-retry-and-aggregate-filters-f872a85d0b815982.yaml @@ -5,7 +5,7 @@ upgrade: RetryFilter Deprecated in Train (20.0.0). The RetryFilter has - not been requied since Queens following the completion of the + not been required since Queens following the completion of the return-alternate-hosts blueprint Aggregatefilter, AggregateRAMFilter, AggregateDiskFilter diff --git a/releasenotes/notes/remove-topic-config-opts-336f72bebf4e9141.yaml b/releasenotes/notes/remove-topic-config-opts-336f72bebf4e9141.yaml index f709700b2eca..83fb341ae115 100644 --- a/releasenotes/notes/remove-topic-config-opts-336f72bebf4e9141.yaml +++ b/releasenotes/notes/remove-topic-config-opts-336f72bebf4e9141.yaml @@ -2,7 +2,7 @@ upgrade: - | Configuration options related to RPC topics were deprecated in the past - releases and are now completly removed from nova. There was no need to + releases and are now completely removed from nova. There was no need to let users choose the RPC topics for all services. There was little benefit from this and it made it really easy to break Nova by changing the value of topic options. diff --git a/releasenotes/notes/remove_deprecated_barbican_config_opts-7eb4e801d0ac252f.yaml b/releasenotes/notes/remove_deprecated_barbican_config_opts-7eb4e801d0ac252f.yaml index 001fb70e9dad..623e269c99e2 100644 --- a/releasenotes/notes/remove_deprecated_barbican_config_opts-7eb4e801d0ac252f.yaml +++ b/releasenotes/notes/remove_deprecated_barbican_config_opts-7eb4e801d0ac252f.yaml @@ -2,7 +2,7 @@ upgrade: - | Configuration options related to the Barbican were deprecated and now - completly removed from ``barbican`` group. These options are available in + completely removed from ``barbican`` group. These options are available in the Castellan library. Following are the affected options: - ``barbican.catalog_info`` diff --git a/releasenotes/notes/retrieve_physical_network_from_multi-segment-eec5a490c1ed8739.yaml b/releasenotes/notes/retrieve_physical_network_from_multi-segment-eec5a490c1ed8739.yaml index 9d942629f617..9d46c82391fb 100644 --- a/releasenotes/notes/retrieve_physical_network_from_multi-segment-eec5a490c1ed8739.yaml +++ b/releasenotes/notes/retrieve_physical_network_from_multi-segment-eec5a490c1ed8739.yaml @@ -3,6 +3,6 @@ fixes: - Physical network name will be retrieved from a multi-segement network. The current implementation will retrieve the physical network name for the first segment that provides it. This is mostly intended to support a - combinatin of vxlan and vlan segments. Additional work will be required to + combination of vxlan and vlan segments. Additional work will be required to support a case of multiple vlan segments associated with different physical networks. diff --git a/releasenotes/notes/stable-compute-uuid-08663a0955616728.yaml b/releasenotes/notes/stable-compute-uuid-08663a0955616728.yaml index fdeb593bd291..26dbdf069cb6 100644 --- a/releasenotes/notes/stable-compute-uuid-08663a0955616728.yaml +++ b/releasenotes/notes/stable-compute-uuid-08663a0955616728.yaml @@ -3,7 +3,7 @@ features: - | The compute manager now uses a local file to provide node uuid persistence to guard against problems with renamed services, among other things. - Deployers wishing to ensure that *new* compute services get a predicatble + Deployers wishing to ensure that *new* compute services get a predictable uuid before initial startup may provision that file and nova will use it, otherwise nova will generate and write one to a `compute_id` file in `CONF.state_path` the first time it starts up. Accidental renames of a @@ -12,7 +12,7 @@ features: they manage nodes and uuids differently. upgrade: - | - Existing compute nodes will, upon upgrade, perist the uuid of the compute + Existing compute nodes will, upon upgrade, persist the uuid of the compute node assigned to their hostname at first startup. Since this must match what is currently in the database, it is important to let nova provision this file from its database. Nova will only persist to a `compute_id` file diff --git a/releasenotes/notes/support-sys.argv-in-wsgi-app-2dc5006f9e9e5f9e.yaml b/releasenotes/notes/support-sys.argv-in-wsgi-app-2dc5006f9e9e5f9e.yaml index bccce9821d48..17fb7cdd1f30 100644 --- a/releasenotes/notes/support-sys.argv-in-wsgi-app-2dc5006f9e9e5f9e.yaml +++ b/releasenotes/notes/support-sys.argv-in-wsgi-app-2dc5006f9e9e5f9e.yaml @@ -3,7 +3,7 @@ features: - | Now nova-api and nova-api-metadata WSGI services support command line arguments similarly to other nova services. For example these services - now support specifying mutliple config files via --config-file parameter. + now support specifying multiple config files via --config-file parameter. Please note that passing command line arguments to WSGI apps depends on the given WSGI runner. For example uwsgi supports this via the --pyargv parameter of the uwsgi binary. diff --git a/releasenotes/notes/ussuri-prelude-4b96f1244cefcdf4.yaml b/releasenotes/notes/ussuri-prelude-4b96f1244cefcdf4.yaml index 2d9282fc426a..00b22b6a1a0f 100644 --- a/releasenotes/notes/ussuri-prelude-4b96f1244cefcdf4.yaml +++ b/releasenotes/notes/ussuri-prelude-4b96f1244cefcdf4.yaml @@ -53,7 +53,7 @@ prelude: | .. __: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id79 - - Support for `heterogenous virtual GPU types per compute node`__. + - Support for `heterogeneous virtual GPU types per compute node`__. .. __: https://docs.openstack.org/nova/latest/admin/virtual-gpu.html#enable-gpu-types-compute diff --git a/releasenotes/notes/vdpa-cc2300d2c46c150b.yaml b/releasenotes/notes/vdpa-cc2300d2c46c150b.yaml index 9bf5cc3a994e..dbcb48a675b7 100644 --- a/releasenotes/notes/vdpa-cc2300d2c46c150b.yaml +++ b/releasenotes/notes/vdpa-cc2300d2c46c150b.yaml @@ -9,7 +9,7 @@ features: virtio interfaces. issues: - | - Nova currenly does not support the following livecycle operations when + Nova currently does not support the following lifecycle operations when combined with a instance using vDPA ports: shelve, resize, cold migration, live migration, evacuate, suspend or interface attach/detach. Attempting to use one of the above operations will result in a HTTP 409 @@ -26,7 +26,7 @@ issues: This requires the DMA buffers to be locked in memory. As the DMA buffers are allocated by the guest and can be allocated anywhere in the guest RAM, QEMU locks **all** guest RAM. By default the ``RLIMIT_MEMLOCK`` for a - normal QEMU intance is set to 0 and qemu is not allowed to lock guest + normal QEMU instance is set to 0 and qemu is not allowed to lock guest memory. In the case of SR-IOV, libvirt automatically set the limit to guest RAM + 1G which enables QEMU to lock the memory. This does not happen today with vDPA ports. As a result if you use VDPA ports without enabling locking @@ -37,7 +37,7 @@ issues: using ``hw:cpu_realtime`` for its side-effect of locking the guest memory, this usage does not require the guest or host to use realtime kernels. However, all other requirements of ``hw:cpu_realtime`` such as requiring - hw:cpu_policy=dedicated still apply. It is also stongly recommended that - hugpages be enabled for all instnace with locked memory. This can be done + hw:cpu_policy=dedicated still apply. It is also strongly recommended that + hugpages be enabled for all instances with locked memory. This can be done by setting ``hw:mem_page_size``. This will enable nova to correctly account for the fact that the memory is unswapable. diff --git a/releasenotes/notes/versioned-notification-interface-is-complete-06725d7d4d761849.yaml b/releasenotes/notes/versioned-notification-interface-is-complete-06725d7d4d761849.yaml index 2a4143bd22e6..50cb21d1a1fd 100644 --- a/releasenotes/notes/versioned-notification-interface-is-complete-06725d7d4d761849.yaml +++ b/releasenotes/notes/versioned-notification-interface-is-complete-06725d7d4d761849.yaml @@ -4,7 +4,7 @@ features: The versioned notification interface of nova is now complete and in feature parity with the legacy interface. The emitted notifications are documented in `notification dev ref`_ with full sample files. - The deprecation of the legacy notification interface is under dicussion + The deprecation of the legacy notification interface is under discussion and will be handled separately. .. _notification dev ref: https://docs.openstack.org/nova/latest/reference/notifications.html#existing-versioned-notifications diff --git a/releasenotes/notes/virtio-as-default-display-device-5341d3d5180036e2.yaml b/releasenotes/notes/virtio-as-default-display-device-5341d3d5180036e2.yaml index d27efce1fc47..ee96463bebc6 100644 --- a/releasenotes/notes/virtio-as-default-display-device-5341d3d5180036e2.yaml +++ b/releasenotes/notes/virtio-as-default-display-device-5341d3d5180036e2.yaml @@ -6,4 +6,4 @@ features: If your guest has a native kernel (called "virtio-gpu" in Linux; available since Linux 4.4 and above) driver, then it'll be used; otherwise, the 'virtio' model will gracefully fallback to VGA - compatibiliy mode, which is still better than ``cirrus``. + compatibility mode, which is still better than ``cirrus``. diff --git a/releasenotes/notes/workarounds-libvirt-rbd-host-block-devices-ca5e3c187342ab4d.yaml b/releasenotes/notes/workarounds-libvirt-rbd-host-block-devices-ca5e3c187342ab4d.yaml index eb740d0ada46..a4e80fd8766f 100644 --- a/releasenotes/notes/workarounds-libvirt-rbd-host-block-devices-ca5e3c187342ab4d.yaml +++ b/releasenotes/notes/workarounds-libvirt-rbd-host-block-devices-ca5e3c187342ab4d.yaml @@ -4,7 +4,7 @@ other: The ``[workarounds]/rbd_volume_local_attach`` configuration option has been introduced. This can be used by operators to ensure RBD volumes are connected to compute hosts as block devices. This can be used with - the ``[worarounds]/disable_native_luksv1`` configuration option to + the ``[workarounds]/disable_native_luksv1`` configuration option to workaround recently discovered performance issues found within the `libgcrypt library`__ used by QEMU when natively decrypting LUKSv1 encrypted disks. diff --git a/releasenotes/source/mitaka.rst b/releasenotes/source/mitaka.rst index 0e87d62fe356..b0710face1b2 100644 --- a/releasenotes/source/mitaka.rst +++ b/releasenotes/source/mitaka.rst @@ -271,7 +271,7 @@ New Features .. releasenotes/notes/instance-hostname-used-to-populate-ports-dns-name-08341ec73dc076c0.yaml @ b'997d8f516cee99b4e16429d13ca5cf7fc05166aa' -- When booting an instance, its sanitized 'hostname' attribute is now used to populate the 'dns_name' attribute of the Neutron ports the instance is attached to. This functionality enables the Neutron internal DNS service to know the ports by the instance's hostname. As a consequence, commands like 'hostname -f' will work as expected when executed in the instance. When a port's network has a non-blank 'dns_domain' attribute, the port's 'dns_name' combined with the network's 'dns_domain' will be published by Neutron in an external DNS as a service like Designate. As a consequence, the instance's hostname is published in the external DNS as a service. This functionality is added to Nova when the 'DNS Integration' extension is enabled in Neutron. The publication of 'dns_name' and 'dns_domain' combinations to an external DNS as a service additionaly requires the configuration of the appropriate driver in Neutron. When the 'Port Binding' extension is also enabled in Neutron, the publication of a 'dns_name' and 'dns_domain' combination to the external DNS as a service will require one additional update operation when Nova allocates the port during the instance boot. This may have a noticeable impact on the performance of the boot process. +- When booting an instance, its sanitized 'hostname' attribute is now used to populate the 'dns_name' attribute of the Neutron ports the instance is attached to. This functionality enables the Neutron internal DNS service to know the ports by the instance's hostname. As a consequence, commands like 'hostname -f' will work as expected when executed in the instance. When a port's network has a non-blank 'dns_domain' attribute, the port's 'dns_name' combined with the network's 'dns_domain' will be published by Neutron in an external DNS as a service like Designate. As a consequence, the instance's hostname is published in the external DNS as a service. This functionality is added to Nova when the 'DNS Integration' extension is enabled in Neutron. The publication of 'dns_name' and 'dns_domain' combinations to an external DNS as a service additionally requires the configuration of the appropriate driver in Neutron. When the 'Port Binding' extension is also enabled in Neutron, the publication of a 'dns_name' and 'dns_domain' combination to the external DNS as a service will require one additional update operation when Nova allocates the port during the instance boot. This may have a noticeable impact on the performance of the boot process. .. releasenotes/notes/libvirt-live-migration-new-tunneled-option-d7ebb1eb1e95e683.yaml @ b'621594fc41d0e07fd63dfe7c3c5cfee9edc380ad' @@ -638,7 +638,7 @@ Deprecation Notes - The Zookeeper Service Group driver has been removed. - The driver has no known users and is not actively mantained. A warning log + The driver has no known users and is not actively maintained. A warning log message about the driver's state was added for the Kilo release. Also, evzookeeper library that the driver depends on is unmaintained and `incompatible with recent eventlet releases`_.