support for jammy was added to yoga in:
https://review.opendev.org/c/openstack/kolla-ansible/+/869127
it should thus be perfectly fine to directly upgrade to jammy
and then upgrade to zed.
Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Id77704f4386b48c9bfd7b684bee3fb47d2b4a93a
there are currently known bugs in our interaction with the ansible
--limit option. document those and recommend not to use this like it
was agreed in the kolla meeting:
https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-02-21-14.00.log.txt
Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Iaeaa8c667ce7cd677b2b3dc2096ef4e52c1f651f
The development quickstart document has not been updated for a
while, and it has become desynchronized with the regular quickstart.
Change-Id: I6b14623b73b0032df94f0f633659a1b6dfc15dea
This reverts commit f8d4db54db.
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 94a74f58c7.
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
This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.
The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kolla_max_fail_percentage, and individual services may define a max
failure percentage via <service>_max_fail_percentage.
Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.
Closes-Bug: #1833737
Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f
This commit addresses a few shortcomings in the etcd service:
* Adding or removing etcd nodes required manual intervention.
* The etcd service would have brief outages during upgrades or
reconfigures because restarts weren't always serialised.
This makes the etcd service follow a similar pattern to mariadb:
* There is now a distiction between bootstrapping the cluster
and adding / removing another member.
* This more closely follows etcd's upstream bootstrapping
guidelines.
* The etcd role now serialises restarts internally so the
kolla_serial pattern is no longer appropriate (or necessary).
This does not remove the need for manual intervention in all
failure modes: the documentation has been updated to address the
most common issues.
Note that there's repetition in the container specifications: this
is somewhat deliberate. In a future cleanup, it's intended to reduce
the duplication.
Change-Id: I39829ba0c5894f8e549f9b83b416e6db4fafd96f
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