kayobe/ansible/logging.yml
Mark Goddard 6c54ce4d3b Introduce max fail percentage to playbooks
This allows us to continue execution until a certain proportion of hosts
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
kayobe_max_fail_percentage, and individual playbooks may define a max
failure percentage via <playbook>_max_fail_percentage.

Related Kolla Ansible patch:
https://review.opendev.org/c/openstack/kolla-ansible/+/805598

Change-Id: Ib81c72b63be5765cca664c38141ffc769640cf07
2024-06-03 16:24:29 +00:00

57 lines
1.4 KiB
YAML

---
- name: Ensure Logging configuration is applied
hosts: seed-hypervisor:seed:overcloud:infra-vms
max_fail_percentage: >-
{{ logging_max_fail_percentage |
default(host_configure_max_fail_percentage) |
default(kayobe_max_fail_percentage) |
default(100) }}
gather_facts: false
vars:
# NOTE(wszumski): Kayobe target env does not yet exist.
ansible_python_interpreter: /usr/bin/python3
tags:
- logging
tasks:
- name: Create /var/log/journal
become: true
file:
path: /var/log/journal
owner: "root"
group: "root"
mode: 0755
state: directory
notify: Flush journal to disk
when: journald_storage == "persistent"
- name: Ensure journald drop in directory exists
file:
path: "/etc/systemd/journald.conf.d/"
owner: "root"
group: "root"
mode: 0770
state: directory
become: true
- name: Ensure journald.conf overrides are set
copy:
content: |
[Journal]
Storage={{ journald_storage }}
dest: /etc/systemd/journald.conf.d/kayobe.conf
owner: root
group: root
mode: 0660
become: true
notify: Restart journald
handlers:
- name: Restart journald
service:
name: systemd-journald
state: restarted
become: true
- name: Flush journal to disk
become: true
command: journalctl --flush