Below are the highlights from our October 11th customer conference call.

• It’s been a pretty quiet week which is a good thing.
• Our postgres DB maintenance went extremely well with less than 5 minutes of downtime.
• A node on C2 went down and will be replaced, however, no customers experienced any downtime. While we don’t like nodes going down, this is a great example of our redundant architecture.
• Development on control panel and self service tools continues along nicely.
• Hacking on Rubinius is fun!

Wow. I’ve been busy. More busy that I’ve ever been!

No blogging, no coding, no sleeping kind of busy! :-)

But, I’ve taken a little bit of time to work on Rubinius after spending a couple of days with Evan at RailsConf Berlin.

Want to know a secret? Working on Rubinius is really, really fun.

I had noticed that a YARV benchmark was failing when run under Rubinius. It turns out that Class#attr had never been implemented. That’s not surprising, as the Rubinius crew works on whatever they need at the moment, in true agile fashion.

So, I checked out the code using git (hang in there, it gets easier once you’ve used it a bit!), got Rubinius built on my trusty MacBook, and fired up TextMate.

I probably spent about 8-10 hours implementing the patch. In the end, I ended up refactoring the entire attr_* family to DRY them up a bit.

One of the coolest things about Rubinius is that I implemented all this in Ruby. Yes, I wrote part of the Rubinius implementation in Ruby! How cool is that? I think it’s really cool because I simply don’t have the C chops (anymore!) to even begin to help if C was required.

The next cool thing was learning a tiny bit about spec based testing. You see, since the Rubinius project has rather significant spec coverage, I absolutely knew when I was done and ready to commit, because the spec tests were passing, where they didn’t before. This made it really easy to get started!

So, I’m really quite jazzed about this! Why? Well, for a couple of reasons:

1) Rubinius is progressing! A really good Ruby implementation draws near, and I helped, albeit in a very small way. Rubinius is very much a building block sort of project, however, so my work will help others out. In fact, I already talked to someone in the #rubinius IRC channel (irc.freenode.net) that had taken a few stabs at attr, because he needed it working to work on what he wanted to work on.

2) Someday soon, this little bit of code has a good chance of skyrocketing to the top of my “most used code” list. Think about how many uses of attr, attrreader, attrwriter and attr_accessor will use this code in the future! :-)

So, I’m off to bed. It’s late, but I’m happy. For the first time in quite a while, I feel like a bit of a hacker again!

Below are the highlights from our October 4th customer conference call.

• C2 Load Balancer fix with less than 5 minutes of interruption on October 2nd.
• We had a successful maintenance/upgrade last weekend for our private cluster customer Zaadz.
• Our two new support staff members Lee and Taylor are ramping up quickly and we will be bringing on two more shortly.
• We will be replacing our ticketing system soon with a much more user friendly and effective system.
• Tom discussed Rubinius and it’s potential.

General News:

• Our new customer Food Moves had some very positive comments for us. Thank you.
• We announced two new support staff members Lee and Taylor. Welcome!
• We will be looking at several new data centers in Missouri and the UK for our next clusters.
• Engine Yard has secured a new office in San Francisco and several of our members will be relocating there.

Maintenance Updates:

• The maintenance for C1 on 9/23 went very well and C1 now has new load balancers improving stability.
• The maintenance upgrade for C2 went very well also and now has two more nodes added on.