| Age | Commit message (Collapse) | Author | Files | Lines |
|
``kolla-ansible genconfig`` includes some tasks [1] that require
containers to still be running. Move the config generation to be done
before containers are stopped.
Also make it clearer that containers should not be restarted with the
new config until after RabbitMQ state has been reset.
1. https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/octavia/tasks/get_resources_info.yml#L2
Change-Id: I1d4fc32e5963a8e8fa4a8fc7c467cadf0f26fd5f
(cherry picked from commit 44aa76cf2a5144fe7d3b148d897096cccb09604d)
|
|
Updates the HA section to account for the change to quorum queues and
streams by default.
Also adds a note to the SLURP section as it's not needed for Epoxy.
Change-Id: I3d6f8a13319b9789c07e21a2122f11c77b629ead
|
|
Followup on Ib69fc0017b3bfbc8da4dfd4301710fbf88be661a. This change
adds the ability to provide the NTP (time source) server for multiple
DHCP ranges in the Ironic Inspector DHCP server.
Change-Id: I4bbfef3a391b8582ae73cbe06138715b43584dec
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
(cherry picked from commit 5a37bd6a7f22680f311bf9c39b6da5f29498b965)
|
|
|
|
|
|
|
|
Given we bump the RabbitMQ version each release, there is a manual
upgrade to an intermediary RabbitMQ version needed before a skip-level
upgrade can be performed.
Change-Id: Id8a5ebe19a50ebdc59d12667889472c803b8d7c8
|
|
Added Restart=on-failure policy to octavia-interface systemd unit
Added octavia_interface_wait_timeout variable to control
TimeoutStartSec in octavia-interface systemd unit
Change-Id: I9de6c27131ce78e85aac56ea5d91d9740fd58354
Closes-Bug: 2067036
(cherry picked from commit a3fcc07c7a52d72cee497f1abc8e4b8bb661557a)
|
|
This isn't obvious from reading of the docs, let's make sure users are
aware.
Change-Id: I0da1ad16bfab00bed7e935cca118551a6c5860c6
(cherry picked from commit ef26c7e1e65dc3b985fd443922b4edb9e9e24195)
|
|
We don't use dots in the image name
Change-Id: I29172448c14a1ca9a5fa23abe701366f875959e0
(cherry picked from commit 07312e61b2c370360db8f554b477718fe657a2a0)
|
|
Required before a SLURP upgrade
Change-Id: I09a45d26a6075554b204e007f64122f23de5f53c
(cherry picked from commit 249c1e89de0bef6a00f3abecdd8dfc820a5719fb)
|
|
|
|
This fixes an issue where it is not possible to customise the `host`
config option in the Nova Compute Ironic config file without breaking
detection of the service.
This is a backwards compatible fix, which allows a user to set the
`host` config option using Ansible host or group vars.
Other reasons for not using the default host setting of
`{{ ansible_hostname }}-ironic` are covered in [1].
[1] https://specs.openstack.org/openstack/nova-specs/specs/2024.1/approved/ironic-shards.html#migrate-from-peer-list-to-shard-key.
Closes-Bug: #2056571
Change-Id: I9b562f6a5722f21b7dbec2a4d53a46a57c829155
(cherry picked from commit ac7c1e96e3709785395db275feb83419c13e1c13)
|
|
Closes-Bug: #2070051
Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/923544
Change-Id: I221eb136e77c61aef39e8646b48b927352d1419d
(cherry picked from commit a535e65a85aa99af2e42a22a891de79a172bd033)
|
|
Change-Id: Iad34c3340325d2aad0f468d88e94007823871a41
(cherry picked from commit b8146efd1c671971028cac85942e06c5ab8890c5)
|
|
neutron-fwaas has become active again
Depends-On: https://review.opendev.org/c/openstack/kolla/+/914855
Change-Id: Ie5a7b2da9a351e8f47a1ae830bb2fee0a8e35e38
|
|
|
|
|
|
Change-Id: I3975b5266c8700c81439b4d891d446eba2a52e54
|
|
Fix existing spelling errors
Change-Id: Ie689cf5a344aaa630a4860448b09242333a8e119
|
|
|
|
This reverts commit 9675347fecd2907e7f60e84e405abcedf426b229.
Reason for revert: Masakari CI is working
Change-Id: Ifb44a437b96c0c029210b1491ee6c6403ee9e6fb
|
|
Travial fix
Change-Id: Ie8de00bccd940a6c45a81fb505a6c3cd9d86a2aa
|
|
|
|
|
|
|
|
|
|
Change-Id: I5b4a30e605bb143cf342f83f0c811c25046269ef
|
|
Change-Id: I0a086c59076120aa53e6a05526dbab88e393c1c7
|
|
|
|
This patch implements horizon's preferred way how
to configure itself described in docs [1],
[1] https://docs.openstack.org/horizon/latest/configuration/settings.html
Depends-On: https://review.opendev.org/c/openstack/kolla/+/906339
Change-Id: I60ab4634bf4333c47d00b12fc4ec00570062bd18
|
|
This patch basically does a simple thing, on the basis
of a variable neutron_dns_integration it enables/disables
DNS integration.
There is also precheck added which checks whether dns_domain
in neutron.conf has a non-default value if DNS integration is
enabled as this is requirement.
[1] https://docs.openstack.org/neutron/latest/admin/config-dns-int.html
[2] https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html#config-dns-int-ext-serv
Closes-Bug: #2049503
Change-Id: I90f0f8dcec6fa0112179f050d96e9d9db5956cf8
|
|
This reverts commit f8d4db54db8f2ab2c7f99f0fcbc456177d33ddad.
Reason for revert: Zun was deprecated due to the hard dependency on old version of docker and etcd. Right now, the problem was fixed.
Change-Id: I9fe760e2b9b774b5ea623e6b305de004fc0c6dd2
|
|
* Remove docker's cluster-store option. This option was removed from
the latest version of docker so we removed it.
* Switch kuryr's capability_scope from "global" to "local". The "global"
scope relies on a cluster store but docker no longer supports it.
Change-Id: Ie62396184552938d099223f9d325a41c9a5067c3
|
|
This reverts commit 94a74f58c7891e41ca637c4e2a6450ca88cbfb56.
Reason for revert: Zun/Kuryr-libnetwork has switched to "local" scope which doesn't require docker 20 anymore. It should work for latest docker version. Related patches:
https://review.opendev.org/c/openstack/zun/+/903884
Change-Id: Ieb545ae5a5917322f599728587c3f04ea8356126
|
|
|
|
|
|
We previously used ElasticSearch Curator for managing log
retention. Now that we have moved to OpenSearch, we can use
the Index State Management (ISM) plugin which is bundled with
OpenSearch.
This change adds support for automating the configuration of
the ISM plugin via the OpenSearch API. By default, it has
similar behaviour to the previous ElasticSearch Curator
default policy.
Closes-Bug: #2047037
Change-Id: I5c6d938f2bc380f1575ee4f16fe17c6dca37dcba
|
|
RabbitMQ does not need to be reconfigured when migrating from non-HA
queues to quorum queues.
Change-Id: I69d409732ff8eb7ae736e95f8a5d290efd33fa32
|
|
This implements a global toggle `om_enable_rabbitmq_quorum_queues`
to enable quorum queues for each service in RabbitMQ, similar to
what was done for HA[0].
Quorum Queues are enabled by default.
Quorum queues are more reliable, safer, simpler and faster than
replicated mirrored classic queues[1].
Mirrored classic queues are deprecated and scheduled for removal
in RabbitMQ 4.0[2].
Notice, that we do not need a new policy in the RabbitMQ definitions
template, because their usage is enabled on the client side and can't
be set using a policy[3].
Notice also, that quorum queues are not yet enabled in oslo.messaging
for the usage of reply_ and fanout_ queues (transient queues).
This will change once[4] is merged.
[0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771
[1]: https://www.rabbitmq.com/quorum-queues.html
[2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/
[3]: https://www.rabbitmq.com/quorum-queues.html#declaring
[4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479
Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: I6c033d460a5c9b93c346e9e47e93b159d3c27830
|
|
|
|
|
|
|
|
Since the CI is failing and there are no contributors working on fixing
this, we are deprecating the service.
Also mention other deprecations in the README.
Change-Id: Ifff11645f6b4682810c042a0421d1eb569ab0ede
|
|
Adds configurations and changes tasks to enable the
systemd plugin. Additionaly, the plugin is set to
read logs from the /var/log/journal directory
Implements: enable-fluent-plugin-systemd
Signed-off-by: Juan Pablo Suazo <jsuazo@whitestack.com>
Change-Id: Ic714a341befa5f906d9c0f78fa86f4c934df87cd
|
|
Introduce keystone_federation_oidc_additional_options variable
Change-Id: I39b9f35dab6f4e3ac2fcb505aabd2589e6e2ca69
|
|
This avoids the need to use a proxy, or some other means, to connect to
Prometheus. This is disabled by default and can be enabled by setting
enable_prometheus_server_external to true.
Change-Id: Ia0af044ff436c2a204b357750a16ff49fcdfec45
|
|
Kolla Ansible should deploy Glance and Cinder Backup with
S3 backend support working out-of-the-box.
The S3 backend had been re-introduced in Ussuri after being
deprecated around the Mitaka timeframe, and having some local
object storage options is nice for testing..
Closes-Bug: #1977515
Change-Id: I4ca58382d1ee568bfca2ad108495422163f81260
Co-authored-by: Juan Pablo Suazo <jsuazo@whitestack.com>
Co-authored-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
Following Monasca initial removal in [1]
[1]: I6fc7842bcda18e417a3fd21c11e28979a470f1cf
Change-Id: I94d6f102e8da3882f37f3007639b917c49f907a9
|
|
* Zun currently has a dependency on a combination of Docker and
etcd that is no longer installable (or supported) in newer
distros.
* These components are core dependencies of other systems and
vendoring them will be very painful.
* Work to update Zun past this is scheduled for the 'C' cycle.
* If Zun regains compatibility, backports to this series will be
considered.
Change-Id: I6a2a4ffdcaf1c4fab1097e94d5f255ffb9a2947d
|