Linux and Unix Users Group at Virginia Teck Wiki - User contributions [en]

Infrastructure:Scaryterry

2025-02-24T00:06:48Z

Coolcuber:

'''Scaryterry''' is our web host running on [[Infrastructure:Spectre|Spectre]].

== History ==
Scaryterry was created in 2025 for the purpose of hosting webpages for Virginia Tech student organizations. Scaryterry is named after Washington wide receiver [https://en.wikipedia.org/wiki/Terry_McLaurin Terry McLaurin], whose greatness transcended VTLUUG naming precedents at the time.

== Web Services ==
* Caddy proxy
** [https://awm.vtluug.org AWM at VT]

== See Also ==
* [https://github.com/vtluug/docker-manifests/tree/master/scaryterry docker configuration files]
* [https://www.nfl.com/players/terry-mclaurin/stats/career Terry McLaurin's stats]

[[Category:Infrastructure]]
[[Category:Hosts]]

Infrastructure:Scaryterry

2025-02-24T00:05:01Z

Coolcuber: Created page with "'''Scaryterry''' is our web host running on Spectre. == History == Scaryterry was created in 2025 for the purpose of hosting webpages for Virginia..."

'''Scaryterry''' is our web host running on [[Infrastructure:Spectre|Spectre]].

== History ==
Scaryterry was created in 2025 for the purpose of hosting webpages for Virginia Tech student organizations. Scaryterry is named after Washington wide receiver [https://en.wikipedia.org/wiki/Terry_McLaurin Terry McLaurin], whose greatness transcended VTLUUG naming precedents at the time.

== Web Services ==
* Caddy proxy
** [https://awm.vtluug.org AWM at VT]

== See Also ==
* [https://github.com/vtluug/docker-manifests/tree/master/scaryterry docker configuration files]
* [https://www.espn.com/nfl/player/_/id/3121422/terry-mclaurin Terry McLaurin's 2024-2025 season stats]

[[Category:Infrastructure]]
[[Category:Hosts]]

Infrastructure

2025-02-21T14:32:18Z

Coolcuber:

This page documents VTLUUG's infrastructure post-[[CVL eviction]].

== Physical Infrastructure ==
=== NFS Hosts ===
* [[Infrastructure:Dirtycow|dirtycow]] - Primary NFS server, 8x2TB raidz2 array
* [[Infrastructure:Cyberdelia|cyberdelia]] - OFF, 7x1TB raidz2 array, sitting on shelf instead of rack

=== VM Hosts ===
* [[Infrastructure:Meltdown|meltdown]] - Primary VM/docker host
* [[Infrastructure:Spectre|spectre]] - Secondary VM/docker host, for example user VMs

=== Router ===
* [[Infrastructure:Shellshock|shellshock]] - 3 disk RAID1 array

All hosts are on our own 1 Gb/s port with [[Infrastructure:Shellshock|shellshock]], a gateway featuring ARP proxying, and full delegation of the 2607:b400:6:cc80/64 prefix.

Virginia Tech has started blocking inbound ports 22 and 3389 and outbound port 25 at the campus border, in a move
[[User:echarlie|echarlie]] is calling [[gp:Cyber Auschwitz|Cyber Auschwitz]]. Contact itso-g@vt.edu for firewall exceptions.
When deploying new hosts, make ssh listen on both 2222 and 22. [[Infrastructure:Acidburn|Acidburn]] currently listens on 3128 as well.

=== Other hosts ===
* [[Infrastructure:Joey|joey]] used to be the router, but is no longer in use due to a failure of the single drive
* [[Infrastructure:Wood|Wood]] is sitting in our rack turned off because we don't have a use for it currently. It is in a 4U case capable of fitting several GPUs.
* [[Infrastructure:Sunway|sunway]] and a SuperMicro server were all transferred to WUVT. Older hosts have either been thrown out or given to members.
* A mystery Proliant dl380 g7. Unnamed and unused at the moment.

See [[VTLUUG:Strategic_plan]] for things we plan to do in the future.

== On the Network Architecture ==
''Further Information: [[Infrastructure:Networking]] and [[Infrastructure:Network]]''

[[File:Infra2019-network.png|thumb|500px|A simple network diagram by [[user:pew|pew]]. '''Update June 2021: Joey is dead, long live Joey. Shellshock is the new router. Cyberdelia is off.]]

We currently have some services with public IPv4 address, and all hosts have an internal IPv4 address on the 10.98.x.x/16 subnet and an IPv6 address assigned via SLAAC.
In the future, [[Infrastructure:IPsec|VPN]]/[[Iodine]] should be used.

In theory, services can be provided via a hidden service such as [[w:Tor|Tor]], but that introduces other complications.
Alternately, services can require use of the [[Infrastructure:IPsec|VPN]] on [[Infrastructure:Acidburn|acidburn]],
[[Iodine]], or [[Secure Shell|ssh tunnelling]], although all of these limit usage to members with a shell account.
All of these have the benefit of NAT transversal, however.

== Services ==
''Further information: [[:Category:Services]]''

* [[Infrastructure:Acidburn|acidburn]]
** Shell server
** [[Email]]
** [[Wadsworth]]
** [[Iodine]]
* [[Infrastructure:Chimera|chimera]]
** FreeIPA
* [[Infrastructure:Sczi|Sczi]]
** Website
*** [https://hokieprivacy.org hokieprivacy]
*** [https://bash.vtluug.org vtbash]
*** [https://vtluug.org Main Site]
*** This wiki and [[gp:Main Page|Gobblerpedia]]
*** dex, for authing with the wikis
*** https://vtluug.org/users/~$user - User homepages
*** [https://search.vtluug.org 4get] a metasearch engine
*** [https://git.vtluug.org Gitea] a Github-esque git server with dex/LUUG OpenID auth
*** [https://element.vtluug.org element], a Matrix client
*** [https://soulseek.vtluug.org slskd]
*** [https://seed.vtluug.org qbittorrent-nox]
*** [https://bitwarden.vtluug.org bitwarden]
* [[Infrastructure:Nikonwormhole|nikonwormhole]]
** AdGuard DNS blackhole
* [[Infrastructure:Dirtycow|dirtycow]]
** Storage for all primary services
** NFS - ZFS pool name is cistern
* [[Infrastructure:Meltdown|meltdown]]
** VM host for above services
* [[Infrastructure:Scaryterry|scaryterry]]
** [https://awm.vtluug.org AWM site]

[[Infrastructure:Acidburn|acidburn]] and the website ''must'' be accessible through real services, and it is preferable other hosts are too. This means we must use our public IPv4 & IPv6 Addresses allotted by ECE.

== Website details ==
=== Current Setup ===
All vtluug websites are run on nginx on [[Infrastructure:Sczi|sczi]]. These sites are currently functional:
* gobblerpedia.org
* hokieprivacy.org
* vtluug.org
* wiki.vtluug.org (redirects to vtluug.org/wiki/)
* bash.vtluug.org
* vtluug.org/users/~$user

All of these sites exclusively allow for the use of TLS connections. All services use automatically updated
letsencrypt certs.

==== Main Page ====
The main VTLUUG page was scraped from the [[w:Internet Archive|Internet Archive]] and added created as a github page at
[https://vtluug.github.io vtluug.github.io], and is reverse-proxied through [[Infrastructure:Sczi|sczi]].

==== Wiki ====
The wiki currently runs fully on MediaWiki hosted on nginx using a [https://github.com/vtluug/mediawiki-docker modified version of the official mediawiki docker image]. You can auth with the admin account, [[User:wiki-admin|wiki-admin]] or a Google account. See note on [[Main_page]] about why LDAP isn't working yet.

===== Gobblerpedia =====
Runs on the same Mediawiki instance as this wiki. Similarly to LUUGWiki, only Google accounts or the admin user are supported logins.

=== Needs Restoration ===
These are VTLUUG services that haven't yet been properly restored:
* [https://github.com/mutantmonkey/foodforus foodfor.vtluug.org] - For [[Wadsworth]]'s .pickfood and .foodvote commands. This is [[User:Timelord|jpo's]] fault.
* tahoe.vtluug.org - [[user:mjh|mhazinsk's]] Tahoe-LAFS grid
* git.vtluug.org - git hosting; previously a redirect to gitweb with gitosis as the SSH backend
* gitweb.vtluug.org - git hosting; previously gitweb
* [https://github.com/vtluug/campusmap map.vtluug.org] - [[Openstreetmap|OSM]] based map of VT

=== Historically ===

See [[Dead_projects]] for historic information

=== Goals ===
See [[VTLUUG:Strategic_plan#Web_Services]] for future goals involving web services

== Addressing ==
VTLUUG currently has DNS with gandi.net. Message officers for access (please don't be scared :D).

We currently hold the IPv6 prefix <code>2001:470:8:6d9::/64</code> from HE's allocation due to our tunnel.
When CNS finally sets up prefix-delegation, we might be able to get something from <code>2607:b400::/32</code>,
which is VT's largest allocation.

{{:Infrastructure:Network}}

[[Category:Infrastructure]]
[[Category:VTLUUG:Projects]]
[[Category:Featured content]]

Infrastructure:Sysadmin Handbook

2025-02-17T17:55:48Z

Coolcuber:

This page describes how to manage the infra. See [https://vtluug.github.io/rtfm.txt rtfm.txt] for a guide to build it from scratch.

This covers setup of a VM on [[Infrastructure:Meltdown|meltdown]] or [[Infrastructure:Spectre|spectre]] depending on if the service is critical or not.

== Infodump (i will clean this up later, promise) ==

LUUG infrastructure runs on, essentially, four key components:
* Hosts
* NFS
* Auth
and
* out-of-band Ansible & Docker manifests

Almost all of our services are hosted in Docker containers across various hosts: on [[Infrastructure:Gibson]], the LLM server, on [[Infrastructure:Sczi]] the web content. 100% of these docker containers have their configuration detailed [https://github.com/vtluug/docker-manifests here].

The entire repository is cloned to /nfs/cistern/docker/apps, and the docker-compose.yml files for each service are ran with the command 'docker compose up -d' while in the service folder.

Note the path: /nfs/cistern/docker/apps. Looking at the docker-compose folders & configs, you will notice that the *data* for the container is **never** stored alongside the compose files themselves. Instead, they are stored at /nfs/cistern/docker/data/<insert-service-name>/<etc>. This is an NFS (Network File System) mounted path: it exists physically on our NFS server, [[Infrastructure:Dirtycow]] and is mounted over the local network.

The implications of this should be clear: *the host install does not actually matter*. If the operating system for e.g. [[Infrastructure:Sczi]] blew up, all one would need to do to bring everything back up is re-create it, install docker, mount the cistern NFS directory (with the date files still intact), set up auth, and start all the containers again. No data is ever lost, because nothing is stored on the host itself: it's all on the NFS share.

How do you easily set all that stuff back up again? [https://github.com/vtluug/ansible Ansible]. you can think of ansible as a language designed for defining deployed servers. It uses YAML (.yml), and "roles" are specified for each server. in roles/<server role>/tasks, there exists a list of things needed to set up the server, and in /hosts.cfg there exists a list of servers and which roles they all have. All you need to do to set a server up is run ansible -- it will take care of the rest. You can run it twice, or a million times, to no ill effect: it's designed to be idempotent.

Knowing this much, you can re-create [[Infrastructure:Sczi]] and [[Infrastructure:Gibson]], but there are a few remaining things: VM hosts ([[Infrastructure:Meltdown]], [[Infrastructure:Spectre]]), and the router ([[Infrastructure:Shellshock]]). Deploying the router is described in [https://vtluug.org/rtfm.txt rtfm.txt], but VM deployment is entirely automated via ansible, which is *sick as fuck*. It only works for ubuntu server and redhat enterprise (alma, rocky, centos) distros, but for those it works brilliantly -- add a VM to [https://github.com/vtluug/ansible/blob/master/roles/deploy-vms/defaults/main.yml this file] and run the ansible playbook -- the new VM will automagically create.

Web traffic!
We run DNS through Gandi. Ask an officer to add you to the VTLUUG org on that website ([[User:Rsk]] has access, if you're reading this in the far future and need it).
Each host gets a direct A record pointing at it's IP address, and web content *all* points to [[Infrastructure:Sczi]] via CNAME records. Sczi's docker config has an nginx container that handles certificates and reverse proxying.

Acidburn is our singular "traditionally managed" server. It runs many services, mail among them, and all are running as services on the VM itself, not a container in sight (sans the IRC <-> Matrix bridge, which is there for IP whitelisting reasons. You can redeploy it from ansible, but it won't have the same soul. Try not to break it.

Auth
We run two Authentication servers, [[Infrastructure:Chimera]] and [[Infrastructure:Sphinx]]. They're both on the same FreeIPA network and can be deployed via ansible.

FreeIPA is a full-stack authentication provider. Part of our ansible playbook for LUUG hosts runs ipa-client-install, which sets up the hosts as "clients" to this FreeIPA network, and allows users with FreeIPA accounts to log in via ssh, reflecting usergroups over on to the system.

[[Infrastructure:Spectre]] notably is *not* a FreeIPA client, because it's intended for use by non-LUUG entities (whether that be personal member VMs or ones loaned out to other student orgs).

== Networks ==
''Further information: [[Infrastructure:Network|Network]]

We ''should'' have the following networks in place:

* [[Infrastructure:Meltdown|meltdown]] and [[Infrastructure:Spectre|spectre]] br0 on eno1 <--> enp4s0 on [[Infrastructure:Joey|joey]]. This is the main LUUG network.
** 10.98.0.0/16 for VTLUUG NAT
** IPv6 via prefix delegation on 607:b400:6:cc80/64
** Global IPv4s via ARP proxying (See https://github.com/vtluug/scripts). Gateway is 128.173.88.1/22.
* Static hosts are on 10.98.0.0/24, and DHCP is enabled on 10.98.1.0/24. This is mainly just useful for organization and quickly finding new hosts or other hosts on the network.
** Static host IPs are assigned via static DHCP leases for IPv4.
** Since we can't do this with IPv6, physical host IPs are determined upon first boot and VMs are assigned a specific MAC to pre-determine the SLAAC IP.
* "Internet" (a CNS portal) <--> enp2s0 on [[Infrastructure:Joey|joey]]. LUUG only has one of these, and port security is probably enabled.

'''DNS/DHCP:'''
* All DNS entries for services run by VTLUUG are hosted on [https://gandi.net Gandi]. Ask an officer if you want to change something.
* jkh and Roddy own ece.vt.edu. DNS updates don't happen. echarlie can add IPv6-only records if needed to wuvt.vt.edu so we have PTRs.
* [[Infrastructure:Joey|joey]] runs DHCP via dnsmasq on enp4s0 (that is, 10.98.0.0/16). To change anything, modify it on https://github.com/vtluug/scripts first then pull that into root's homedir on [[Infrastructure:Joey|joey]]. Please don't just update it on a machine without pushing your updates.
* By default, hosts are accessible via SSH on ports 22 and 2222.

== Adding a VTLUUG Service VM ==
''VMs in this category are deployed to [[Infrastructure:Meltdown|meltdown]]''

Prerequisites:
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.
* Have access to [https://git.vtluug.org/officers/vtluug-admin officers/vtluug-admin] on [https://git.vtluug.org gitea].
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].
* Put your SSH key on [[Infrastructure:Meltdown|meltdown]]

=== Configure the network ===
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code>
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases.
* If a new IP in 128.173.88.1/22 is being added, also add it to <code>SCRIPTS/router/proxy/arp_proxy.sh</code>

'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.

Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code>
* ARP Proxy configuration is in <code>/usr/local/bin</code>

=== Add the VM configuration to ansible ===
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry, following the existing format.

'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.

Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K -e @VTLUUG_ADMIN_REPO/accounts.yml</code>, using the correct vtluug-admin repo path.

=== Testing ===
The new host should be accessible by papatux on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.

== Adding a User VM ==
''VMs in this category are deployed to [[Infrastructure:Spectre|spectre]]''

Prerequisites:
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].
* Have root on [[Infrastructure:Spectre|spectre]]
* Put your SSH key on [[Infrastructure:Spectre|spectre]]

=== Configure the network ===
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code>
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases. (If applicable; you might not care for a test/temp VM).

'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.

Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code>

=== Add the VM configuration to ansible ===
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry under <code>new_vms_spectre</code>, following the existing format.

'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.

Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K</code>, using the correct vtluug-admin repo path.

'''Important:''' A random root password is set during VM creation and printed to stdout. Record this!

=== Testing ===
The new host should be accessible by root on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.

[[Category:Infrastructure]]
[[Category:Howtos]]
[[Category:Needs restoration]]

VTLUUG:Officers

2025-02-03T22:42:15Z

Coolcuber:

==Positions==
===Required positions:===
* '''President:''' The president is the public face of the Linux and Unix Users Group and the person responsible for seeing that all tasks of the organization are taken care of. The president position has traditionally not been allowed to be held by a senior (within one year of graduation).
* '''Treasurer:''' The treasurer is in charge of financial bookkeeping and appointing 1-2 SEC representatives. In the past, this has also included the duty of activities coordinator, which is in charge of the logistics and publicity of events.
* '''Vice president'''

===Additional positions===
We can appoint (or elect) up to two additional officers, in addition to an advisor. These positions are either up for election too, or just appointed by the new president and/or other officers. Here's a few positions that we've had in the past:
* Advisior
* Penguin Expert
* Activities Coordinator / Programs Manager / Outreach Coordinator
* Webmaster
* Secretary
* Sysadmin (or VP of IT)
* Graduate Liaison

Additionally, VTLUUG has given special titles (non-officer positions) to certain members in the past. These have included:
* Steering Committee Member
* Worker Peon
* Donor

==Current Officers==
The current officers are listed on [http://vtluug.org/about.html the about page] of our main website.

[[Category:VTLUUG:Administration]]

VTLUUG:Officers

2025-02-03T22:41:49Z

Coolcuber:

User:Coolcuber

2025-01-23T20:18:46Z

Coolcuber:

Math graduate student

openSUSE enthusiast

User:Coolcuber

2025-01-23T20:18:37Z

Coolcuber:

Math graduate student
openSUSE enthusiast

User:Coolcuber

2025-01-23T20:18:06Z

Coolcuber: Created page with "Math graduate student"

Math graduate student

VTLUUG:2025-01-22

2025-01-23T20:11:39Z

Coolcuber:

[[VTLUUG:2024-12-04|Previous Meeting]]

[https://github.com/vtluug/calendarium generated using calendarium]

== Time/Location ==

Meeting:
* Time: 2025-01-22 19:00:00
* Location: McBryde 240, maybe. we'll find an empty room day-of if that one's occupied.
* Subject: Installfest planning and the Spring semester
* Presenter: Rishi Krishna

== Plan/Description ==

We're going to hold an Installfest on the first week of February. This meeting, we'll hash out the details (what date, who's coming, what flavor pizza, ...). Also up for discussion: the rebuilt 100TB cyberdelia, and our new GPU compute server 'gibson'.

== Meeting Notes ==

=== installfest planning ===

Wednesday 02/05 12:00 PM to 5:00 PM

Ideas:
* Netbooting
* Ventoy

Supplies:
* USB drives (Zach, Rishi)
* Network switch (Rishi)
* Pizza (echarlie)

Distros:
* Ubuntu
* Debian
* Mint
* Bazzite (?)

=== general news ===

* DPR got pardoned!
* china has a super-AI model
* BambuLabs leaked their firmware signing key

=== whit server room field trip ===

it's still a server room.

[[category:VTLUUG:2025]][[category:VTLUUG:Meetings]]