Docs/Proxmox Cluster - Revision history

D2wn: /* Proxmox Nodes */

2025-10-10T22:24:55Z

Proxmox Nodes

← Older revision		Revision as of 22:24, 10 October 2025
Line 16:		Line 16:
	\|-		\|-
	\|10.10.1.21		\|10.10.1.21
	\|Okabe'''**'''		\|Okabe'''*'''
	\|-		\|-
	\|10.10.1.22		\|10.10.1.22
Line 26:		Line 26:
	\|10.10.1.24		\|10.10.1.24
	\|Mayuri		\|Mayuri
		⚫	\|}'''*''' = currently offline; was running Windows 10 LTSC temporarily to poke around with [[Locked HGST drives\|HGST Drives]]
	\|-
	\|10.10.1.25
	\|MrBraun'''*'''
	\|}
	'''*''' = HP Server

⚫	'''**''' = currently offline; running Windows 10 LTSC temporarily to poke around with [[Locked HGST drives\|HGST Drives]]

	Note that all these addresses are static, and must be changed manually on each host (Proxmox doesn't currently support DHCP). The process is loosely outlined by the comments [https://forum.proxmox.com/threads/proxmox-change-ip-address.145254/ here].		Note that all these addresses are static, and must be changed manually on each host (Proxmox doesn't currently support DHCP). The process is loosely outlined by the comments [https://forum.proxmox.com/threads/proxmox-change-ip-address.145254/ here].

D2wn at 07:42, 23 April 2025

2025-04-23T07:42:10Z

← Older revision		Revision as of 07:42, 23 April 2025
Line 1:		Line 1:
	~~<small>~~[[~~Infrastructure~~\|~/~~Infrastructure]]~~</small>		[[Docs\|<small>~/Docs</small>]]

	The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).		The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).

D2wn: D2wn moved page Infrastructure/Proxmox Cluster to Docs/Proxmox Cluster

2025-04-23T07:39:32Z

D2wn moved page Infrastructure/Proxmox Cluster to Docs/Proxmox Cluster

← Older revision

Revision as of 07:39, 23 April 2025

D2wn at 21:06, 22 April 2025

2025-04-22T21:06:13Z

← Older revision		Revision as of 21:06, 22 April 2025
Line 1:		Line 1:
	<small>[[Infrastructure\|../Infrastructure]]</small>		<small>[[Infrastructure\|~/Infrastructure]]</small>

	The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).		The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).

D2wn: /* Virtual Machines */

2025-04-22T20:38:22Z

Virtual Machines

@@ Line 8: / Line 8: @@
 The nodes in the cluster include:
 {| class="wikitable"
 !IP
 !Node Name
@@ Line 40: / Line 40: @@
 == Virtual Machines ==
 The VMs in the cluster include:
 You can see all VMs listed in the Proxmox WebUI.
 == Updates ==

D2wn: /* Updating Nodes */

2025-04-22T20:31:17Z

Updating Nodes

← Older revision		Revision as of 20:31, 22 April 2025
Line 64:		Line 64:
	# (Optional) Manually migrate all VMs to other Proxmox nodes first; Proxmox doesn't do this automatically and all the VMs running on the host when it reboots will go offline until the host comes back up		# (Optional) Manually migrate all VMs to other Proxmox nodes first; Proxmox doesn't do this automatically and all the VMs running on the host when it reboots will go offline until the host comes back up
	# (Optional but recommended) <code>reboot</code> the node		# (Optional but recommended) <code>reboot</code> the node


	For the yearly major version bumps, you may need to run <code>apt update && apt upgrade</code>, followed by <code>apt dist-upgrade</code>; This is the process on Debian, but I haven't tested it on Proxmox.		For the yearly major version bumps, you may need to run <code>apt update && apt upgrade</code>, followed by <code>apt dist-upgrade</code>; This is the process on Debian, but I haven't tested it on Proxmox.

D2wn at 20:29, 22 April 2025

2025-04-22T20:29:43Z

← Older revision		Revision as of 20:29, 22 April 2025
Line 1:		Line 1:
			<small>[[Infrastructure\|../Infrastructure]]</small>

	The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).		The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).

D2wn at 20:29, 22 April 2025

2025-04-22T20:29:01Z

@@ Line 3: / Line 3: @@
 In the panel for each VM in the webUI, make sure to enable the guest agent; Debian will auto install the QEMU guest agent on first install when it detects being run inside a VM.
-=== Proxmox Nodes ===
+== Proxmox Nodes ==
 The nodes in the cluster include:
 Note that all these addresses are static, and must be changed manually on each host (Proxmox doesn't currently support DHCP). The process is loosely outlined by the comments [https://forum.proxmox.com/threads/proxmox-change-ip-address.145254/ here].
 These are also listed in [[Servers]] since they're all physical servers in the GLRC rack.
-=== Virtual Machines ===
+== Virtual Machines ==
 The VMs in the cluster include:
@@ Line 32: / Line 52: @@
 * [10.10.1.229] "Kube-Minecraft" (idk; ask Allen)
 You can see all VMs listed in the Proxmox WebUI.
 === Updating Nodes ===

D2wn: Created page with "The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down). In the panel for each VM in the webUI, make sure to enable the guest agent; Debian will auto install the QEMU guest agent on first install when it detects being run inside a VM. === Proxmox Nodes === The nodes in the cluster include: * [10.10.1.20] Kur..."

2025-04-22T20:26:14Z

Created page with "The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down). In the panel for each VM in the webUI, make sure to enable the guest agent; Debian will auto install the QEMU guest agent on first install when it detects being run inside a VM. === Proxmox Nodes === The nodes in the cluster include: * [10.10.1.20] Kur..."

New page

The majority of our infrastructure are VMs in the Proxmox cluster, so everything can be [https://en.wikipedia.org/wiki/High_availability highly-available] (meaning VMs can jump to another Proxmox node if one goes down).

In the panel for each VM in the webUI, make sure to enable the guest agent; Debian will auto install the QEMU guest agent on first install when it detects being run inside a VM.

=== Proxmox Nodes ===
The nodes in the cluster include:

* [10.10.1.20] Kurisu
* [10.10.1.21] Okabe (currently offline; running Windows 10 LTSC temporarily to poke around with [[Locked HGST drives|HGST Drives]])
* [10.10.1.22] Daru
* [10.10.1.23] Luka
* [10.10.1.24] Mayuri
* [10.10.1.25] MrBraun (HP Server)
Note that all these addresses are static, and must be changed manually on each host (Proxmox doesn't currently support DHCP). The process is loosely outlined by the comments [https://forum.proxmox.com/threads/proxmox-change-ip-address.145254/ here].

These are also listed in [[Servers]] since they're all physical servers in the GLRC rack.

=== Virtual Machines ===
The VMs in the cluster include:

* [10.10.1.8] Huskybot IRC<->Matrix<->Discord bridge
* [10.10.1.9] LUG IRC Server (running ergo)
* [10.10.1.15] webserver running NGINX, hosts the lug.mtu.edu homepage and servers as a reverse-proxy for all other webservers behind our NAT.
* [10.10.1.16] This mediawiki instance
* [10.10.1.70] Socksproxy (so members using the split-tunneled LUG VPN have an easy way to route traffic through LUG)
* [10.10.1.76] debian (noah courseproject; will eventually delete)
* [10.10.1.170] hashtopolis (RedTeam Hashtopolis server for CTFs)
* [10.10.1.172] badapple (parrot.live-like badapple service)
* [10.10.1.202] "Main-MC" (idk; ask Allen)
* [10.10.1.212] [https://papermc.io/software/velocity Velocity] reverse-proxy for Minecraft servers (so we can offer unlimited servers to clubs/halls on campus without running out of public IPs)
* [10.10.1.224] Allen's Gaming VM (runs Windows)
* [10.10.1.229] "Kube-Minecraft" (idk; ask Allen)
You can see all VMs listed in the Proxmox WebUI.

=== Updating Nodes ===
Proxmox runs on top of Debian, so the updating process is the mostly same.

# <code>apt update && apt upgrade</code>
# (Optional) Remove the annoying unlicensed popup from web dashboard: <code>sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.service</code>
# (Optional) Manually migrate all VMs to other Proxmox nodes first; Proxmox doesn't do this automatically and all the VMs running on the host when it reboots will go offline until the host comes back up
# (Optional but recommended) <code>reboot</code> the node

For the yearly major version bumps, you may need to run <code>apt update && apt upgrade</code>, followed by <code>apt dist-upgrade</code>; This is the process on Debian, but I haven't tested it on Proxmox.

Check the [https://pve.proxmox.com/wiki/Category:Upgrade Proxmox wiki's 'Upgrade' category] for specific instructions when the time comes.

=== Updating VMs ===
All VMs run Debian to keep things homogenous and easy to upgrade/automate, except a few Windows VMs like Allen's scuffed Win10 LTSC gaming VM; Those are presumed self-managed.

The update process is the same as any Debian system:

# <code>apt update && apt upgrade</code>
## If the kernel or systemd get updated, it's a good idea to <code>reboot</code>
# For major version bumps (I think there's one each year?), you need to run the aforementioned <code>apt update && apt upgrade</code>, followed by <code>apt dist-upgrade</code>

Updates need to be automated with [https://docs.ansible.com/ Ansible] at some point.