Tag: Branch: Tree: 10087b5c58

feature/softwareraid

main

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '10087b5c58'

${ noResults }

Commit Graph

1 Commits (10087b5c587fc3e5f8f083825dfad308a80cfdc1)

Author	SHA1	Message	Date
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. ... * Updated Server->shutdown_virsh() to work without a database connection. * Updated System->reboot_needed() to store/read from a cache file when the database is not available. * Updated anvil-safe-start to remove the old --enable/disable/status switches, now that we use anvil-safe-start.service systemd unit. * Reworked anvil-safe-stop to work without a database connection, and to work on DR hosts. * Updated anvil-special-operations to add new tasks, but it's likely these new tasks aren't needed and will be removed very shortly. * Added/updated multiple man pages. Signed-off-by: digimer <mkelly@alteeve.ca>	1 year ago