[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
This commit is contained in:
Sean Mooney
parent
320c6fadde
commit
6314f09ed4
@ -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,
|
||||
|
||||
@ -47,5 +47,5 @@ prelude: |
|
||||
stopped on the destination host until manually started.
|
||||
|
||||
- Nova APIs now `by default support new RBAC policies <https://docs.openstack.org/nova/latest/configuration/policy.html>`
|
||||
and scopes. See our `Policy Concepts documention <https://docs.openstack.org/nova/latest/configuration/policy-concepts.html>`
|
||||
and scopes. See our `Policy Concepts documentation <https://docs.openstack.org/nova/latest/configuration/policy-concepts.html>`
|
||||
for further details.
|
||||
|
||||
@ -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**
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
The old pci.passthrough_whitelist, glob syntax, is still valid config.
|
||||
@ -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
|
||||
<http://docs.ceph.com/docs/luminous/start/hardware-recommendations/#hard-disk-drives>`_
|
||||
Ceph deployments where multiple OSDs are running on a single disk. The new
|
||||
|
||||
@ -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.
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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``
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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``.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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`_.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user