db4a5dbca2
Now that Podman natively supports healthchecks, let's use them; which will reduce our footprint in how we consume Podman. Using native healthcheck brings a few benefits: - Less Ansible tasks to manage the systemd resources, so deployment should be slightly faster. - Leverage features into the container tooling directly; not in tripleo. This patch does the following: - Fix the podman arguments for healthcheck options in podman_container module, transparent for the end-user. Indeed, the args are "health-*". - Remove the management of timers and healthcheck services and their requires. - New playbook "healthcheck_cleanup" to cleanup previous systemd healthchecks if they exist. - Update molecule default testing to test if new healthchecks work fine. - Update the role manual for healthchecks usage. This patch should be transparent for the end-users except that the systemd healthchecks won't exist anymore: Instead of running: "systemctl status tripleo_keystone_healthcheck.timer status", we would run "podman healthcheck run keystone" or check the output of "podman inspect keystone". The document has also been updated in the role manual. It requires at least Podman 1.6 where this patch has been tested. Depends-On: https://review.opendev.org/720089 Change-Id: I37508cd8243999389f9e17d5ea354529bb042279
8 lines
273 B
YAML
8 lines
273 B
YAML
---
|
|
features:
|
|
- |
|
|
Stop using systemd to manage container healthchecks and use native podman
|
|
healthchecks which are easier to consume than systemd.
|
|
The tripleo_container_manage role will take care of cleaning up the old
|
|
systemd healthchecks if they exist.
|