Docs/Proxmox Cluster: Difference between revisions

← Older edit

Docs/Proxmox Cluster (view source)

Revision as of 22:24, 10 October 2025

477 bytes removed , 10 October 2025

m

→‎Proxmox Nodes

D2wn

Bureaucrats, Interface administrators, Administrators

476

edits

Revision as of 20:29, 22 April 2025 (view source) D2wn (talk \| contribs) mNo edit summary Tag: Visual edit ← Older edit		Latest revision as of 22:24, 10 October 2025 (view source) D2wn (talk \| contribs) m (→‎Proxmox Nodes) Tag: Visual edit
(5 intermediate revisions by the same user not shown)
~~<small>~~[[~~Infrastructure~~Docs\|..<small>~/~~Infrastructure]]~~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 nodes in the cluster include: {\| class="wikitable" \|+Nodes ~~\|+IP Assignment~~ !IP !Node Name \|- \|10.10.1.21 \|Okabe'''''' \|- \|10.10.1.22 \|10.10.1.24 \|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]. == Virtual Machines == The VMs in the cluster include: {\| class="wikitable" \|+VMs [10.10.1.8] Huskybot IRC<->Matrix<->Discord bridge !IP * [10.10.1.9] LUG IRC Server (running ergo) !VM Name * [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.258 * [10.10.1.70] Socksproxy (so members using the split-tunneled LUG VPN have an easy way to route traffic through LUG) \|Huskybot * [10.10.1.76] debian (noah courseproject; will eventually delete) \|- * [10.10.1.170] hashtopolis (RedTeam Hashtopolis server for CTFs) \|10.10.1.9 * [10.10.1.172] badapple (parrot.live-like badapple service) \|LUG IRC Server * [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.15 * [10.10.1.224] Allen's Gaming VM (runs Windows) \|Homepage * [10.10.1.229] "Kube-Minecraft" (idk; ask Allen) \|- \|10.10.1.16 \|This MediaWiki instance \|- \|10.10.1.70 \|Socksproxy \|- \|10.10.1.76 \|noah courseproject \|- \|10.10.1.170 \|hashtopolis \|- \|10.10.1.172 \|badapple \|- \|10.10.1.202 \|Main-MC \|- \|10.10.1.212 \|[https://papermc.io/software/velocity Velocity] \|- \|10.10.1.224 \|Allen's Gaming VM \|- \|10.10.2.229 \|Kube-Minecraft ▲\|} You can see all VMs listed in the Proxmox WebUI. All IPs should be configured via DHCP on OPNsense and '''not assigned statically on the VM'''. == Updates == # (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.