puppet
Puppet errors explained
Puppet is a wonderful system automation tool, however the learning curve can be a little steep. We've collected some of the errors messages and "strange" behaviour you may come across together with explanations to help overcome these hurdles and boost adoption of this fabulous tool.
If you have any useful errors and explanations, please do send them in and we'll update this article.
General Puppet errors
These errors happen on current or popular versions of Puppet.
Puppet dashboard - early days
Reductive Labs, who produce Puppet recently released an early version their dashboard tool. You can have a look at their brief tour as well as the code repository and documentation site which is here.
It's clearly early days both in terms of the dashboard (v0.2.1) and in terms of our experience with it. To be frank in it's current state it's a pretty tool however it lacks a large amount of functionality which would make it actually useful.
Puppet quickstart - automate your server administration
Puppet is a class-leading automation tool which allows rapid but well controlled changes to your server estate and configuration.
Using it, your system administrator(s) will be able to automate the many tasks that can consume time and often rely on accurate input of critical settings. Using it well depends on automating the right things and learning the basic capabilities. So although you can get hold of Puppet easily enough, it can be tricky to put the correct structure in place and give you a gentle introduction to the process.
Another week, some more packages (facter, openssh, sudo), Linux LDAP integration
One of our puppet rules ensures that NTP (which ensures that the server has the correct time) is not installed on any virtualised guest images where the time is supposed to be taken from the host automatically. Unfortunately "facter" which should provide this information still hasn't applied patches submitted over 6 months ago. So we've rolled our own package instead for use on Debian Lenny.
Puppet - 2 year anniversary
It's been two years since we started using puppet in a production environment and it's worth taking a step back to see the big picture.
What's worked well? Firstly puppet is still around and very active. Reductive Labs (who develop puppet) just closed their first funding round. Old setups from two years ago still work just as they always have done.
Puppet introduction
We use many tools here at bitcube, however one has made a bigger impression than any other and we believe it gives us the edge over other companies. That tool is Puppet.
Puppet allows us to set up "recipes" on a central "puppetmaster" machine. All the servers we look after use then use these recipes to ensure they are set up correctly.
