User contributions for Digimer

06:0506:05, 19 September 2024 diff hist +3,203‎ N Storage Groups ‎ Created page with "{{howto_header}} In an Anvil! cluster, a "''storage group''" is a logical group of LVM Volume Groups. When a server is created, the selected storage group tells the cluster where to pull the physical storage from to create the server's virtual hard drive. Most Anvil! nodes have only one VG per subnode and they are generally the same size. As such, the Anvil! is able to automatically link them into a storage group automatically. = Multi-VG Example = Consider a..."
05:5105:51, 19 September 2024 diff hist +35‎ N M2 ‎ Redirected page to AN!Cluster Tutorial 2 current Tag: New redirect
05:5105:51, 19 September 2024 diff hist +20‎ N Logical Volume ‎ Redirected page to LVM#LV current Tag: New redirect
05:5005:50, 19 September 2024 diff hist +20‎ N Physical Volume ‎ Redirected page to LVM#PV current Tag: New redirect
05:5005:50, 19 September 2024 diff hist +20‎ N Volume Groups ‎ Redirected page to LVM#VG current Tag: New redirect
05:0205:02, 19 September 2024 diff hist +138‎ Build an M3 Anvil! Cluster - v3.1 ‎ →‎Disaster Recovery (DR) Host
00:2000:20, 19 September 2024 diff hist +43‎ Build an M3 Anvil! Cluster - v3.1 ‎ →‎Administrative Tasks
00:2000:20, 19 September 2024 diff hist +2,266‎ N Configuring a Disaster Recovery Host ‎ Created page with "{{howto_header}} A Disaster Recovery host, aka "DR Host", is a physical server that is installed in a physically different location from the production Anvil! cluster. The purpose of the DR host is to provide a fall-back location to run servers should the production cluster suffer a catastrophic failure. Consider failure scenarios like; * Accidental fire suppression discharge * Transformer failure feeding the data-center * Localized fire in the cluster location In su..."

02:4102:41, 12 September 2024 diff hist +1,018‎ Striker-boot-machine ‎ →‎Commands:

04:1604:16, 31 August 2024 diff hist +466‎ Striker-manage-peers ‎ →‎Commands: current

15:5215:52, 30 August 2024 diff hist +36‎ N File:An-striker01-rhel9-m3-updating ssh 05.png ‎ No remaining bad keys. current
15:5215:52, 30 August 2024 diff hist 0‎ Upgrading the Base OS in an M3 Anvil! Cluster ‎ →‎Updating SSH Host Key
15:5115:51, 30 August 2024 diff hist +1,214‎ Upgrading the Base OS in an M3 Anvil! Cluster ‎ →‎Base OS Install
15:4915:49, 30 August 2024 diff hist +54‎ N File:An-striker01-rhel9-m3-updating ssh 04.png ‎ Confirm that you want to delete the key. current
15:4715:47, 30 August 2024 diff hist +55‎ N File:An-striker01-rhel9-m3-updating ssh 03.png ‎ Check to select the old key(s) to delete. current
15:4615:46, 30 August 2024 diff hist +59‎ N File:An-striker01-rhel9-m3-updating ssh 02.png ‎ Expand the "Manage changed SSH keys" toolbox. current
15:4015:40, 30 August 2024 diff hist +35‎ N File:An-striker01-rhel9-m3-updating ssh 01.png ‎ Go to Striker config. current
02:5202:52, 30 August 2024 diff hist +300‎ Upgrading the Base OS in an M3 Anvil! Cluster ‎ →‎Rebuilding Machines

04:5204:52, 29 August 2024 diff hist +850‎ N Scan agent ‎ Created page with "{{howto_header}} In Scancore, "scan agents" are the individual programs that know how to interact with the thing being monitored and managed by that specific agent. They act as a go-between, knowing how to collect and process data, and how to store it in a way that the main Scancore process can use. Taking one example, <span class="code">scan-apc-ups</span> is the scan agent for APC-branded UPSes. This example agent know how to collect data from the UPSes..." current