Difference between revisions of "Project Bringing Sexy Back"

From the Linux and Unix Users Group at Virginia Teck Wiki
Jump to: navigation, search
imported>Pew
(→‎VMs)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
'''Note''': This page does '''not''' reflect current infrastructure. It is for planning purposes.
+
'''Note''': This page does '''not''' reflect current infrastructure. It was for planning purposes. As of 2019 everything has been migrated to new infra, as explained in [[Infrastructure]].
 +
 
 +
If you're looking for the older project [[User:telnorattti|telnoratti]] proposed, details about it are at [[Summer_2013_New_Machines]].
  
 
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
 
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 [[Infrastructure:Acidburn|Acidburn]]. This is not possible with the current hardware.
+
One major change offering a VPS service in addition to shell accounts on [[Infrastructure:Acidburn|Acidburn]]. This is not possible with the current hardware.
  
 
<!--TODO talk about doing stuff from the project list-->
 
<!--TODO talk about doing stuff from the project list-->
Line 12: Line 14:
  
 
We are still working on exactly what to ask for, but here are some desirable things:
 
We are still working on exactly what to ask for, but here are some desirable things:
−
//TODO link items
+
 
 
{| class='wikitable' id='sortMe'
 
{| class='wikitable' id='sortMe'
 
!Priority
 
!Priority
Line 39: Line 41:
 
* Router/DNS Server: joey (sry temp88191 is too old)
 
* Router/DNS Server: joey (sry temp88191 is too old)
 
* NAS: [[Infrastructure:Cyberdelia|Cyberdelia]] due to its HDD capacity
 
* NAS: [[Infrastructure:Cyberdelia|Cyberdelia]] due to its HDD capacity
−
* Proxmox hosted-engine: Both R620s, Phantomphreak
+
* Libvirt hosts: Meltdown & Spectre
 
* HPC: [[Infrastructure:Wood|Wood]] due to its 4U height that can easily fit gpus
 
* HPC: [[Infrastructure:Wood|Wood]] due to its 4U height that can easily fit gpus
  
Line 59: Line 61:
 
|128.173.88.191
 
|128.173.88.191
 
|-
 
|-
−
|"Main" Proxmox Node
+
|One Libvirt Node (out of 2)
 
|meltdown.vtluug.org
 
|meltdown.vtluug.org
−
|128.173.89.244
+
|128.173.89.246
 
|-
 
|-
 
|Web/Proxy server
 
|Web/Proxy server
Line 72: Line 74:
 
|-
 
|-
 
|FreeIPA
 
|FreeIPA
−
|zerocool.vtluug.org
+
|chimera.vtluug.org
 
|128.173.89.247
 
|128.173.89.247
 
|-
 
|-
−
|Mirror
+
|Primary NFS server
−
|mirror.vtluug.org
+
|dirtycow.vtluug.org
−
|128.173.89.246
+
|128.173.89.244
 
|-
 
|-
 
|Matt's server
 
|Matt's server
Line 91: Line 93:
  
 
Syntax:
 
Syntax:
−
* Host (hostname)
+
* Overall service (hostname)
−
** Services running on host
+
 
 +
Services running on each host are covered in the following sections
  
 
=== Essential ===
 
=== Essential ===
Line 100: Line 103:
 
* Firewall (joey)
 
* Firewall (joey)
 
* NAS ("new" dell 2900 - dirtycow, dell 2900 - cyberdelia, r310 - shellshock)
 
* NAS ("new" dell 2900 - dirtycow, dell 2900 - cyberdelia, r310 - shellshock)
−
* Proxmox VE (meltdown,spectre,phantomphreak)
+
* Libvirt hosts (meltdown, spectre)
  
 
==== VMs ====
 
==== VMs ====
Line 109: Line 112:
 
=== Very Important ===
 
=== Very Important ===
 
==== Bare Metal ====
 
==== Bare Metal ====
−
* VPS system via Proxmox
+
* VPS system via Libvirt
 
** Somewhat automated system where a user is given a VM
 
** Somewhat automated system where a user is given a VM
 
** Give each user an ipv6 address
 
** Give each user an ipv6 address
Line 115: Line 118:
  
 
==== VMs ====
 
==== VMs ====
−
* rsyslog (theplague)
+
* elk (theplague)
 
** Need to research this a bunch
 
** Need to research this a bunch
−
 
 
* jitsi.vtluug.org (jitsi)
 
* jitsi.vtluug.org (jitsi)
 
** Proxy through sczi
 
** Proxy through sczi
 
* emby.vtluug.org (emby)
 
* emby.vtluug.org (emby)
 
** Proxy through sczi
 
** Proxy through sczi
 +
* mirror.vtluug.org (mirror)
 +
* syncthing discovery server (sync)
  
 
=== Important ===
 
=== Important ===
 
==== VMs ====
 
==== VMs ====
−
* mirror.vtluug.org (mirror)
 
−
* syncthing discovery server (sync)
 
 
* Tahoe-LAFS (crashoverride)
 
* Tahoe-LAFS (crashoverride)
 
* telnet BBS
 
* telnet BBS
Line 149: Line 151:
  
 
=== Wadsworth/phenny ===
 
=== Wadsworth/phenny ===
 +
* Use irc3 module instead
 
* Setup on acidburn via the small-services ansible role
 
* Setup on acidburn via the small-services ansible role
  

Latest revision as of 02:34, 10 January 2019

Note: This page does not reflect current infrastructure. It was for planning purposes. As of 2019 everything has been migrated to new infra, as explained in Infrastructure.

If you're looking for the older project telnoratti proposed, details about it are at Summer_2013_New_Machines.

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 offering a VPS service in addition to shell accounts on Acidburn. This is not possible with the current hardware.


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:

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
  • Libvirt hosts: Meltdown & Spectre
  • 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
One Libvirt Node (out of 2) meltdown.vtluug.org 128.173.89.246
Web/Proxy server sczi.vtluug.org 128.173.88.78
Shell Server acidburn.vtluug.org 128.173.89.245
FreeIPA chimera.vtluug.org 128.173.89.247
Primary NFS server dirtycow.vtluug.org 128.173.89.244
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:

  • Overall service (hostname)

Services running on each host are covered in the following sections

Essential

Bare Metal

  • Routing (joey)
  • DNS (joey)
  • Firewall (joey)
  • NAS ("new" dell 2900 - dirtycow, dell 2900 - cyberdelia, r310 - shellshock)
  • Libvirt hosts (meltdown, spectre)

VMs

  • FreeIPA (chimera)
  • Web services (sczi)
  • Shell (acidburn)

Very Important

Bare Metal

  • VPS system via Libvirt
    • Somewhat automated system where a user is given a VM
    • Give each user an ipv6 address
  • NAS Backup

VMs

  • elk (theplague)
    • Need to research this a bunch
  • jitsi.vtluug.org (jitsi)
    • Proxy through sczi
  • emby.vtluug.org (emby)
    • Proxy through sczi
  • mirror.vtluug.org (mirror)
  • syncthing discovery server (sync)

Important

VMs

  • 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

  • Use irc3 module instead
  • 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)

mail

  • 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)

Retrieved from "https://vtluug.org/w/index.php?title=Project_Bringing_Sexy_Back&oldid=7622"