From af6e1ca4fd3366c1ae936d225b2835e95a4191fc Mon Sep 17 00:00:00 2001 From: Mark Goddard Date: Mon, 16 Aug 2021 17:03:22 +0100 Subject: Support Ansible max_fail_percentage 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 _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 --- etc/kolla/globals.yml | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'etc') diff --git a/etc/kolla/globals.yml b/etc/kolla/globals.yml index 92d1d7147..3429c2c0e 100644 --- a/etc/kolla/globals.yml +++ b/etc/kolla/globals.yml @@ -32,6 +32,12 @@ workaround_ansible_issue_8743: yes # scenarios with all facts cached (as there is no task to fail). #kolla_ansible_setup_any_errors_fatal: false +# This variable may be used to set the maxiumum failure percentage for all +# plays. More fine-grained control is possible via per-service variables, e.g. +# nova_max_fail_percentage. The default behaviour is to set a max fail +# percentage of 100, which is equivalent to not setting it. +#kolla_max_fail_percentage: + ############### # Kolla options ############### -- cgit v1.2.3