I’ve been working with puppet a lot in the last few weeks. I really enjoy this style of administration compared to “ssh in a for loop”. Its great to script things and I still do it but for maintaining configuration I don’t know if it gets much better than puppet. That being said I ran into a few issues today that had me splitting my head open on my desk, keyboard, pop cans and just about everything else I could reach.
I have to use windows for a few things at my new employeer. I’ve found a few programs that I just cant survive using windows without. Launchy – Gnome-do like launcher Quotefix – Properly bottom post when replying to emails IsoRecorder – Right click iso and burn Cygwin – Linux-like environment for Windows I still spend very little time in windows so its not too bad but when I am there not having access to those tools drives me batty.
Matt Simmons recently had another post that mentioned structured systems management. I find myself re-reading Ad-Hoc vs Structured Systems Management from time to time and I figure its time for me to chime in. First off, Michael Jankes’ post is one of my favorite blog post reads. Few posts do I ever re-read unless its tutorialesque. For a quick sidetrack one of those posts that I do return to when I deal with developers is The Joel Test: 12 Steps to Better Code.
Sorry for the spam just testing modifications to a plugin
A while back I wrote about using Apache as a dynamic reverse proxy. Anyone who has done even minimal research into web servers knows that Apache is the swiss army knife. It trys to be everything for everyone, and like a swiss army knife may not be as good as a more refined too at least as far as efficiency is concerned. Here is the situation. You have a single pinhole into your private network.
Ha! I have trapped you with my sensationalized headline. Or you didn’t read this just like I wouldn’t have :P. I don’t know about anyone else but I had to turn off some of my feeds over the past several days. I was sick and tired of all the Chrome OS posts filtering about the net. It’s not that I don’t think having google behind another linux platform is a bad idea.
Apparently I have had a caching issue on the blog for a while now. It should be fixed but if anyone notices that your feed is updating but the site is not feel free to drop me a line. Thanks to Warren Guy from planetsysadmin.com for letting me know.
I recently had to write an init script for our continuous integration systems remote build agent. Of course this agent is a java jar and does not write its own pidfile. On debian or gentoo (yes I used to rice it) this would not have been an issue. Both have and use start-stop-daemon in their init scripts. start-stop-daemon actually understands that not every process you might want to daemonize writes its own pidfile and thus gives you the ability to daemonize a process, capture its pid, and write a pidfile.
Recently I have been working on cleaning up our continuous integration enviornment. Continuous integration is pretty cool but don’t shoot yourself in the foot by making bad build plans and not being very specific about your build requirements. If you have a package dependancy for a build make sure you put it in your requirements. If you need specific access to a database to do fixture tests SPECIFY it. In the short term you can see the benefits of continuous integration without doing these things.
I know I’ve been absent. I am not appologising I’ve been adjusting to the new job and its been keeping me busy. I did notice that my traffic tanked around the 20th of May and pretty much stayed that way until June 9th. I don’t know where everyone went but I’m glad to have you back. I don’t really have any ideas for articles at the moment but I am working on some virtualization at work.