Jiri Stransky bcd6cde608 Introduce proper steps to external update/upgrade tasks ... So far the tasks for external update/upgrade were not using the step mechanism as other tasks, we had a single step. As external deploy/update/upgrade tasks are being used for more things nowadays, it's likely that we'll need to go towards a similar model like we have for deploy/update/upgrade tasks -- proper usage of steps. For now we have just 2: * Step 0 for setting global facts, and performing validations. * Step 1 for actual update/upgrade tasks. (There's an upcoming change to run online data migrations in step 1). Change-Id: I1933bd0eedab71caab56c0e5d93ba7927fb7c20f Partial-Bug: #1793332		2018-10-04 12:08:21 +02:00
..
all_nodes	Change template names to rocky	2018-05-09 08:28:42 +02:00
nova_metadata	Merge "Revert "Switch public endpoints to use FQDNs by default""	2018-05-17 21:56:29 +00:00
post_deploy	undercloud/stackrc: unset OS_* variables	2018-09-20 15:48:05 +00:00
pre_deploy	Undercloud - Restart keepalived on update	2018-09-24 21:02:34 +00:00
pre_network	Merge "Avoid ifcfg files modification when a reboot is not required"	2018-08-13 10:09:16 +00:00
services	Introduce proper steps to external update/upgrade tasks	2018-10-04 12:08:21 +02:00
tasks	IHA Default the compute endpoint check script to internal	2018-08-23 12:14:40 +02:00