Changes

'''Note''': This is an effort toward the end of Fall 2017 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 page does '''not''' reflect current infrastructure, make managing the current infrastructure easier, and to provide enough documentation so that anybody can have a very good understanding . It was for planning purposes. As of how 2019 everything works without having has been migrated to ask the officers about every little thing. This will be summarized new infra, as explained in the [[Sysadmin HandbookInfrastructure]].

One major change If you're looking for the older project [[User:telnorattti|telnoratti]] proposed, details about it are at [[Summer_2013_New_Machines]]. This is running an oVirt cluster 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, along with 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 [[Infrastructure:Acidburn|Acidburn]]. This is not possible with the current hardware.

Ideally we will get 2. A much more detailed price analysis will be done for the SBB.

==== Hardware we will definitely have:====

=== Assuming we do get SBB funding = Configuration ====Additional hardware: 2x R620 * Router/DNS Server: joey (sry temp88191is too old)

* oVirt ControllerLibvirt hosts: R620* oVirt Workers (via PXE): R620 Controller, the other R620, Phantomphreak, JoeyMeltdown & Spectre

=== If we don't get SBB funding ===We probably need to get some additional RAM & CPUs for Wood Diagrams in this case in order to do the cluster.progress

* Router: temp88191* NAS: [[Infrastructure:Cyberdelia|Cyberdelia]]== Networking ==* oVirt Controller: [[Infrastructure:Wood|Wood]]* oVirt Workers (via PXE): See [[Infrastructure:Wood|WoodNetwork]], Phantomphreak, Joeyfor a mostly up to date networking layout.

We may also get some additional hardware early Spring 2017==== Public IPv4 addresses ===={| class='wikitable' id='sortMe'!Function!DNS!IP|-|Router/DNS|joey.vtluug.org|128.173.88.191|-|One Libvirt Node (out of 2)|meltdown.vtluug. This will replace Phantomphreakorg|128.173.89.246|-|Web/Joey, become the oVirt Controller, or the NAS depending on its specsProxy 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. TBD104|-Diagrams in progress|}

'''Note''': This secionsection's PoV does '''not''' taking into account the current state of service. Instead, it assumes services are being installed to a new infrastructure.

=== Urgent Essential ===

* Monitoring Routing (crashandburnjoey)*DNS (joey)* oVirt mostly takes care of this for usFirewall (joey)*** See https://ovirt.org/blog/2017/12/ovirtNAS ("new" dell 2900 - dirtycow, dell 2900 -metricscyberdelia, r310 -storeshellshock)** Prometheus or Nagios if more detailed monitoring is neededLibvirt hosts (meltdown, spectre)

* FreeIPA (zerocoolchimera) ==== K8s ====* Sczi proxy Web services (sczi)** For proxying *.vtluug.org because we don't have unlimited v4* vtluug.org Shell (vtluugacidburn)* wiki.vtluug.org (wiki_vtluug)* gobblerpedia.org (wiki_gobblerpedia)* hokieprivacy.org (hokieprivacy)* pSQL (wikidb)** For storing wiki.vtluug.org & gobblerpedia.org

* VPS system (crashandburn)via Libvirt

** Possibly is really easy with oVirtGive each user an ipv6 address** Possibly do something like <user>.users.vtluug.orgNAS Backup

* Shell (acidburn)** Member pages @ vtluug.org/~user* rsyslog elk (theplague)

* DNS jitsi.vtluug.org (lordnikonjitsi)** Need to research this a bunchProxy through sczi* Mail emby.vtluug.org (acidburnemby)** Possibly in Docker instead of VM ==== K8s ====Proxy through sczi* Wadsworth mirror.vtluug.org (wadsworthmirror)* duckhunter9000 syncthing discovery server (duckhuntersync)* truncatedcone (truncatedcone)* multimediamanv2 (multimediaman)** Produces /files/irc-vtluug.org 

* finger (kerberos-based)

* Migrate to docker === VTLUUG wiki ===* Backup content* Migrate to dockerSetup on sczi via the web ansible role

=== VTLUUG & Gobblerpedia wiki ===* Backup contentusing dumpBackup.xml script* Migrate Setup on sczi via the web ansible role* Restore content to dockernew wiki

* Backup db (for .in)Use irc3 module instead* Migrate to dockerSetup on acidburn via the small-services ansible role

* Migrate to dockerSetup on sczi via the web ansible role

* Migrate to dockerSetup on sczi via the web ansible role

* Move files to NAS* Migrate to dockerSetup on sczi via the web ansible role

* Migrate homedirs to dirtycow NAS* Currently have a ton of uses - most Implement background tmux irc systemd service (or just tell people probably don't to use it anymorecrontabs @reboot (sounds like u got a problem w/ systemd)) === User Accounts ===*Setup on chimera via freeipa-server ansible role* Have peopl re-register with FreeIPAImport LDAP accounts to freeipa

* Backup then clean upMove main stuff to dirtycow** Either to tardis or Clean up a temporary NASbit

* Lots of out of dat date information* Building templates(populate automatically from database)

* Mobile formatting is fucked, at least for FF on Android-- someone should look into the hugo templates and fix

* Train spamassassin(use corpus)

* who tf uses gopher(fwiw, gopher was 90% of the goal of project bringing sexy back)* legacy IP only, b/c pygopherd is shite