Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1 2026-03-19T12:17:03+00:00 2026-03-19T12:17:03+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-12-12T08:37:56+00:00 urn:sha1:21013949cdae545dbb797d149d7e4bcfa1378ea7 Also add all failed roles into ignore and these will be removed in subsequent patches Change-Id: Ifa6f2725cfa93cb14d72daf27448bd58f186acfd Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2025-12-09T22:13:16+00:00 Bertrand Lanson bertrand.lanson@protonmail.com 2025-12-09T22:12:25+00:00 urn:sha1:0cc4a041b92be785e7d2ad123101a04d956ef979 fix unnamed-task rule violation Change-Id: Ib0527af1fe92b2640564b4f26d0d8a3172bd910d Signed-off-by: Bertrand Lanson <bertrand.lanson@protonmail.com> 2025-12-05T06:07:50+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-12-04T15:41:20+00:00 urn:sha1:04defb5e5d0cd7984d9a57a18e7e903bd897c9f2 Change-Id: I82310a2ebfa326a01424c7469d4eb9d440dc9b9c Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2023-12-05T10:49:42+00:00 Mark Goddard mark@stackhpc.com 2021-08-16T16:03:22+00:00 urn:sha1:af6e1ca4fd3366c1ae936d225b2835e95a4191fc 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 2022-03-21T11:54:54+00:00 Mark Goddard mark@stackhpc.com 2022-02-14T11:56:50+00:00 urn:sha1:80b311bef73ee8469055ae6f0b6083991a61b02a Change Ia1239069ccee39416b20959cbabad962c56693cf added support for running a libvirt daemon on the host, rather than using the nova_libvirt container. It did not cover migration of existing hosts from using a container to using a host daemon. This change adds a kolla-ansible nova-libvirt-cleanup command which may be used to clean up the nova_libvirt container, volumes and related items on hosts, once it has been disabled. The playbook assumes that compute hosts have been emptied of VMs before it runs. A future extension could support migration of existing VMs, but this is currently out of scope. Change-Id: I46854ed7eaf1d5b5e3ccd8531c963427848bdc99