Minutes 2025-03-06

1. LUG Infrastructure By Allen Pham & Noah Holland! [1]
   1. Physical Hardware
      1. Lug shares a rack with ITO
      2. Shell right below the HARC server (google faceplate)
      3. More detailed locations of components in slideshow
   2. Proxmox Cluster
      1. 5 Nodes
      2. Runs virtual machines
      3. Hosts most of our services
         1. Wiki
         2. Website
         3. Infrastructure- Huskybot
      4. High availability
         1. the clustered infrastructure allows the virtual machines to keep services online instead of having one machine sink the whole boat
   3. Shell
      1. Pubnix / Multi-Tenant server
      2. Public webpages (shell.lug.mtu.edu)
      3. Runs Debian, 150GB per user
      4. Lug members get access for life (including alums)
      5. SSH (thanks IT)
   4. Mirrors
      1. Runs FreeBSD
      2. Salt >:(
      3. FreeBSD update borked salt
      4. Mirrors Debian, Arch, CentOS, gentoo, Fedora, Ubuntu, and More
      5. Plans to add Kali, Mint, PopOS, Alpine, FreeBSD
      6. Suggestions?
      7. Docs on the wiki: Docs/Mirrors
   5. Status (the LUG VPS)
      1. Racknerd
         1. Owner is kinda sketchy according to Reddit
         2. keeps exit scamming but its super cheap
         3. worth it just dont pay for years in advance
      2. Tinystatus
         1. Simple POSIX shell script that generates a static HTML status page
         2. Runs every five minutes
         3. I didn't like Uptime Kuma
            1. Way too bloated
            2. Would not run on our bottom-of-the-barrel VPS
            3. Difficult to firewall
   6. Standard Network Setup
      1. Lug uses a 10.10.0.0/16 for the internal Network
         1. 10.10.0.0/24 - Management (IDRAC, ILO, etc) - Generally Copper
         2. 10.10.1.0/24 - Local LAN
      2. public range = 141.219.180.64/27 (Not Being used? Allen?) GATEWAY!!!
   7. Wireguard VPN, Firewall rules, Subnet NAT
      1. pfSense firewalls LAN's
      2. Wireguard for accessing internal Infrastructure
   8. How we do K-Day
      1. Open Server running a live install
      2. Open HDD showing dd and block device seeking
      3. Fun TTY tricks
      4. Penguin Suit :( (David?)
2. mtu.social
   1. Lucas updates
      1. Everything is set up for Mastodon
   2. However...
      1. Bluesky?
      2. Less polished but might be more appealing than Mastodon
   3. How do we want to do sign-ups?
      1. Auto-allow mtu.edu sign-ups
      2. Manually fulfill requests from students that don't want their real identity out there
      3. Maybe open to general public via manual user creation?
      4. Lug doesn't have the resources to fight spambots
      5. Custom "verified" badges for verified MTU professor/students?
         1. Mastodon feature, not sure about Bluesky
      6. Server to host it on?
         1. Compute on Proxmox cluster, storage on 'Storage' server via NFS?