Merge "Refine release notes before kolla 2024.1 release"
This commit is contained in:
Zuul
Gerrit Code Review
commit
652a8f8f72
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Adds a new variable ``prometheus_ceph_exporter_interval`` for controlling
|
||||
Ceph's metrics scrape interval.
|
||||
Added a new variable ``prometheus_ceph_exporter_interval`` for controlling
|
||||
the scrape interval of Ceph metrics.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Minimum supported Ansible version is now ``8`` (ansible-core 2.15)
|
||||
and maximum supported is ``9`` (ansible-core 2.16).
|
||||
The minimum supported Ansible version is now ``8`` (ansible-core 2.15),
|
||||
and the maximum supported is ``9`` (ansible-core 2.16).
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Adds separate role for changing sysctl settings.
|
||||
This role automatically checks if the systems supports
|
||||
IPv6 and if not, skips the IPv6 sysctl settings.
|
||||
This role expands previous backportable fix of this
|
||||
issue at Icccfc1c509179c3cfd59650b7917a637f9af9646
|
||||
`LP#1906306 <https://launchpad.net/bugs/1906306>`__
|
||||
Introduced a separate role for managing sysctl settings. This role
|
||||
automatically detects support for IPv6 and, if unsupported, skips the IPv6
|
||||
sysctl settings. This role expands the previous backportable fix of this
|
||||
issue, reviewed at
|
||||
https://review.opendev.org/c/openstack/kolla-ansible/+/905831. For more
|
||||
details, see `LP#1906306 <https://launchpad.net/bugs/1906306>`__.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixes nova-cell not updating the cell0 database address when VIP changes.
|
||||
`LP#1915302 <https://launchpad.net/bugs/1915302>`__
|
||||
Fixed nova-cell not updating the cell0 database address when VIP changes.
|
||||
For more details, refer to `LP#1915302 <https://launchpad.net/bugs/1915302>`__.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixes an issue with ``openvswitch`` bridge creation when
|
||||
``neutron_bridge_name`` was specified as two bridges.
|
||||
`LP#2056332 <https://bugs.launchpad.net/kolla-ansible/+bug/2056332>`__
|
||||
Fixed an issue with ``openvswitch`` bridge creation when
|
||||
``neutron_bridge_name`` was specified as two bridges. For details, see
|
||||
`LP#2056332 <https://bugs.launchpad.net/kolla-ansible/+bug/2056332>`__.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixes the use of redis as coordination backend.
|
||||
`LP#2056667 <https://bugs.launchpad.net/kolla-ansible/+bug/2056667>`__
|
||||
Fixed the use of Redis as coordination backend. For details, see
|
||||
`LP#2056667 <https://bugs.launchpad.net/kolla-ansible/+bug/2056667>`__.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fix the wrong configuration of the ovs-dpdk service.
|
||||
this breaks the deployment of kolla-ansible.
|
||||
For more details please see `bug 2058372
|
||||
Fixed the wrong configuration of the ovs-dpdk service, which broke the
|
||||
deployment of Kolla-Ansible. For details, see `bug 2058372
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2058372>`__.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Support for deploying ``Murano`` has been dropped.
|
||||
In addition to that support for deploying outward RabbitMQ (only used
|
||||
for Murano) has been dropped as well.
|
||||
Support for deploying ``Murano`` has been dropped. Additionally, support
|
||||
for deploying outward RabbitMQ (only used for Murano) has been dropped as
|
||||
well.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,8 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Exposes a flag, ``bifrost_enable_ironic_inspector``, to enable
|
||||
ironic-inspector in Bifrost. This option defaults to ``True`` as it can be
|
||||
useful for backwards compatibility. It is still possible to use native
|
||||
in-band inspection when Ironic Inspector is enabled by setting
|
||||
``inspect_interface`` to ``agent``. Please see the Ironic documentation for
|
||||
more details.
|
||||
Exposed a flag, `bifrost_enable_ironic_inspector`, to enable
|
||||
ironic-inspector in Bifrost. This option defaults to `True` as it can be
|
||||
useful for backwards compatibility. It still allows using native in-band
|
||||
inspection when Ironic Inspector is enabled by setting `inspect_interface`
|
||||
to `agent`. Please see the Ironic documentation for more details.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,8 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Implements [Configure tap-as-a-service plugin on neutron containers].
|
||||
Adds the needed changes and configurations in order to use the
|
||||
neutron plugin, tap-as-a-service, to create por mirrors using
|
||||
`openstack tap` commands.
|
||||
`Blueprint configure-taas-plugin
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/configure-taas-plugin>`__
|
||||
Implemented [Configure tap-as-a-service plugin on neutron containers].
|
||||
Added the necessary changes and configurations to use the neutron plugin,
|
||||
tap-as-a-service, for creating port mirrors using `openstack tap` commands.
|
||||
For more information, refer to the blueprint
|
||||
`configure-taas-plugin <https://blueprints.launchpad.net/kolla-ansible/+spec/configure-taas-plugin>`__.
|
||||
|
|
|
|||
|
|
@ -1,23 +1,23 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Implements [Enable Fluentd Plugin Systemd].
|
||||
Adds the needed changes and configurations in order to use the
|
||||
fluentd plugin, systemd, to read logs from /var/log/journal by
|
||||
default. This allows us to read and manipulate this logs for
|
||||
monitoring purposes.
|
||||
Implemented [Enable Fluentd Plugin Systemd].
|
||||
Added the necessary changes and configurations to use the fluentd plugin,
|
||||
systemd, to read logs from /var/log/journal by default. This allows us to
|
||||
read and manipulate these logs for monitoring purposes.
|
||||
|
||||
These logs will be sent to OpenSearch by default, to disable this
|
||||
behavior, set the value of the variable ``enable_fluentd_systemd``
|
||||
to ``false`` in the configuration file ``/etc/kolla/globals.yml``.
|
||||
These logs will be sent to OpenSearch by default. To disable this behavior,
|
||||
set the value of the variable ``enable_fluentd_systemd`` to ``false`` in
|
||||
the configuration file ``/etc/kolla/globals.yml``.
|
||||
|
||||
By default, when enabling central logging, we also enable the
|
||||
``systemd`` plugin. To disable this behavior when central logging
|
||||
is enabled, set the value of the variable ``enable_fluentd_systemd``
|
||||
to ``false`` in the configuration file ``/etc/kolla/globals.yml``.
|
||||
By default, when enabling central logging, we also enable the ``systemd``
|
||||
plugin. To disable this behavior when central logging is enabled, set the
|
||||
value of the variable ``enable_fluentd_systemd`` to ``false`` in the
|
||||
configuration file ``/etc/kolla/globals.yml``.
|
||||
|
||||
fluent-plugin-systemd source:
|
||||
https://github.com/fluent-plugin-systemd/fluent-plugin-systemd
|
||||
|
||||
`Blueprint enable-fluent-plugin-systemd
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/enable-fluent-plugin-systemd>`__
|
||||
For more information, refer to the blueprint
|
||||
`enable-fluent-plugin-systemd
|
||||
<https://blueprints.launchpad.net/kolla-ansible/+spec/enable-fluent-plugin-systemd>`__.
|
||||
|
|
|
|||
|
|
@ -1,24 +1,26 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Changes configuration variable ``designate_enable_notifications_sink``
|
||||
to ``no`` which configures notifications for designate in neutron, nova
|
||||
and control deployment of ``designate-sink`` which is now optional.
|
||||
The configuration variable ``designate_enable_notifications_sink`` has
|
||||
been changed to ``no``, configuring notifications for designate in neutron,
|
||||
nova, and control deployment of ``designate-sink`` which is now optional.
|
||||
|
||||
Operators that want to keep the previous behavior should set this to
|
||||
Operators who want to keep the previous behavior should set this to
|
||||
``true``.
|
||||
|
||||
features:
|
||||
- |
|
||||
Adds new variables to be used by the neutron role,
|
||||
New variables have been added to be used by the neutron role,
|
||||
``neutron_dns_integration`` and ``neutron_dns_domain``.
|
||||
They allow to enable/disable internal/external DNS integrations,
|
||||
or their combinations.
|
||||
They allow enabling/disabling internal/external DNS integrations, or their
|
||||
combinations.
|
||||
|
||||
fixes:
|
||||
- |
|
||||
Fixes configuration of DNS integrations. See `LP##2049503
|
||||
The configuration of DNS integrations has been fixed. See `LP##2049503
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2049503>`__,
|
||||
`DNS Integration
|
||||
<https://docs.openstack.org/neutron/latest/admin/config-dns-int.html>`__
|
||||
<https://docs.openstack.org/neutron/latest/admin/config-dns-int.html>`__,
|
||||
and the `DNS Integration with an External Service
|
||||
<https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html#config-dns-int-ext-serv>`__
|
||||
for details.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fix a trove deployment bug where trove guest-agent failed to connect
|
||||
to RabbitMQ due to the missing of the `oslo_messaging_rabbit` config in
|
||||
Fixed a trove deployment bug where the trove guest-agent failed to connect
|
||||
to RabbitMQ due to the absence of the `oslo_messaging_rabbit` config in
|
||||
`guest-agent.conf`.
|
||||
see `bug 2048822 <https://bugs.launchpad.net/kolla-ansible/+bug/2048822>`__
|
||||
See `bug 2048822 <https://bugs.launchpad.net/kolla-ansible/+bug/2048822>`__
|
||||
for details.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fix trove failed to discover swift endpoint due to the missing of
|
||||
Fixed trove failing to discover the swift endpoint due to the absence of
|
||||
`service_credentials` in guest-agent.conf.
|
||||
see `bug 2048829 <https://bugs.launchpad.net/kolla-ansible/+bug/2048829>`__
|
||||
See `bug 2048829 <https://bugs.launchpad.net/kolla-ansible/+bug/2048829>`__
|
||||
for details.
|
||||
|
|
|
|||
|
|
@ -1,11 +1,12 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Updates the default Grafana OpenSearch datasource configuration to use
|
||||
values for OpenSearch that work out of the box. Replaces the Elasticsearch
|
||||
Updated the default Grafana OpenSearch datasource configuration to use
|
||||
values for OpenSearch that work out of the box. Replaced the Elasticsearch
|
||||
values that were previously being used. The new configuration can be
|
||||
applied by deleting your datasource and reconfiguring Grafana through kolla
|
||||
ansible. In order to prevent dashboards from breaking when the datasource
|
||||
is deleted, one should use `datasource variables
|
||||
<https://grafana.com/docs/grafana/latest/dashboards/variables/add-template-variables/#add-a-data-source-variable>`__
|
||||
in Grafana. See bug `2039500 <https://bugs.launchpad.net/kolla-ansible/+bug/2039500>`__.
|
||||
applied by deleting your datasource and reconfiguring Grafana through
|
||||
Kolla Ansible. To prevent dashboards from breaking when the datasource is
|
||||
deleted, one should use `datasource variables
|
||||
<https://grafana.com/docs/grafana/latest/dashboards/variables/add-template-variables/#add-a-data-source-variable>`
|
||||
in Grafana. See bug `2039500
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2039500>`.
|
||||
|
|
|
|||
|
|
@ -1,23 +1,24 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixes bug `#2039498
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2039498>`__ where the
|
||||
grafana docker volume was bind mounted over Grafana plugins installed at
|
||||
image build time. This is fixed by copying the dashboards into the
|
||||
container from an existing bind mount instead of using the ``grafana``
|
||||
volume. This however leaves behind the volume which can be removed by
|
||||
setting ``grafana_remove_old_volume`` to ``true``. Please note that any
|
||||
plugins installed via the cli directly and not through kolla will be lost
|
||||
when doing this. In a future release ``grafana_remove_old_volume`` will
|
||||
default to ``true``.
|
||||
Fixed bug `#2039498
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2039498>`__ where the Grafana
|
||||
docker volume was bind mounted over Grafana plugins installed at image
|
||||
build time. This was fixed by copying the dashboards into the container
|
||||
from an existing bind mount instead of using the ``grafana`` volume.
|
||||
However, this leaves behind the volume, which can be removed by setting
|
||||
``grafana_remove_old_volume`` to ``true``. Please note that any plugins
|
||||
installed via the CLI directly and not through Kolla will be lost when
|
||||
doing this. In a future release, ``grafana_remove_old_volume`` will default
|
||||
to ``true``.
|
||||
|
||||
upgrade:
|
||||
- |
|
||||
The ``grafana`` volume is no longer used. If you wish to automatically
|
||||
remove the old volume, set ``grafana_remove_old_volume`` to ``true``. Note
|
||||
that doing this will lose any plugins installed via the cli directly and
|
||||
not through kolla. If you have previously installed Grafana plugins via the
|
||||
Grafana UI, or CLI, you must change to installing them at image `build time
|
||||
that doing this will lose any plugins installed via the CLI directly and
|
||||
not through Kolla. If you have previously installed Grafana plugins via the
|
||||
Grafana UI or CLI, you must change to installing them at image `build time
|
||||
<https://docs.openstack.org/kolla/latest/admin/image-building.html#dockerfile-customisation>`__.
|
||||
The grafana volume, which will contain existing custom plugins, will be
|
||||
The Grafana volume, which contains existing custom plugins, will be
|
||||
automatically removed in the D release.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Horizon role was reworked to preferred local_settings.d
|
||||
configuration model. Files ``local_settings`` and
|
||||
``custom_local_settings`` were renamed to ``_9998-kolla-settings.py``
|
||||
and ``_9999-custom-settings.py`` Users who use horizon's custom
|
||||
configuration have to change the names of those files in
|
||||
``/etc/kolla/config/horizon`` also.
|
||||
The Horizon role has been reworked to the preferred local_settings.d
|
||||
configuration model. Files ``local_settings`` and ``custom_local_settings``
|
||||
have been renamed to ``_9998-kolla-settings.py`` and
|
||||
``_9999-custom-settings.py`` respectively. Users who use Horizon's custom
|
||||
configuration must change the names of those files in
|
||||
``/etc/kolla/config/horizon`` as well.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,10 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Enable elevated access for project scoped service role
|
||||
in Ironic. Ironic recently started to enforce new policies
|
||||
and scope. And Ironic is one of the sole openstack project
|
||||
which need system scope for some admin related api calls.
|
||||
However Ironic also started to allow project-scope behaviour
|
||||
for service role with setting
|
||||
``rbac_service_role_elevated_access``. This change enables
|
||||
this setting to get similar behaviour of service role as other
|
||||
openstack projects.
|
||||
Elevated access for project-scoped service role in Ironic has been
|
||||
enabled. Ironic recently started to enforce new policies and scopes,
|
||||
and it is one of the few OpenStack projects that require system scope
|
||||
for some admin-related API calls. However, Ironic has also begun to
|
||||
allow project-scoped behavior for service roles by setting
|
||||
``rbac_service_role_elevated_access``. This change enables this setting
|
||||
to achieve similar behavior for service role as other OpenStack projects.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Add the service role to ironic service users. Ironic recently enforced
|
||||
new policy validation and added service role support.
|
||||
The service role has been added to Ironic service users. Ironic recently
|
||||
enforced new policy validation and added support for service roles.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Adds support for setting the max fail percentage for Ansible plays via
|
||||
``kolla_max_fail_percentage``. It can also be set on a per-service basis,
|
||||
e.g. ``nova_max_fail_percentage``.
|
||||
Support has been added for setting the max fail percentage for Ansible
|
||||
plays via ``kolla_max_fail_percentage``. It can also be set on a
|
||||
per-service basis, e.g., ``nova_max_fail_percentage``.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Adds missing support for friendly labels for Prometheus Ironic exporter and
|
||||
Alertmanager metrics. `LP#2041855
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2041855>`__
|
||||
Support for friendly labels has been added for Prometheus Ironic exporter
|
||||
and Alertmanager metrics. See `LP#2041855
|
||||
<https://bugs.launchpad.net/kolla-ansible/+bug/2041855>`__ for details.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Re-added support for neutron-fwaas v2. Set ``enable_neutron_fwaas: yes``
|
||||
to enable.
|
||||
Support for neutron-fwaas v2 has been re-added.
|
||||
Set `enable_neutron_fwaas: yes` to enable.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Configure Skyline's Prometheus connection to make the Monitor Center work.
|
||||
The latest Skyline Console has now a Monitor Center in the administrator
|
||||
view that displays information from Prometheus. For that to work the
|
||||
Prometheus connection needs to be set up in skyline.yaml.
|
||||
Configuration has been added to connect Skyline's Prometheus to make the
|
||||
Monitor Center work. The latest Skyline Console now includes a Monitor
|
||||
Center in the administrator view that displays information from Prometheus.
|
||||
For this to work, the Prometheus connection needs to be set up in
|
||||
skyline.yaml.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Allow overriding of Skyline configuration files by supplying your own
|
||||
version of nginx.conf for Skyline Console, gunicorn.py and skyline.yaml
|
||||
for Skyline API Server. Place the files in the skyline subfolder of
|
||||
your Kolla config directory, skyline.yaml will be merged with the
|
||||
Kolla provided version.
|
||||
The ability to override Skyline configuration files has been added. You can
|
||||
supply your own versions of nginx.conf for Skyline Console, gunicorn.py,
|
||||
and skyline.yaml for the Skyline API Server. Place the files in the skyline
|
||||
subfolder of your Kolla config directory; skyline.yaml will be merged with
|
||||
the Kolla-provided version.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,7 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Add more services now supported by Skyline to the configuration to make
|
||||
them accessible to Skylines's frontend console.
|
||||
New services include Barbican, Designate, Masakari and Swift or Ceph RGW.
|
||||
Only one of Swift and CEph RGW can be used, if both are enabled, Swift is
|
||||
configured.
|
||||
More services supported by Skyline have been added to the configuration,
|
||||
making them accessible to Skyline's frontend console. The new services
|
||||
include Barbican, Designate, Masakari, and Swift or Ceph RGW. If both
|
||||
Swift and Ceph RGW are enabled, only Swift is configured.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Enables SSO in Skyline Console if Keystone federation is enabled and
|
||||
at least one identity provider with protocol openid is set up.
|
||||
Skyline Console's redirect URI is added to Keystone's trusted dashboards.
|
||||
Single Sign-On (SSO) is enabled in Skyline Console if Keystone federation
|
||||
is enabled and at least one identity provider with the openid protocol
|
||||
is set up. Skyline Console's redirect URI is added to Keystone's trusted
|
||||
dashboards.
|
||||
|
|
|
|||
Loading…
Reference in New Issue