deft-39.md

Puppet Camp Melbourne

• check out Puppet Forge
• upgrade to Puppet 3.0 ASAP
  • big performance and memory handling improvements over 2.7
  • Hiera used internally

Puppet for sysadmins

• Puppet can write puppet
  • how?
  • might try switching to this…
  • puppet resource user blah | puppet apply -
  • using “puppet resource …” to install packages, setup users etc. platform indepedently from the commandline
• dot for dependency diagrams
• puppet doc file.pp
  • should make more of an effort to document manifests!

Love / Hate Puppet

• Type Casting
  • is weird, so learn (implications for comparisons in Hiera)
• check his blog thatbytes.co.uk
• destroyallsoftware.com/talks/wat
• look at exported resources
• really look at Hiera
• wonder how use Puppet to manage Route53 records
• static data bad, time to use Hiera and PuppetDB
• interesting puppet edge cases

Company Culture for Competitive Advantage

• more formalised first day induction
  • deploy on their first day, a–la Facebook
• cross–skilling
• embed an engineer in your dev. team
• extracurricular hacks—barrista, good food, company sport
• hack days, on stuff unrelated to work
• flexible working conditions, no 9–5
• measure happiness? actual metrics

Build and Test Environment Configuration with Puppet—“Infrastructure as Code”

Gist is that puppet is good for setting up “development” and “production” environments.

“Infrastructure as Code”—treat manifests as such, with tests and whatnot. Vagrant to setup a puppetmaster to test your puppet changes.