Add information regarding labs, staff/school changes, asgard, yggdrasil and seps-app01.

Writerside/hi.tree

@@ -77,6 +77,10 @@
     <toc-element topic="Splashtop.md"/>
     <toc-element topic="Staff-Research-Device-Setup.md">
     </toc-element>
+    <toc-element topic="web01-services.md">
+        <toc-element topic="Asgard.md"/>
+        <toc-element topic="Yggdrasil.md"/>
+    </toc-element>
     <toc-element topic="Servers-and-Remote-Storage.md">
         <toc-element topic="socs-web01.md">
             <toc-element topic="Logging-In.md"/>
@@ -88,4 +92,12 @@
         <toc-element topic="Coltrane.md"/>
         <toc-element topic="Hephaestus.md"/>
     </toc-element>
+    <toc-element topic="Labs-and-Projects.md">
+        <toc-element topic="Arcade-Machines.md" accepts-web-file-names-ref="61f98d37"/>
+        <toc-element topic="INB1102-1A.md"/>
+        <toc-element topic="INB1301-1B.md"/>
+        <toc-element topic="INB1101-1C.md"/>
+        <toc-element topic="INB2102-2B.md"/>
+        <toc-element topic="INB2305-2C.md"/>
+    </toc-element>
 </instance-profile>

Writerside/redirection-rules.xml

@@ -25,6 +25,7 @@
     <rule id="41010b79">
         <description>Created after removal of "Staff Rotas" from SoCSTech Docs</description>
         <accepts>Staff-Rotas.html</accepts>
+    </rule>
     <rule id="679c8b1">
         <description>Created after removal of "Installing Linux" from SoCSTech Docs</description>
         <accepts>Installing-Linux.html</accepts>
@@ -39,4 +40,12 @@
         <description>Created after removal of "Windows Setup" from SoCSTech Docs</description>
         <accepts>Windows-Setup.html</accepts>
     </rule>
+    <rule id="66a0a5ad">
+        <description>Created after removal of "Traefik" from SoCSTech Docs</description>
+        <accepts>Traefik.html</accepts>
+    </rule>
+    <rule id="61f98d37">
+        <description>Created after removal of "Arcademia Leaderboard" from SoCSTech Docs</description>
+        <accepts>Arcademia-Leaderboard.html</accepts>
+    </rule>
 </rules>

Writerside/topics/Arcade-Machines.md

@@ -0,0 +1,25 @@
+# Arcade Machines
+
+The arcade machines, aka Arcademia or Research Arcade is a long term project running in the first floor corridor of the Issac Newton Building. They are occasionally used for recruitment both to the School and the Computer Science Society.
+
+Originally these were deployed as a project to gather data for experiments, the most notable project that came from the machines is paper [Adi's Maze and the Research Arcade: A Long-term Study on the Impact of Gendered Representation on Player Preferences](http://lncn.ac/adis-maze) published by Christopher J. Headleand, Bethany Davies, and Benjamin Williams.
+
+And after the arcade machines were stopped being used for research, they were converted into the Arcademia project, which used to promote student game development allowing students to make games for the machines.
+
+And then in 2024, [Matt F.](https://github.com/malphatt) as a part of the Computer Science Society, rewrote the launcher for the arcade machines in WPF and C#. He did this as two components the Updater and the Launcher.
+
+## Research Arcade Updater
+
+> [ComputerScienceSociety/Research-Arcade-Updater](https://github.com/ComputerScienceSociety/Research-Arcade-Updater)
+
+This is a service that runs on the machines to manage the state of the launcher and ensure it is always at the latest version.
+
+## Research Arcade Launcher
+
+> [ComputerScienceSociety/Research-Arcade-Launcher](https://github.com/ComputerScienceSociety/Research-Arcade-Launcher)
+
+This is the actual launcher window which allows users to launch the games. To exit this, <kbd>alt</bkd>+<kbd>f4</kbd> then <kbd>win</kbd>+<kbd>r</kbd> and re-launch `explorer.exe`.
+
+## Computer
+
+There is an ex-lab pc in the bottom of the arcade cabinets, this machine doesn't need to be all that powerful but should be powerful enough to run the arcade games the students make.

Writerside/topics/Asgard.md

@@ -0,0 +1,58 @@
+# Asgard
+
+Asgard is the name for the microservices that build the computing lab experience.
+
+The main part of it is that it's the backend timetabling engine that provides content to [yggdrasil](Yggdrasil.md), 
+it acts as a data aggregator and single point of truth to all display content.
+
+More specifically we are using it to combine the data we get from multiple sources such as the UoL Timetable, Internet Calendars, Microsoft Bookings and Manually created events.
+
+## Getting Started
+
+You will need an account to use asgard, you should have been provided this during your onboarding.
+
+![asgard-login.png](asgard-login.png)
+
+When you have been given your account you will need to go through the password recovery process to set a password for your account.
+
+The password for your account should be secure and not shared as if you have access to asgard you can put things on the signage screens, you should put this in your [1Password](1Password.md) employee vault.
+
+You will need this password everytime you want to make a change to the signage.
+
+You will either be given a 'technician' account or a 'standard' account. A 'technician' account has access to all timetables that exist inside the asgard system. 
+
+## Day to Day
+
+### Home
+
+![asgard-home.png](asgard-home.png)
+
+The asgard homepage is the page you will land onto first, it is a quick overview of the timetables that you're able to access (if you have a standard account) or the one's you've marked as favourite (if you have a technician account).
+
+### Timetables
+
+![asgard-timetables.png](asgard-timetables.png)
+
+#### Add Timetable
+
+![asgard-add-timetable.png](asgard-add-timetable.png)
+
+#### Manage Timetable 
+
+##### Events
+![asgard-manage-timetable.png](asgard-manage-timetable.png)
+
+##### Carousel
+![asgard-carousel.png](asgard-carousel.png)
+
+### Timetable Groups
+
+![asgard-timetable-groups.png](asgard-timetable-groups.png)
+
+## Development
+
+All development documentation is in the [GitHub Wiki in the Asgard Repo](https://github.com/SoCSTech/asgard/wiki).
+
+## Deployment
+
+Asgard is currently deployed onto the SEPS-APP01

Writerside/topics/Docker-on-socs-web01.md

@@ -1,22 +1,28 @@
-# Docker on socs-web01
+# Docker on seps-app01
 
 We make extensive use of Docker on the Server and in the School too. Docker powers our sites, services and some of the 
 student projects on this server! 
 
 There will be a section added soon to discuss Docker a little more. 
 We recommend you get yourself comfortable with the idea of using Docker before proceeding to make any changes to it on 
-`socs-web01`.
+`seps-app01`.
 
 ## Gotchas!
 * **You may find that after a reboot not all services are back up and running - these will need manually starting again!**
+* If you notice a service that is consistently not restarted, raise an issue on the [GitHub Repo](https://github.com/SoCSTech/seps-app01).
 
-## Using `docker-compose`
+## Using docker compose
 
-Please use docker-compose to start containers, rather than simply pulling and running containers directly. Store the
-`docker-compose.yml` in a directory relating to that service you are trying to run. This allows for easier maintenance.
+We use docker-compose to start containers, rather than simply pulling and running containers directly.
+
+To deploy a new service, clone the repo to your local machine, and create a folder named as the service and author a compose file describing your required deployment. 
 
 ## Monitoring Containers via `ctop`
 
+<warning>
+We are investigating replacing `ctop` as it is abandoned... This section will be updated in the future!
+</warning>
+
 As long as you have been added to the `docker` user-group, you will be able to use `ctop` to monitor, start, stop, restart
 and view logs on a container. `ctop` offers a nice "UI" that you can use to check container statuses rather than relying
 on `docker ps`.

Writerside/topics/INB1101-1C.md

@@ -0,0 +1,42 @@
+# INB1101 (1C)
+
+## PC Specification
+
+| Component | Spec                          |
+|-----------|-------------------------------|
+| CPU       | 11th Gen Core i5              |
+| GPU       | NVidia RTX 3070 w/ 12GB GDDR5 |
+| RAM       | 16GB DDR4                     |
+| SSD       | 1TB (NVMe)                    |
+
+## Capacity
+1C has a capacity of 28 lab PCs.
+
+## Imaging
+This lab is imaged using our master machines and CloneZilla, as detailed in the Lab Imaging section.
+
+## AV
+The AV in 1C needs to be checked before 9am every day.
+
+There is no Extron AV controller in this room, just an HDMI port in the wall and a remote controller for the projector.
+
+Academics frequently unplug the HDMI cable from the lectern PC to use with their laptops and don't plug it back into the
+pc, so make sure it is plugged into the PC when doing AV checks.
+
+More details on how to check the lab AV can be found in the Lab AV section.
+
+## PC Checks
+Ensure that all PCs turn on and boot before 9am every day.
+
+For some reason, students unplug the HDMI from the PC to use the monitor with their laptops in 1C way more than in other
+labs. They often don't put it back into the PC, or plug it into the motherboard instead of the GPU. When doing morning
+checks, if there is no display when turning on the PC this is very likely the issue.
+
+## Unique Features
+
+### Robotics Storage
+A number of different robots are stored in 1C, including the LIMO robots currently used for teaching. There are stored
+in the tambours, the keys for which have a red tag on them and are kept in the lock box in INB1201.
+
+The day before the workshop for a module that uses the LIMOs, they should all be checked and charged, but not left
+overnight.

Writerside/topics/INB1102-1A.md

@@ -0,0 +1,78 @@
+# INB1102 (1A)
+
+## PC Specification
+
+| Component | Spec                          |
+|-----------|-------------------------------|
+| CPU       | 11th Gen Core i5              |
+| GPU       | NVidia RTX 3070 w/ 12GB GDDR5 | 
+| RAM       | 16GB DDR4                     |
+| SSD       | 1TB (SSD)                     |
+
+## Capacity
+1A has a capacity of 78 lab PCs, 4 iMacs, 11 BYOD monitors and 1 usable desk with no PC.
+
+## Imaging
+This lab is imaged using our master machines and CloneZilla, as detailed in the Lab Imaging section.
+
+## AV
+The AV in 1A needs to be checked before 9am every day.
+
+There is an Extron controller that turns on/off both projectors in 1A. (The right side projector currently doesn't turn
+on from the controller, only from a remote control.)
+
+There are two inputs, PC and Laptop. PC displays the Lectern PC, and Laptop connects to the HDMI port in the lectern
+itself.
+
+Sometimes the laptop input refuses to display anything, in which case the AV unit needs to be turned off and on again.
+(We're not supposed to do this ourselves, so details won't be included in this document, but a senior technician will
+show you how to do this.)
+
+More details on how to check the lab AV can be found in the Lab AV document.
+
+### Combined Mode
+
+* **This can only be done by a technician or DT, so if you catch academics doing this tell them they need to contact us to
+  switch the AV into/out of combined mode.**
+
+* It is possible to combine the projectors in 1A and 1B to display the same input. This is useful when the wall between
+  the labs is open.
+
+* Open the AV cabinet in the 1A lectern, and you will see two AV switches with glowing numbers. The top switch is 1A, and
+  the bottom switch is 1B.
+
+* On the top switch, **number 3** is the input for the 1A lectern PC, and **number 7** is the laptop input.
+
+* On the bottom switch, **number 7** is the local input in 1B, and **number 3** simply copies whatever is being displayed in 1A,
+  whether that be a laptop or the lectern PC.
+
+* The rest of the numbers do not do anything. Only 3 and 7 matter.
+
+* When you swap inputs on the Extron controller you will see these numbers change, but you can also press the buttons on
+  the AV switch to change inputs manually.
+
+* To put the lab into combined mode, simply press the number 3 button on the bottom switch. The projector in 1B will now
+  display whatever is being displayed in 1A, whether that be the lectern PC or a laptop.
+
+* To set 1B back to displaying its local input, press number 7 on the bottom switch.
+
+* Hopefully by the time a new technician is reading this, DT have created a better solution for this using the Extron
+  controllers.
+
+* **We aren't meant to do this, but there is currently no other solution.**
+
+### PC Checks
+All the PCs in this room also need checking before 9am, especially if there is an exam that day. You must turn them
+all on, either manually or via Deep Freeze, and ensure that they all boot and display the lock screen.
+
+## Unique Features
+
+### Splashtop
+A large portion of our Splashtop remote lab is set up in 1A, on the wall with the projectors. These PCs run the normal
+lab image, with REFIND set to the desired OS and the splashtop client installed.
+
+### Wall to INB1301 (Lab 1B)
+The wall between 1A and 1B can be opened/closed using the key kept in INB1201. This allows the labs to be combined into
+one big lab. We do this frequently for exams and modules with a large number of students.
+
+Generally we only close the wall when there is a session run specifically in INB1301.

Writerside/topics/INB1301-1B.md

@@ -0,0 +1,50 @@
+# INB1301 (1B)
+
+## PC Specification
+
+| Component | Spec                                 |
+|-----------|--------------------------------------|
+| CPU       | 14th Gen Core i5                     |
+| GPU       | NVidia RTX 4070 SUPER w/ 12GB GDDR6X | 
+| RAM       | 32GB DDR5                            |
+| SSD       | 	1TB (NVMe)                          |
+
+## Capacity
+1B has a capacity of 48 lab PCs, and 4 extra PCs at the front of the room.
+
+## Imaging
+This lab is imaged using our master machines and CloneZilla, as detailed in the Lab Imaging section.
+
+## AV
+The AV in 1B needs to be checked before 9am every day.
+
+There is an Extron controller by the lectern which can turn on/off the projector, but there is only one input called
+'Laptop'. Despite it saying laptop, it is used to display the lectern PC. An HDMI cable runs from the PC under the desk
+to the HDMI port in the wall.
+
+When an academic wishes to use a laptop, they should unplug the HDMI cable from the PC.
+
+The projector in 1B can be combined to display the PC/Laptop connected to the controller in 1A, but this can only be
+done from the 1A side. More details on this can be found in the 1A documentation.
+
+More details on how to check the lab AV can be found in the Lab AV section.
+
+## PC Checks
+All of the PCs in this room also need checking before 9am, especially if there is an exam that day. You must turn them
+all on, either manually or via Deep Freeze, and ensure that they all boot and display the lock screen.
+
+## Unique Features
+
+### Wall to INB1102
+The wall between 1A and 1B can be opened/closed using the key kept in INB1201. This allows the labs to be combined into
+one big lab. We do this frequently for exams and modules with a large number of students.
+
+Generally, we only close the wall when there is a session run specifically in INB1301.
+
+### Wall Vinyl
+
+The room has vinyl on the walls which was installed in 2024 in partnership with XMA and ASUS ROG. 
+
+If the wall has become scuffed, you should clean the walls ASAP with a damp cloth and clean water. This is because the vinyl is the same as what can be installed on floors and is designed to be hard wearing but isn't bulletproof.
+
+If the vinyl gets damaged or needs repairing - there is some offcuts in the store room, but there isn't enough to redo a whole panel.

Writerside/topics/INB2102-2B.md

@@ -0,0 +1,43 @@
+# INB2102 (2B)
+
+## PC Specification
+
+| Component | Spec                         |
+|-----------|------------------------------|
+| CPU       | 11th Gen Core i5             |
+| GPU       | NVidia RTX 3060 w/ 8GB GDDR5 |
+| RAM       | 16GB DDR4                    |
+| SSD       | 1TB NVMe                     |
+
+## Capacity
+2B has a capacity of 56 lab PCs.
+
+## Imaging
+This lab is imaged using our master machines and CloneZilla, as detailed in the Lab Imaging section.
+
+## AV
+The AV in 2B needs to be checked before 9am every day.
+
+There is an Extron controller by the lectern which can turn on/off the projector. This is one of the newer touch screen
+controllers and generally works with no issues.
+
+More details on how to check the lab AV can be found in the Lab AV section.
+
+## PC Checks
+All the PCs in this room also need checking before 9am, especially if there is an exam that day. You must turn them
+all on, either manually or via Deep Freeze, and ensure that they all boot and display the lock screen.
+
+## Unique Features
+
+### Cisco Networking Equipment
+There are 4 racks at the back of 2B which contain Cisco equipment used for CCNA teaching. Each rack contains 2 switches,
+2 routers, and a firewall. Model numbers and more specific details can be seen on snipe.
+
+### Additional Ethernet Patching
+As well as the network ports which connect the Lab PCs to the university network, there is patching which connects
+extra network ports underneath the desks to patch panels in the network cabinets at the back of the room.
+
+### Additional PCs Under Desk
+Alongside the lab PCs on the desk, there is another PC underneath the desk. The idea is that these PCs connect through
+the additional patching to the cabs at the back of the room to create an isolated network, but currently it doesn't get
+used.