Archive | lists

Round-up: process managers, job schedulers, and private clouds!

Oh my!

Here’s some bite-sized things that have been hanging out in my “Oh man, these look neat” queue for the last couple of weeks.

  • A while back, I wrote something about evaluating process managers; maybe you remember?. Anyway, Crocodoc‘s Matt Long recently wrote a post where he also dove into process managers. It also got some traction on HackerNews, where the peanut gallery has something to say about the matter. By the way, congratulations Crocodoc!
  • OpenStack on RedHat, CentOS, OR Fedora? With an easy-peasy installation process and support for building on as few as one, single, solitary hardware node? Hello RDO!

  • You may or may not know this, but last year I lost months at $DAYJOB researching free and commercial Job Scheduling systems that can scale better than Cron1. But Airbnb recently released an exceptionally interesting scheduling tool named Chronos built on Apache Mesos and if I’d had this a year ago then the project probably would have gone very, very different.

  1. Spoiler Alerts: Cron doesn’t scale, and we hated everything we found. 

Working. Busy. Read these instead.

So many posts in the “draft” status, and so little time to make any of them presentable. But there’s been a ton of interesting things coming down the pipe for the last few weeks and I wanted to hype a few things that caught my attention.

  • Ruby 1.8.7 EOL in 90 days
    The only reason to have any Ruby 1.8 installations floating around is because it’s what
    Puppet Labs distributes if you use the packages they provide.
    Embrace change.
  • Marc Gauthier | Please Keep a Changelog For Your Open Source Lib
    This is probably tied with “no examples or sample code” for
    “biggest open source pet peeve” and Marc makes an excellent argument for why
    changelogs rule.
  • Chronos
    airbnb needed a distributed task scheduling solution, so they wrote one.
    At ${DAYJOB} I was once involved in a project to find a cron replacement
    which was distributed and provided a web front-end. The project failed horribly
    and we instead built nothing. This would have been fast-tracked as
    “must build proof of concept” if it had existed at the time, no questions asked.
  • Rob Bell | A Beginner’s Guide to Big O Notation
    For reasons I’ve never really be able to fathom, Google and almost anyone who
    has ever worked for Google insists on asking admins about algorithms because they
    deeply, truly believe that an admin should have a computer science background.
    Nevermind that this industry has spent 30 years abstracting things to the point
    where even CS majors don’t really have CS backgrounds anymore. I don’t do so hot
    on those tests, but in my eternal quest to hold my own whenever possible I found
    Rob’s introduction to be tremendously useful. Now, if anyone ever asks how long
    a bubble sort takes (… again), you and I can tell them O(N2) and
    we won’t mix it up with O(2N). Let’s be armchair computer
    scientists together!

And finally, because this project is near and dear to me:

  • Lack AV Rack
    I’ve built a couple of small Lack Racks using shelving brackets, but nothing
    that looks as clean and professional as these. If you’re an audio-gear slut who is
    handy and thrifty, you owe it to yourself to go through sparced‘s
    build-out documentation.

See you all after Monitorama!