Project Bringing Sexy Back
Note: This page does not reflect current infrastructure. It is for planning purposes.
This is an effort toward the end of Fall 2017 and early Spring 2018 to get new hardware, determining if we can use old hardware for anything, bring many vtluug services back to life plus add new services, fix major problems relating to the current infrastructure, make managing the current infrastructure easier, and to provide enough documentation so that anybody can have a very good understanding of how everything works without having to ask the officers about every little thing. This will be summarized at https://vtluug.org/rtfm.txt
One major change is running an Proxmox cluster to managing everything, along with offering a VPS service in addition to shell accounts on Acidburn. This is not possible with the current hardware.
Contents
Getting new hardware
Cyberdelia is the only connected physical machine right now, besides our router. See Infrastructure 2017. We are planning to request funding from the SBB for new infrastructure as early as possible Spring 2018.
We are still working on exactly what to ask for, but here are some desirable things: //TODO link items
Priority | Item | Estimated Cost |
---|---|---|
10 | Dell Poweredge R620s | $600 ish |
Ideally we will get 2. A much more detailed price analysis will be done for the SBB.
\o/ We got $1300 to get 2 R620s!!
Hardware Configuration
Hardware
- temp88191
- Cyberdelia
- Wood
- 2x SGI (Phantomphreak/Joey)
- 2x R620s (Meltdown/Spectre)
Configuration
- Router/DNS Server: joey (sry temp88191 is too old)
- NAS: Cyberdelia due to its HDD capacity
- Proxmox hosted-engine: Both R620s, Phantomphreak
- HPC: Wood due to its 4U height that can easily fit gpus
Diagrams in progress
Networking
See Infrastructure:Network for a mostly up to date networking layout.
Public IPv4s are the same except for a few, the local IPv4 network is different, and IPv6 is completely different because we have a prefix.
Public IPv4 addresses
Function | DNS | IP |
---|---|---|
Router/DNS | joey.vtluug.org | 128.173.88.191 |
"Main" Proxmox Node | meltdown.vtluug.org | 128.173.89.244 |
Web/Proxy server | sczi.vtluug.org | 128.173.88.78 |
Shell Server | acidburn.vtluug.org | 128.173.89.245 |
FreeIPA | zerocool.vtluug.org | 128.173.89.247 |
Mirror | mirror.vtluug.org | 128.173.89.246 |
Matt's server | mjh.ece.vt.edu | 128.173.88.104 |
As per echarlie, "check rdns. if there isn't an entry, and it's in ece's allocated block, we can use it."
Service Importance
Note: This section's PoV does not taking into account the current state of service. Instead, it assumes services are being installed to a new infrastructure.
Syntax:
- Host (hostname)
- Services running on host
Essential
Bare Metal
- Routing (joey)
- DNS (joey)
- Firewall (joey)
- NAS ("new" dell 2900 - dirtycow, dell 2900 - cyberdelia, r310 - fallout)
- Proxmox VE (meltdown,spectre,phantomphreak)
VMs
- FreeIPA (chimera)
- Sczi (sczi)
- vtluug.org
- wiki.vtluug.org
- hokieprivacy.org
- linx.vtluug.org + linx.li
- bash.vtluug.org
- pSQL
Very Important
Bare Metal
- VPS system via Proxmox
- Somewhat automated system where a user is given a VM
- Give each user an ipv6 address
- NAS Backup
VMs
- Shell (acidburn)
- Wadsworth
- duckhunter9000
- multimediamanv2
- Produces /files/irc-vtluug.org
- Member pages @ vtluug.org/~user
- rsyslog (theplague)
- Need to research this a bunch
- jitsi.vtluug.org (jitsi)
- Proxy through sczi
- emby.vtluug.org (emby)
- Proxy through sczi
Important
VMs
- mirror.vtluug.org (mirror)
- syncthing discovery server (sync)
- Tahoe-LAFS (crashoverride)
- telnet BBS
- How tf do these things work
- wargame.vtluug.org (wargame)
- Archive Team Warrior
- map.vtluug.org (map)
Other things to consider
- diaspora*
- finger (kerberos-based)
- talkd
Migration
VTLUUG Site
- Setup on sczi via the web ansible role
VTLUUG & Gobblerpedia wiki
- Backup content using dumpBackup.xml script
- Setup on sczi via the web ansible role
- Restore content to new wiki
Wadsworth/phenny
- Setup on acidburn via the small-services ansible role
VTBash
- Setup on sczi via the web ansible role
Hokieprivacy
- Setup on sczi via the web ansible role
Linx
- Setup on sczi via the web ansible role
Acidburn
- Migrate homedirs to dirtycow NAS
- Implement background tmux irc systemd service (or just tell people to use crontabs @reboot (sounds like u got a problem w/ systemd))
User Accounts
- Setup on chimera via freeipa-server ansible role
- Import LDAP accounts to freeipa
/tank
- Move main stuff to dirtycow
- Clean up a bit
Issues with current services
When (re)implementing services listed above do the following changes.
VTLUUG Site
- We're literally proxying a static github page (vtluug.github.io)
- Probably should be redesigned to be slightly more dynamic using jekyll or flask or something
VTLUUG wiki
- Need meeting script
- Need to clean up a lot of old information
Gobblerpedia
- Lots of out of date information
- Building templates (populate automatically from database)
Wadsworth/phenny
- Things constantly break, but there's nothing we can really do about this
- Migrate to irc3 pythong library for a stable core
- Migrate SysV scripts to systemd unit files
VTBash
- Old shitty interface converted from python2 to python3
- Nothing good seems to already exist, so we probably need to write one from scratch
- Need to merge 2 old sqlite databases
- Causes bug when only 1 quote author is entered, this is why they can't be merged
Hokieprivacy
- Mobile formatting is fucked -- someone should look into the hugo templates and fix
- Out of date
Linx
- Offload storage to NAS
- Binaries need updating
- Need to do reddit stress test
vtluug.org/files
- Need easy way fo non-root to add stuff here
vtluug.org/users/~$USERNAME
- should document for users
- maybe support dynamic server-side content (probably not; use js)
- Train spamassassin (use corpus)
- Sieve doesn't seem to work
gopherspace
- who tf uses gopher (fwiw, gopher was 90% of the goal of project bringing sexy back)
- legacy IP only, b/c pygopherd is shite
TOR services
linx, hokieprivacy, and the main site (hence vtluug.org) can be accessed over tor. advertise these urls or make them more memorable (or both)