Background In Bootstrapping and Rooting Documentation: Part 1, I laid out a blueprint for using documentation as the bootstrap for entry into an operations environment. In this article I will dig into the three main concepts mentioned in Part 1. In Part 3, I will demonstrate our use case for a data center of about
Last week Ksplice announced free no-reboot kernels for Fedora which sparked off some interesting conversation about uptime over at the Standalone Sysadmin. Honestly, I ran across Ksplice a while back and I thought to myself, huh that might be useful for a certain niche, I added to a wiki page that I use to track
Bootstrapping and rooting are two concepts often associated with computing, but not the documentation of computing environments. Sometimes concepts such as these are called design patterns and I would like to try and introduce a new pattern called Documentation Bootstrapping. I think this is a critical pattern for the creation of any successful and useful documentation.
Background Scripting & Automation has been a goal since the beginning of Unix and, let me state, that I believe that it is possible to achieve a Fully Automated Provisioning system in our production environments. In fact, I think it is essential that we develop fully automated provisioning systems to keep up with the rate
I will be giving an introduction to DevOps ((http://dev2ops.org/blog/2010/2/22/what-is-devops.html)) and the DevOps Toolchain ((http://code.google.com/p/devops-toolchain/wiki/DevOps)) at the Akron Linux Users Group (ALUG) ((http://groups.google.com/group/AkronLUG/web/alug-home-page)), held at the New Era Restaurant at 10 Massillon Rd. Akron Ohio (See map below) Often development and operations seem to have competing goals. Development is the gas, while operations is often perceived