DevOps DayCamp

The Open Source Lab will host the new DevOps DayCamp on Saturday, October 11, in the Kelley Engineering Center from 9 a.m. until 6 p.m. The event is free and open to the public.

DevOps DayCamp will kick off DevOps BootCamp, allowing students to start their DevOps education early in the school year. In order to accommodate different experience levels, DayCamp is comprised of two tracks: a beginner track and an advanced track. The beginner track will help inexperienced attendees get started with DevOps through introductory sessions and workshops on the basics of DevOps. Additionally, the advanced track will be comprised of a hands-on hackathon with educational sessions throughout the day for the more experienced DevOps crowd. Advanced track sessions will be given by industry professionals and will include Ansible, Travis CI and Docker.

The OSL is hosting DevOps DayCamp instead of the fall Beaver Barcamp. Due to the tight academic calendar, as well as the amount of organizing a successful Barcamp entails, Beaver Barcamp is now an annual event held in the Spring.

Read more

Make Bash, Not War

At the OSL we have shared workstations, most of which are named after colors. In the NOC, I usually work at emerald.workstation.osuosl.bak (Figure 1). I use tmux (Figure *) to multiplex so I can have multiple terminals open in a single ssh connection and connect to my session from anywhere. When splitting the terminal vertically, the prompt can get so long that it's hard to see the command that I'm entering (Figure 2). I'd like my prompt to automatically shorten itself in narrow windows. Fortunately, my terminal already knows how much space it has available: $COLUMNS is an environment variable which stores how wide your current terminal is, and the default unixism is 80. So in order to save space, I'd like to shorten my prompt to only a directory listing and a colored character replacing the normal $ or >.

Behold! (Figure 3, 4)

Read more

A Recap of OSCON 2014

The OSL made a strong showing at the O’Reilly Open Source Conference (OSCON) this year with the majority of the student employees attending along with all of the full time staff. The conference was held in Portland, OR, and fell on July 20-24.

The Lab always places a special emphasis on education, and the conference was certainly an educational experience. The expo hall held dozens of booths filled with information and demonstrations about open source projects and the companies that support them.

The expo hall was student developer Evan Tschuy’s favorite part of the conference. “I liked wandering around the expo hall because there were so many booths. It was like ‘I’ve heard of that company! Them too! I’ve never heard of them, what are they about?’”

In between shifts at the OSL booth, staff that attended the conference were given the opportunity to go to a variety of informational sessions including A Glimpse of Git’s future, Data Structures and Netflix API: Top 10 Lessons Learned.

Read more

Google Migration Post-mortem

OSU administration recently approached the OSL asking us to help migrate their email archives to Google. Through contacts with other local universities that had made the switch recently, we discovered that Portland State University had written and published an open source Python app to manage the process. In the name of expedience, we decided to fork that project and use that as our base from which to extend.

Having had time to reflect, I’d like to share a few lessons from the experience:

1. Enterprise means customized. All software comes bundled with biases and assumptions; small teams may be better off adapting their organization to fit those assumptions, but there exists a threshold beyond which it is easier to adjust software to fit the organization's assumptions instead. Despite forking a completed application, we found ourselves making several customizations and undoing several assumptions made by upstream developers.

Read more

Vim Trick FTW!

Recently, I learned a useful Vim trick. One of our hosted clients has a Dokuwiki instance that we help manage, and they were having problems with a lot of spam user accounts being created. We added a CAPCHA to the wiki to make it less convenient for new spammers to join, but there were a lot of bad accounts already existing. By "a lot," I mean there were 112,808 accounts listed in users.auth.php, and only about a dozen real project personnel using the wiki on a regular basis.

To clean it out, we decided the best course of action would be deleting every account except those with admin privileges, because most of the real humans were in the admin group and those who weren't could get the project leader to re-add their accounts. The benefit of clearing out a hundred thousand spammers would, in this case, outweigh the inconvenience of manually recreating a couple of real accounts.

Read more

Protein Geometry - What the Heck is That?

When I bumped into my biochemistry professor, Dr. Kevin Ahern, on campus a few months ago, I had the pleasure of explaining how I actually get to use what I learned in his class. And at the Open Source Lab of all places. At the lab, I’ve had the opportunity to work on an open source project called the Protein Geometry Database (PGD), and my coursework as a food science major with fermentation science option -- specifically, that course in biochemistry -- has proven unexpectedly helpful when working on the PGD.

Read more