So on Monday in the middle of the day all of my systems upgraded to 3.0. Before I go to far into this blog I want to explain that this was my fault. The puppet module that controls the version of puppet which is installed on each of my clients is set to “ensure =>
So I decided to release this bit of code I wrote which allows you to leverage mongodb as an ENC for puppet. I am not yet sure if this is a premature move or not but I plan to be using it in production in the next few weeks. I have a list of features
I wanted to write a blog post about something that I assume other people might be struggling with when deploying applications to EC2. Specifically how do I tell my deployment scripts (fabric in my case) to wait until puppet has finished before moving on to actually deploying my application.
At this point you have to be asking your self if you should edit the puppet manifests on the puppetmaster, well the answer to that is “Heck No”. If you want your infrastructure to come to a screeching halt then by all means have at it but if you actually want to be able to
So now we have our systems up and running with Ubuntu 10.04 and next you want to make sure that some common configuration files are identical across your infrastructure. You also want to have specific components installed on specific servers, for instance you want your databases installed on your database servers, you want your applications