9 Commits (99dc4ba6ba5c13af72554a70aa7d2d1ccdbd6bbd)

Author SHA1 Message Date
digimer 01b714f3b3 Fixed typo from issue #369. 1 year ago
digimer 7bd76c10dc Major thing in this commit is reworking striker-update-cluster to work without expecting anvil-daemon to be running on target machines. Similarly, they had to be able to work when the Striker DBs were not available. This is to account for cases where the Striker dashboards have updated, and the schema has changed, preventing the not-yet-updated DR hosts and subnodes from being able to use the DB. To do this, anvil-safe-stop, anvil-update-system, and anvil-shutdown-server had to be updated to use the new --no-db switch, which tells then to run without the database being available. 1 year ago
digimer 9bc78860a6 * Updated anvil-update-system to detect kmod-drbd upgrade problems and fix them. 1 year ago
digimer f262da544d Removed '--best --allowerasing' from dnf update. 1 year ago
digimer d741f4aa6f * Updated anvil-daemon to not exit on high RAM use is any job is running. 1 year ago
digimer 751687129a * Updated anvil-daemon to not exit on RAM use if anvil-update-system is running. 1 year ago
digimer 02c3d204ea * Updated anvil-update-system to set 'job_data' to track reboots, and striker-update-cluster to read it. 1 year ago
digimer 3016fb875b * Reworded striker-update-cluster to use anvil-update-system for on-system OS updates. 1 year ago
digimer d56b7f9a84 * Created (but not finished!) the new striker-update-cluster tool. 1 year ago