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
..
__init__.py	Restart mcollective on slave nodes after restore	2016-10-12 17:43:23 +03:00
admin_networks.py	Fix the backup of network node group data	2016-09-21 18:40:45 +03:00
astute.py	Fix validation of astute.yaml before backup	2016-09-16 12:12:13 +03:00
base.py	Raise NotImplementedError in the base archivator	2016-08-22 00:05:42 +03:00
cobbler.py	Use ubuntu_bootstrap for old systems	2016-08-16 11:48:28 +03:00
fuel_keys.py	Add fuel admin node backup tool	2016-01-22 17:06:12 +03:00
fuel_uuid.py	Add fuel admin node backup tool	2016-01-22 17:06:12 +03:00
logs.py	Remove docker related code from LogsArchivator	2016-06-17 16:18:23 +03:00
mcollective.py	Restart mcollective on slave nodes after restore	2016-10-12 17:43:23 +03:00
mirrors.py	Replace SQL SELECTs with API calls	2016-08-16 18:09:59 +03:00
nailgun_plugins.py	Send credentials as environment variables to subprocess	2016-03-18 17:20:56 +03:00
postgres.py	Check that astute.yaml password is valid before backup	2016-09-12 14:01:10 +03:00
puppet.py	Check that astute.yaml password is valid before backup	2016-09-12 14:01:10 +03:00
release.py	Clean imports in code	2016-09-07 11:46:45 +07:00
ssh.py	Add `stderr_log_level` parameter to popen	2016-07-29 14:24:35 +00:00
version.py	Add fuel admin node backup tool	2016-01-22 17:06:12 +03:00