Merge "Clean up release notes for Bobcat"

This commit is contained in:
Zuul 2023-12-06 10:59:48 +00:00 committed by Gerrit Code Review
commit 88b93884b6
8 changed files with 23 additions and 24 deletions

View File

@ -2,5 +2,5 @@
features: features:
- | - |
Adds a new ``kolla_bifrost_deploy_image_user_data_content`` variable used Adds a new ``kolla_bifrost_deploy_image_user_data_content`` variable used
to define the custom user_data content used by the cloud-init for overcloud to define custom ``user_data`` content used by cloud-init for overcloud
provision. provision.

View File

@ -1,7 +1,7 @@
--- ---
features: features:
- | - |
Adds initial support for configuring NVIDIA vGPUs. For more information please see Adds initial support for configuring NVIDIA vGPUs. For more information
the `new documentation please see the `new documentation
<https://docs.openstack.org/kayobe/latest/configuration/reference/vgpu.yml>`_ <https://docs.openstack.org/kayobe/latest/configuration/reference/vgpu.html>`_
for this feature. for this feature.

View File

@ -1,4 +1,4 @@
--- ---
features: features:
- | - |
Adds support for using DellOS 10 switches with Networking Generic Switch. Adds support for using Dell OS10 switches with Networking Generic Switch.

View File

@ -1,5 +1,5 @@
--- ---
features: features:
- | - |
Adds a experimental support for layering multiple environments using a Adds experimental support for layering multiple environments using a
.kayobe-environment file. ``.kayobe-environment`` file.

View File

@ -1,7 +1,7 @@
--- ---
fixes: fixes:
- | - |
When merging kolla config, fallback to templating when only one source file When merging Kolla configuration, fallback to templating when only one
exists. This allows you to use config that templates to invalid yaml/ini as source file exists. This allows you to use configuration that templates to
long as there isn't an environment override. This improves backwards invalid YAML/INI as long as there is no environment override. This improves
compatability where it was permitted to use such constructs. backwards compatibility where it was permitted to use such constructs.

View File

@ -46,7 +46,6 @@ deprecations:
* ``kolla_extra_placement`` * ``kolla_extra_placement``
* ``kolla_extra_sahara`` * ``kolla_extra_sahara``
Use of Kolla custom service configuration files in Kolla custom service configuration files in ``etc/kayobe/kolla/config`` and
``etc/kayobe/kolla/config`` and
``etc/kayobe/environments/<environment>/kolla/config`` should be used ``etc/kayobe/environments/<environment>/kolla/config`` should be used
instead. instead.

View File

@ -2,12 +2,12 @@
fixes: fixes:
- | - |
When determining whether or not a host needs bootstrapping, we attempt to When determining whether or not a host needs bootstrapping, we attempt to
connect to the host using ansible_user, if the login fails, we then assume connect to the host using ``ansible_user``, if the login fails, we then
that the host needs bootstrapping. In previous releases we used a manually assume that the host needs bootstrapping. In previous releases we used a
crafted ``ssh`` command. This did respect any customisations to the SSH manually crafted ``ssh`` command. This did not respect any customisations
arguments made through ansible configuration. We now use the raw module so to the SSH arguments made through Ansible configuration. We now use the raw
that these customisations are used when connecting to the host. One module so that these customisations are used when connecting to the host.
possible use case is to configure a jump host between the control host and One possible use case is to configure a jump host between the control host
the target hosts. If bootstrapping was needed, hosts will now show as and the target hosts. If bootstrapping was needed, hosts will now show as
unreachable in the summary stats at the end of the run. This can safely be unreachable in the summary stats at the end of the run. This can safely be
ignored. ignored.

View File

@ -6,9 +6,9 @@ fixes:
``kolla_ansible_default_custom_passwords`` and own dictionary with custom ``kolla_ansible_default_custom_passwords`` and own dictionary with custom
passwords in configuration files. Now passwords in configuration files. Now
``kolla_ansible_extra_custom_passwords`` should provide only user custom ``kolla_ansible_extra_custom_passwords`` should provide only user custom
passwords to add or override in the passwords.yml. passwords to add or override in ``kolla/passwords.yml``.
upgrade: upgrade:
- | - |
Now no need to combine ``kolla_ansible_default_custom_passwords`` and Introduces a new variable ``kolla_ansible_extra_custom_passwords`` to avoid
``kolla_ansible_custom_passwords`` in your custom configuration. Just use the need to combine ``kolla_ansible_default_custom_passwords`` and
``kolla_ansible_extra_custom_passwords`` to add or override passwords. ``kolla_ansible_custom_passwords`` when adding or overriding passwords.