Docs: Difference between revisions

Jump to navigation Jump to search
1,261 bytes removed ,  10 February
Updated services to include separate IRC headings for IRC server and IRC bouncer. Linked associated pages/stubs.
(added proxmox section)
(Updated services to include separate IRC headings for IRC server and IRC bouncer. Linked associated pages/stubs.)
 
(43 intermediate revisions by 3 users not shown)
This page is intendedthe as a 'hub' for all of LUGs internalLUG's documentation.
 
All of our documentation is intentionally public so that other student organizationsorgs (or individualsstudents) can replicate aspects of our infrastructure if they sowant. Everything sensitive (private keys, break-glass passwords, etc) should go in the LUG desireBitwarden.
 
Topics should generally be broken out into individual articles and linked on this page, unless there's a very small amount of content.
'''<br />If a topic requires a significant amount of content, you may want to break it out into a new article and link it on this page.'''
= Servers & Services =
 
== [[Docs/Infrastructure|Infrastructure]] ==
== Proxmox Cluster ==
General infrastructure notes
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).
 
=== Proxmox Nodes[[Docs/Plans|Plans]] ===
Pending upgrades/maintenance to our infrastructure
The nodes in the cluster include:
 
=== Network ===
* [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)
 
==== [[Docs/Cables|Cables]] ====
These are also listed in [[Servers]] since they're all physical servers in the GLRC rack.
Physical cabling and "layer 1" network config.
 
==== Virtual Machines[[Docs/Switches|Switches]] ====
Switch and layer 2 network configs (VLANs).
The VMs in the cluster include
 
=== Servers ===
* [10.10.1.2] PXEBoot server (inactive)
* [10.10.1.8] Huskybot IRC<->Matrix<->Discord bridge
* [10.10.1.9] LUG IRC Server (running ergo)
* [10.10.1.12] Invidious (private youtube frontend, currently inactive)
* [10.10.1.14] BookStack (alternative knowledgebase for documentation. Inactive, we're using this Wiki instead)
* [10.10.1.15] The lug.mtu.edu website and HTTP reverse-proxy for everything else behind NAT (running NGINX)
* [10.10.1.16] This Wiki
* [10.10.1.17] Netbox (network/rack-related documentation. Currently inactive, overly complicated for our needs)
* [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.71] VM for accessvillage.net (contact [[User:D2wn|Noah]] if any issues)
* [10.10.1.76] debian (noah courseproject; will eventually delete)
* [10.10.1.99] Noah's personal VM for random stuff
* [10.10.1.170] hashtopolis (RedTeam Hashtopolis server for CTFs)
* [10.10.1.172] badapple (parrot.live-like badapple service)
 
==== Updating Nodes[[Docs/Leskinen|Leskinen]] ====
Proxmox runs on top of Debian, so the updating process is the same.
 
The primary storage server.
# <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
 
Currently has Shell home directory backups and media for maho.
For the yearly major version bumps, you may need to run <code>apt update && apt upgrade</code>, followed by <code>apt dist-upgrade</code>
 
==== [[Docs/Maho|Maho]] ====
This is the process on Debian, but I haven't tested it on Proxmox yet.
The GPU compute server.
 
Currently hosts a [https://studio.blender.org/films/ Blender Open Studio Films] mirror via Jellyfin.
Check the [https://pve.proxmox.com/wiki/Category:Upgrade Proxmox wiki's 'Upgrade' category] for specific instructions when the time comes.
 
==== [[Docs/Mirrors|Mirrors]] ====
The Linux mirror server at mirrors.lug.mtu.edu
Mirrors is a standalone [https://www.dell.com/en-us/shop/povw/poweredge-r730xd/1000 Dell R730xd] server (3.5" drive bay variant) running FreeBSD, and all services are managed by salt.
 
==== [[Docs/OPNsense|OPNsense]] (Lasanga/Ravioli) ====
We're in the process of rebuilding it, but in the meantime this is what we've been doing to manage it thus far:
Router/Firewall and layer 3+ network configs.
 
==== [[Docs/Proxmox Cluster|Proxmox Cluster]] ====
Our Proxmox cluster running the majority of our services
 
==== [[Docs/Shell|Shell]] ====
The shared multi-tenant server for LUG members/alums at [https://shell.lug.mtu.edu/ shell.lug.mtu.edu]
 
= Servers &== Services ===
Certificate maintenance:
 
==== BlueSky ====
put it in /usr/share/salt/<somewhere> where salt will copy it to /etc/nginx/<somewhere>
 
==== [[Docs/IRC Server|IRC Server]] ====
 
==== Shell[[IRC Bouncer]] ====
 
==== Firewall/RouterWebsite ====
 
==== FileserverWiki ====
Coming Soon, currently unprovisioned (waiting on new PSU and drives to arrive)
 
== Org Management ==
 
=== Time-sensitiveWiki ===
Email IT for new certs (example template to use, make sure to keep SubjectAltName, etc)
 
==== Docs ====
Install-a-thons
How to create/manage pages in this category ("Docs").
 
==== Meeting Minutes ====
shirt printing
Notes are taken during the meetings.
 
There are no specific guidelines, but usually minutes are kept to a series of bullet points, with some elaboration in sub-bullets.
== Budget ==
USG meetings
 
These notes can be written in whatever markup format is preferred, but must be converted to MediaWiki to be pasted onto the wiki. [https://pandoc.org/ Pandoc] can do this for the majority of formats (Markdown, Vimwiki, ODT, etc.)
making presentable diagrams and representations of data
 
=== Time-sensitive ===
 
* Email IT for new certs (example template to use, make sure to keep SubjectAltName, etc)
* Install-a-thons
* Shirt printing / stickers
 
=== Budget ===
 
* USG meetings
making* Making presentable diagrams and representations of data
 
=== MTU Policies and Procedures ===
https://www.mtu.edu/umc/services/websites/requirements/
 
All (sub)domains need to be approved by UMC (University Marketing & Communication)
 
IT handles IP addressing and SSL certificates
 
USG handles funding and reimbursements
38

edits

Navigation menu