Ilya Kharin f91ff40264 Restart mcollective on slave nodes after restore ... Also, on the backup step a status of `mco ping` is serialized in an upgrade tarball and on the restore step it is compared with the actual status. All nodes that are not respond are logged. In additional, the status of `mco ping` is archived on the backup step and is compared on the restore step with the actual ones. Change-Id: Ibba81102214998d83614a42cdb21c21bebd8284a Related-Bug: #1561092		2016-10-12 17:43:23 +03:00
..
backup_restore	Restart mcollective on slave nodes after restore	2016-10-12 17:43:23 +03:00
install	Move partition info transformation to extension	2016-08-24 21:30:12 +03:00
upgrade	Set forcefully upgrade_levels after deploy-changes	2016-09-21 15:34:50 +00:00
__init__.py	Change skipping of tasks	2016-08-19 15:55:02 +03:00