Published: Tue 03 February 2015
Two blog posts in a day? I'm setting some really high expectations for myself.
Today's (second) blog post is about how I have this virtual container of ones and zeroes configured on the internet and the changes I plan to make to it in the near future. I consider it to be a rather important section of my internet life, considering it hosts my Quassel core and my eponymous website. For those unfamiliar with
Quassel, it's a distributed graphical IRC client that allows you to connect from anywhere and maintain an IRC presence across multiple devices. I'll write more about my experiences with it at another time.
At the time of writing, the server that hosts this website, my Quassel core, and a handful of other services, runs CentOS 6.6 x64. It is currently hosted on an OpenVZ VPS hosted by Hostigation. I intend to eventually migrate away from both CentOS 6.6 (in favor of Fedora 21) and the OpenVZ platform.
My primary reason for wanting to leave OpenVZ is because of its limitations. It lacks proper full-stack IPv6 support. The networking is subpar. It lacks the ability to upgrade kernels. If a new version of an OS comes out (whether Fedora, Ubuntu, CentOS, or whatever your choice is), the only real supported method to get to the new version is "nuke it from orbit and install the new version." I could spend a lot of time complaining about why OpenVZ sucks, but there is one advantage to it: It's super cheap to run for a host, and as a result, they sell super cheap VPSes with it. I currently pay $40/year for this VPS, which comes with 256MB guaranteed RAM, 512MB burst, 1TB of traffic, a few IPv6 addresses, and 25GB of storage. $0.11/day is pretty damn cheap for what I'm getting out of this.
I'm not entirely sure what platform I'll be going with next. It's looking like a PostgreSQL server will be in my future, considering that
MySQL has apparently been a low priority for the Quassel team. Ideally, I'd like to get at least 20GB of SSD-based storage, 1GB of RAM, a 100mbps port with at least 500GB of traffic, and be located somewhere in the eastern-half of the United States. A platform that is conducive to kernel upgrades is a must, because as rewarding as it can be to get everything back up and running after a nuke-and-reinstall, it's much nicer to just sit down at my desk in the morning, double-click on Quassel, and join my friends on IRC.
Now, about CentOS. I love CentOS. It's a great distro. Of all of the Linux distros out there, the Red Hat family of distros is what I am most familiar with these days. Since my days as a Fedora Infrastructure team member, I've learned a lot about all of the RPM-based distros. The problem with CentOS, for me specifically, is its release schedule. It's too slow. When I originally chose CentOS, it was because it was stable, and could rely on it to keep pumping bits for me as long as I kept running
yum update occasionally and paying the bills. Well, unfortunately, I've decided that I wanted some new features. I want some of the bleeding-edge stuff that I chose to forego when I picked CentOS a couple of years ago. CentOS, it's not you, it's me. Don't worry though, I'm staying in the family. I'll be moving to Fedora once I get everything inventoried, config files backed up, and can find a couple of hours to completely rebuild this server from the ground up.
As usual, if you've got questions, comments, hate-mail, or tweetspam, please feel free to