Clean up release notes for Bobcat
Change-Id: I96f00721c173cf095463424c0ca8779c54943591
This commit is contained in:
parent
1edf231477
commit
99d0368693
@ -2,5 +2,5 @@
|
||||
features:
|
||||
- |
|
||||
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.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds initial support for configuring NVIDIA vGPUs. For more information please see
|
||||
the `new documentation
|
||||
<https://docs.openstack.org/kayobe/latest/configuration/reference/vgpu.yml>`_
|
||||
Adds initial support for configuring NVIDIA vGPUs. For more information
|
||||
please see the `new documentation
|
||||
<https://docs.openstack.org/kayobe/latest/configuration/reference/vgpu.html>`_
|
||||
for this feature.
|
||||
|
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds support for using DellOS 10 switches with Networking Generic Switch.
|
||||
Adds support for using Dell OS10 switches with Networking Generic Switch.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds a experimental support for layering multiple environments using a
|
||||
.kayobe-environment file.
|
||||
Adds experimental support for layering multiple environments using a
|
||||
``.kayobe-environment`` file.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
When merging kolla config, fallback to templating when only one source file
|
||||
exists. This allows you to use config that templates to invalid yaml/ini as
|
||||
long as there isn't an environment override. This improves backwards
|
||||
compatability where it was permitted to use such constructs.
|
||||
When merging Kolla configuration, fallback to templating when only one
|
||||
source file exists. This allows you to use configuration that templates to
|
||||
invalid YAML/INI as long as there is no environment override. This improves
|
||||
backwards compatibility where it was permitted to use such constructs.
|
||||
|
@ -46,7 +46,6 @@ deprecations:
|
||||
* ``kolla_extra_placement``
|
||||
* ``kolla_extra_sahara``
|
||||
|
||||
Use of Kolla custom service configuration files in
|
||||
``etc/kayobe/kolla/config`` and
|
||||
Kolla custom service configuration files in ``etc/kayobe/kolla/config`` and
|
||||
``etc/kayobe/environments/<environment>/kolla/config`` should be used
|
||||
instead.
|
||||
|
@ -2,12 +2,12 @@
|
||||
fixes:
|
||||
- |
|
||||
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
|
||||
that the host needs bootstrapping. In previous releases we used a manually
|
||||
crafted ``ssh`` command. This did respect any customisations to the SSH
|
||||
arguments made through ansible configuration. We now use the raw module so
|
||||
that these customisations are used when connecting to the host. One
|
||||
possible use case is to configure a jump host between the control host and
|
||||
the target hosts. If bootstrapping was needed, hosts will now show as
|
||||
connect to the host using ``ansible_user``, if the login fails, we then
|
||||
assume that the host needs bootstrapping. In previous releases we used a
|
||||
manually crafted ``ssh`` command. This did not respect any customisations
|
||||
to the SSH arguments made through Ansible configuration. We now use the raw
|
||||
module so that these customisations are used when connecting to the host.
|
||||
One possible use case is to configure a jump host between the control host
|
||||
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
|
||||
ignored.
|
||||
|
@ -6,9 +6,9 @@ fixes:
|
||||
``kolla_ansible_default_custom_passwords`` and own dictionary with custom
|
||||
passwords in configuration files. Now
|
||||
``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:
|
||||
- |
|
||||
Now no need to combine ``kolla_ansible_default_custom_passwords`` and
|
||||
``kolla_ansible_custom_passwords`` in your custom configuration. Just use
|
||||
``kolla_ansible_extra_custom_passwords`` to add or override passwords.
|
||||
Introduces a new variable ``kolla_ansible_extra_custom_passwords`` to avoid
|
||||
the need to combine ``kolla_ansible_default_custom_passwords`` and
|
||||
``kolla_ansible_custom_passwords`` when adding or overriding passwords.
|
||||
|
Loading…
Reference in New Issue
Block a user