…scripted, both locally and in CI. We're currently using a solution with Vagrant and Puppet that lets us spin up consistently formatted build boxes.
Leaky Test State
In production, the agent starts once per process. However, in a test run, the agent might restart hundreds of times. We've had to take care to avoid a leaking state between tests. Otherwise we could …
…1.1.19, 1.5, 7, upgrades for Puppet and and many more bug and security fixes.
We've included the usual Brightbox Ruby deployment stack and our "next generation" Ruby 1.8.7 and 1.9.3 packages, as well as the latest passenger. A significant change from Lucid-based Brightboxes is that Ruby 1.9.3 is now the default , as Ruby 1.8.7 is end-of-life from June 2013. If you still require 1.8.7, the included ruby-switch tool makes …
I find it harder to validate exit codes (again and again and again) in bash than using a DSL (which is what Chef and Puppet essentially are). The code in your cookbooks ( Chef) or manifests ( Puppet) is certainly not faster than a shell script but a lot easier to read and more maintainable in the end.
Bash-scripting is not hard either, but in order to produce a set of scripts …
…example. This makes role assignments highly script-able, whether you're using Chef, Puppet, or Moonshine.
Fine-tuned for large environments
With the recent notification group changes and now roles, we're making monitoring easier for large environments. Our previous tools -- cloud keys and plugin copy-paste -- were useful, but it was easy for things to get out of sync. Roles our our answer for keeping monitoring in sync in large environments.
Roles in Summary
With Roles, we …
…Jesse Aukeman , about the different ways they're monitoring the success or failure of Puppet runs.
If you are like us, you are running some type of linux configuration management tool. The value of centralized configuration and deployment is well known and hard to overstate. Puppet is our tool of choice. It is powerful and works well for us, except when things don't go as planned. Failures of puppet can be innocuous and cosmetic, or they can cause production issues, …
Score +2 if you have used Chef or Puppet or other deployment automation tools,
Score - 5 if you generally use ftp to deploy applications,
Score +1 if you ride a bike,
Score +1 if you play an instrument,
Score +1 if you speak another language,
Score +1 if you paint, draw, sculpt, and build things,
Score +1 if you keep a blog,
Score +1 if …
Score +1 if you have usedor Puppet or other deployment automation tools.
Score - 5 if you've only used ftp to deploy applications.
Score +1 if you ride a bike.
Score +1 if you play an instrument.
Score +1 if you speak another language.
Score +2 if you are a dog or cat.
Let us know your score by sending an email to firstname.lastname@example.org . Tell us a bit about yourself, what you've worked on, what kinds of problems you like to solve. We'll follow up and …
Matthias Marschall wrote a great peice last week on the pitfalls of making manual changes to production systems. TL, ; Making manual changes in the heat of the moment will bite you at the most inopportune times .
The article finishes out with this suggestion:
You should have your configuration management tool (like Puppet or) setup so that you can try out possible solutions without having to go in and do it manually.
In my experience, this is the key to solving the problem.
…of managing an army of developer laptops. Theuses the and Puppet and has been in development for 6 months. It enables a developer to script a configuration for his laptop (e.g. , Ruby, , a text editor, custom aliases, etc) and have that configuration automatically installed on a new .