I've done some mostly basic stuff in COSI.

As always, I help to keep COSI clean. I made sure that the room was spotless when we had our two open houses. This included leading a team of Graham , Hunter, Abby, and myself to clean every inch of COSI, including vacuming the floor, sanitzing all keyboards, mice, and desks, cleaning dust from behind monitors, wiping down Turtlebots, organizing things into cubbies and their respective locations, cleaning around the 3D printer, and wiping down the center table until it shined clean.

Me and Bobby cleaned the inside of the VR machines, it was full of dust. We also documented all of the RAM on Docs.

I also help a little with CS141 students when they need help.

I am helping a bunch with organizing the budget for the igniteCS project from Google, which we were funded $10k. I have also been creating two pieces out of five pieces of the curriculum for the students, related to networking and also a final challenge.

As usual, I'm pretty involved in the server room. I discovered this semester while compiling the services emergency contacts list that I have the most services. That took me by suprise, but I realize that I tend to suck up projects. I do a lot of general maintence as well. I'm generally a pretty knowledgable go-to regarding many services.

Networking Stuff

Power Stuff

I have continued in my quest to document the server room power distribution, and have completed this project. Documentation can be found on Docs.

Hydra

Hydra is our new 32 core, 64GB RAM VM host.
My job, along with Baha, was to put together this machine and to install the software. Baha specced out the hardware late last semester, and the parts arrived over the summer. On the first weekend, we created Hydra. Baha assembled the parts, and then I installed the software, backed up the VM's, and then did the transition from Felix to Hydra. I handed off Felix to Bobby, who will now be running Androbattery natively on hardware, since it really put a toll on Felix as a VM, eating most of the ram and all of the CPU much of the time, and the image would not resize properly without some difficult tweaking.

It runs about 10 services currently, including a hodge podge of pretty much every service COSI has to offer.

GitLab

This service constantly requires attention and is one of the harder services to manage. Recently, we moved it from a Virtual Machine on Hydra (and Felix before that) to Distance (and renamed the server GitLab)

Other Services

Here's a full service list with a small blurb about what's up with it:

• Stat - See below (wait!)
• Hydra - See above
• GitLab - See above
• Bennu - Nothing new to report except for ridiculous uptime - it's a perfectly funcitoning VM host
• Comm - After rebuilding Comm last semester, more and more people have been using this service to communicate via Mumble over long distances.
• hwiki - What happens in Canada stays in Canada
• DDC-Router - Bobby and Graham set up PXE for the DDC.
• Talos - I'm still learning about Talos from GRM and how it works
• Switches - I've been configuring them to be accesible from Management, and throttling internal services when needed. Also, documenting a lot about the network configuration Many things related to the firewall also touched these switches, including the active failover from SWM2 to SWM3 if Ziltoid breaks. Also, replaced SW6 and set up SWM4

Bobby and I moved a bunch of machines from the second floor to evaluate what hardware we have down there. This included many heavy devices including heavy Cisco network switches, the Blade Servers, and a bunch of smaller peices of server and desktop hardware. Much of the hardware is decrepit or impracticly out of date, and some of it we might use to help run more services.

Management 2.0