4320
Comment: walnut+kerosene+lard, -bitumen
|
4757
Add un(der)documented machines and services
|
Deletions are marked like this. | Additions are marked like this. |
Line 16: | Line 16: |
|| '''[[http://www.ucc.asn.au/services/login.ucc|User Shell Servers]]''' || [[Motsugo]] (Debian, and the preferred user server), [[Mussel]], [[Meersau]], [[Musdea]] (FreeBSD), [[Maaxen]] (Windows), [[Gothamburg]] (Macintosh XServe)|| | || '''[[http://www.ucc.asn.au/services/login.ucc|User Shell Servers]]''' || [[Motsugo]] (Debian, and the preferred user server), [[Titan]] (Debian ARM), [[Mussel]], [[Meersau]], [[Musdea]] (FreeBSD), [[Maaxen]] (Windows), [[Gothamburg]] (Macintosh XServe)|| |
Line 37: | Line 37: |
|| '''Member management''' || [[UCCPortal]] (runs https://portal.ucc.asn.au) || || '''Unifi Controller''' || [[Salmon]] (not to be confused with the old machine, [[https://www.ucc.asn.au/machines/salmon.ucc|Salmon]]) || || '''Version Control''' || [[GitlabHost]] (boring name, IKR) || || '''Monitoring''' || [[Myxine]] (ocsinventory), [[LibreNMS]] (seems defunct), [[UCCMonitor]] (runs prometheus/grafana) || |
|
Line 48: | Line 52: |
1. [[mailfish]] - mailfish must come up last - it relies on a number of other services (user home directories, routing etc.) Try and minimise the amount of time it's down - due to the UCC network design, it's the only MX for UCC. Most mailservers will requeue emails if they can't contact mooneye, but some will bounce after as little as a day. | 1. [[Mailfish]] - mailfish must come up last - it relies on a number of other services (user home directories, routing etc.) Try and minimise the amount of time it's down - due to the UCC network design, it's the only MX for UCC. Most mailservers will requeue emails if they can't contact mooneye, but some will bounce after as little as a day. |
UCC Machines
The UCC runs a variety of different hardware. Not just your old Windows machines, or even the increasingly common GNU/Linux or Mac OS X machines. The UCC likes to run lots of other operating systems and architectures, which are sometimes uncommon or extinct out there in the Real World.
The list of machines is currently up to date in the list below.
If you want to know about our old machines, see the section Past Machines. To find out how we name our machines, see Nomenclature.
In the clubroom
Linux |
|
Windows |
|
Macintosh |
|
Oligoboots |
Combto (projects bench computer) |
Services
Motsugo (Debian, and the preferred user server), Titan (Debian ARM), Mussel, Meersau, Musdea (FreeBSD), Maaxen (Windows), Gothamburg (Macintosh XServe) |
|
Dispense Server |
|
Dispense Clients |
|
DNS |
|
Files |
Motsugo (secure /home), Molmol (/away, /space, /services, /mp3s and /vmstore) |
Flame |
|
FTP |
|
LDAP |
Mussel (master) |
Mailfish (mailhost), Mooneye (old mailhost), Motsugo (IMAP and POP server), Mailauesi (haproxy: front-end load balancer for IMAP, POP, SMTP submission) |
|
Routing |
|
Switching |
|
Web |
|
Webcams |
|
Logging |
|
Printers |
Blacklight served up by CUPS on Midshipman, Hologram (3D Printer) |
Samba |
|
VM Hosts (Proxmox/KVM) |
|
Cooling |
Kalimari (was Antarctica) |
Display |
|
Member management |
|
Unifi Controller |
|
Version Control |
GitlabHost (boring name, IKR) |
Monitoring |
Myxine (ocsinventory), LibreNMS (seems defunct), UCCMonitor (runs prometheus/grafana) |
Also read about our online Coke machine, online snack machine and online door sensors. Also check out the exciting services these, and our other machines, provide.
For the curious, here is a photo of our (ex) world class cooling system.
Server boot order
From time to time, the servers in the machine room go down and need to be restarted - to do so, there's a particular order that needs to be followed so things bounce back correctly.
Murasoi - Core routing / firewall - bring up first if networking is required
Molmol - NFS including nas-vmstore, needed for some VMs to boot
Motsugo - NFS including the user network home directories - needs to come up early as other things (eg. Mail) depend on it
Proxmox VM hosts, above - many virtual machines including Mussel and Samson
Mooneye - Internal UCC DNS and resolver
Mailfish - mailfish must come up last - it relies on a number of other services (user home directories, routing etc.) Try and minimise the amount of time it's down - due to the UCC network design, it's the only MX for UCC. Most mailservers will requeue emails if they can't contact mooneye, but some will bounce after as little as a day.
All the other servers including Merlo