Author Archives: Jeff Blaine

Real DevOps Defined: Wonder Twins

I had a “how to define DevOps” revelation last night: It’s the Wonder Twins! Surely everyone remembers the Wonder Twins. You weren’t born before the 1980s? Oh. Well. Anyway… citing the Wikipedia article on Wonder Twins:

If the two are out of reach of each other, they are unable to activate their powers. […] A rarely-seen aspect of their powers is the ability to break mind control. […] The Wonder Twins have a pet Space Monkey called Gleek who had a useful prehensile tail and who could act as a conduit for the twins to activate their powers should they be out of reach.

Dibs on the name Gleek for a DevOps Practices enabling tool. And your manager should have his trait mentioned above.

Can we move on now?

A Missed Thank You

While brushing up on TCP today, ancient synapses fired leading me to recall my first forays into network programming in 1992. While on permanent hiatus from CS education at FSU, I took a very long cross-country train trip from Jacksonville, FL through Chicago to L.A. and back to Jacksonville, FL via Pittsburgh, PA. Ideally, the goal was to get away cheaply to spend time figuring out just what the hell the next step might be. Along the way, I stayed with people I had met on social MUDs. Continue reading

Memory-backed Filesystem for Temporary Storage of Whisper Data

Instead of buying and installing SSDs, storing Graphite’s whisper files in a memory-backed filesystem can be a good way to go if you have the RAM to spare. Depending on your environment, you may or may not care about losing a few minutes (or hours) of metric data. I know we certainly don’t care about losing 30 minutes, so there’s no reason for our carbon-cache instances to be scrawling to persistent storage 24/7. Continue reading

Documenting bash scripts

For those of us still in the bash trenches now and then, I learned you can avoid the hassle of hash/octothorpe (#) commenting blocks of documentation in your scripts by using a standard “here” doc prefixed by the no-op expression (:).

Clearly this is something you’d only want to do for major blocks of text, like a large documentation block at the start of a script.



My free-form documentation here.


Bootstrapping new Chef nodes without knife bootstrap

There may be a time when you don’t want to (or cannot) make use of knife bootstrap to set up a new Chef node or a whole fleet of hundreds of nodes. If that’s the case, and you already have a “hook” into the hosts you want to turn into Chef nodes (such as an existing CM tool), you have an option. Continue reading