Striker-update-cluster - Revision history

Digimer at 03:42, 16 August 2024

2024-08-16T03:42:29Z

← Older revision		Revision as of 03:42, 16 August 2024
Line 14:		Line 14:

	; '''Note:'''		; '''Note:'''
	: This program requires all machines be online, and Anvil! nodes being paired and ~~sync'ed~~. When nodes are updated, the inactive subnode will be removed from the node, updated, rebooted if necessary, and then rejoined to the node. Then hosted servers will migrate to the now-updated subnode, and the process repeated for the other subnode. Anvil! nodes are updated sequentially, so the process can take some time to complete, but should not require a maintenance window.		: This program requires all machines to be online, and Anvil! nodes being paired and synced. When nodes are updated, the inactive subnode will be removed from the node, updated, rebooted if necessary, and then rejoined to the node. Then hosted servers will migrate to the now-updated subnode, and the process repeated for the other subnode. Anvil! nodes are updated sequentially, so the process can take some time to complete, but should not require a maintenance window.
	: The upgrade process will live-migrate all hosted servers! If any hosted server is either under heavy load, or the replication link (the BCN or MN) is relatively lower bandwidth, this could cause performance concerns. As such, it's ideal to run the upgrades at a time less sensitive to performance impacts.		: The upgrade process will live-migrate all hosted servers! If any hosted server is either under heavy load, or the replication link (the BCN or MN) is relatively lower bandwidth, this could cause performance concerns. As such, it's ideal to run the upgrades at a time less sensitive to performance impacts.

Line 26:		Line 26:
	: Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.		: Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.

	== Commands: ==		== Commands ==

	;'''--clear-cache'''		;'''--clear-cache'''
Line 35:		Line 35:
	: Automatically continue with the upgrade without prompting for confirmation.		: Automatically continue with the upgrade without prompting for confirmation.
	; '''--no-reboot'''		; '''--no-reboot'''
	: If the kernel is updated on a remote system, the system will normally be rebooted. This switch prevents the reboot from ~~occuring~~.		: If the kernel is updated on a remote system, the system will normally be rebooted. This switch prevents the reboot from occurring.
	; '''--reboot-self'''		; '''--reboot-self'''
	: By default, if the ~~kenrel~~ on the local system is updated, and so a reboot is needed, a message is printed but the local system is NOT rebooted. This switch will instead cause this host to reboot at the end of the cluster update.		: By default, if the kernel on the local system is updated, and so a reboot is needed, a message is printed but the local system is NOT rebooted. This switch will instead cause this host to reboot at the end of the cluster update.
	: See '''--reboot''' for rebooting if anything is updated.		: See '''--reboot''' for rebooting if anything is updated.
	; '''--reboot'''		; '''--reboot'''

Digimer: /* OPTIONS */

2024-07-31T23:54:49Z

OPTIONS

← Older revision		Revision as of 23:54, 31 July 2024
Line 19:		Line 19:
	= OPTIONS =		= OPTIONS =

	-?, -h, '''--help''' Show this man page.		;-?, -h, '''--help'''
			:Show this man page.
	; '''--log-secure'''		; '''--log-secure'''
	: When logging, record sensitive data, like passwords.		: When logging, record sensitive data, like passwords.
Line 44:		Line 44:
	; '''--timeout''' <seconds, Nm, Nh>		; '''--timeout''' <seconds, Nm, Nh>
	: When given, if a system update doesn't complete in this amount of time, error out and abort the update. This timeout is used when waiting for actions like waiting for a machine to update, reboot, join a subcluster, and so forth.		: When given, if a system update doesn't complete in this amount of time, error out and abort the update. This timeout is used when waiting for actions like waiting for a machine to update, reboot, join a subcluster, and so forth.
	: If this is set to an integer, it is treated as a number of seconds. If this ends in 'm' or 'h', then the preceding number is treated as a number of minutes or hours, respectively. By default, updates will wait for 24 hours.		: If this is set to an integer, it is treated as a number of seconds. If this ends in 'm' or 'h', then the preceding number is treated as a number of minutes or hours, respectively. By default, updates will wait for 24 hours.

	= AUTHOR =		= AUTHOR =

Digimer: Created page with "{{man_header}} = NAME = striker-update-cluster - This program updates all physical machines in an Anvil! cluster = SYNOPSIS = '''striker-update-cluster''' ''<command> ''[''options''] = DESCRIPTION = This program sequentially updates Striker dashboards, DR hosts and Anvil! nodes (the paired sub-nodes). It does this without needing to take hosted servers offline. ; '''Note:''' : This program requires all machines be online, and Anvil! nodes being paired and sy..."

2024-07-31T23:47:45Z

Created page with "{{man_header}} = NAME = striker-update-cluster - This program updates all physical machines in an Anvil! cluster = SYNOPSIS = '''striker-update-cluster''' ''<command> ''[''options''] = DESCRIPTION = This program sequentially updates Striker dashboards, DR hosts and Anvil! nodes (the paired sub-nodes). It does this without needing to take hosted servers offline. ; '''Note:''' : This program requires all machines be online, and Anvil! nodes being paired and sy..."

Páàjì titun

{{man_header}}

= NAME =

striker-update-cluster - This program updates all physical machines in an Anvil! cluster

= SYNOPSIS =

'''striker-update-cluster''' ''<command> ''[''options'']

= DESCRIPTION =

This program sequentially updates Striker dashboards, DR hosts and Anvil! nodes (the paired sub-nodes). It does this without needing to take hosted servers offline.

; '''Note:'''
: This program requires all machines be online, and Anvil! nodes being paired and sync'ed. When nodes are updated, the inactive subnode will be removed from the node, updated, rebooted if necessary, and then rejoined to the node. Then hosted servers will migrate to the now-updated subnode, and the process repeated for the other subnode. Anvil! nodes are updated sequentially, so the process can take some time to complete, but should not require a maintenance window.
: The upgrade process will live-migrate all hosted servers! If any hosted server is either under heavy load, or the replication link (the BCN or MN) is relatively lower bandwidth, this could cause performance concerns. As such, it's ideal to run the upgrades at a time less sensitive to performance impacts.

= OPTIONS =

-?, -h, '''--help''' Show this man page.

; '''--log-secure'''
: When logging, record sensitive data, like passwords.
; -v, -vv, -vvv
: Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.

== Commands: ==

;'''--clear-cache'''
: This will force the dnf cache to be cleared before the OS update is started. This slows the update down a bit, but ensures the latest updates are installed.
; '''--force'''
: If any Striker dashboards or DR hosts are unavailable, or if an entire node (paired subnodes) is offline, this switch will allow you to force the upgrade attempt.
; '''-y''', '''--yes'''
: Automatically continue with the upgrade without prompting for confirmation.
; '''--no-reboot'''
: If the kernel is updated on a remote system, the system will normally be rebooted. This switch prevents the reboot from occuring.
; '''--reboot-self'''
: By default, if the kenrel on the local system is updated, and so a reboot is needed, a message is printed but the local system is NOT rebooted. This switch will instead cause this host to reboot at the end of the cluster update.
: See '''--reboot''' for rebooting if anything is updated.
; '''--reboot'''
: Normally, the system will only reboot if the kernel is updated. If this is used, and if any packages are updated, then a reboot will be performed. This is recommended in most cases.
: Must be used with '''--reboot-self''' to reboot the local system. Otherwise, it is passed along to target machines via their anvil-update-system calls.
; '''--timeout''' <seconds, Nm, Nh>
: When given, if a system update doesn't complete in this amount of time, error out and abort the update. This timeout is used when waiting for actions like waiting for a machine to update, reboot, join a subcluster, and so forth.
: If this is set to an integer, it is treated as a number of seconds. If this ends in 'm' or 'h', then the preceding number is treated as a number of minutes or hours, respectively. By default, updates will wait for 24 hours.

= AUTHOR =

Written by Madison Kelly, Alteeve staff and the Anvil! project contributors.

= REPORTING BUGS =

Report bugs to users@clusterlabs.org

{{footer}}