Ilya Kharin 12daa0e54f 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 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 Closes-Bug: #1561092		2016-10-13 14:33:42 +03:00
..
bin	Change check on host_evacuation	2016-05-13 13:12:31 +00:00
commands	Apply network templates before preupgrade handler	2016-05-27 22:56:22 +00:00
fuelclient	Add clone ips feature to install nodes	2015-09-08 15:38:30 +03:00
handlers	Restart mcollective on slave nodes after restore	2016-10-13 14:33:42 +03:00
helpers	Remove fix for custom field in release metadata	2016-05-13 10:52:12 +00:00
patches	Stop update of volume metadata gracefully if 'os' volume is not on LVM	2016-05-13 12:49:43 +00:00
tests	Restart mcollective on slave nodes after restore	2016-10-13 14:33:42 +03:00
util	Restart mcollective on slave nodes after restore	2016-10-13 14:33:42 +03:00
__init__.py	Cleanup after cookiecutter	2015-07-15 12:23:13 +03:00
app.py	Set default log_file	2015-09-09 17:21:24 +03:00
log.py	Colorize output on tty only	2016-09-07 10:07:20 +00:00
magic_consts.py	Check that astute.yaml password is valid before backup	2016-09-20 17:03:21 +03:00