Infrastructure deployment with Puppet

After few months of hard work with new approach to infrastructure deployment I can say that the choice of using Puppet was very good. We reached our goals like:

  • master-agent and masterless deployment,
  • model our physical infrastructure into hiera,
  • store facts, reports, exported resources, catalogs for each machine into PuppetDB,
  • easily split common puppet classes/resources to public repos and specific resources e.g SSL, apps configs into private one,
  • TDD using serverspec. Continuous integration with Travis
  • and many more...

If you are interested in puppet please have a look on open source set of puppet modules with my huge contribution at Github


Related posts

Mongo MMS API agent for ruby with basic cli client

During last two days I have developed very minimalistic the Mongo MMS API ruby client which is easily extendable as mms-api gem (source code on github so please contribute). The client is used by me to extend Pulsar (capistrano) tasks…

Extending Puppetmaster module with Passenger

If you manage large farm of servers then most probably you experienced performance problems time to time. To solve puppetmaster problems with handling many of concurrent SSL connections the best solution is switch from WEBrick to Apache2 as gateway for…

Migration to Heroku App Cloud with UptimeRobot monitoring

After few hours of playing with Heroku and UptimeRobot I decided to move my blog (WordPress) and website (PHP) to new hosting cloud. So now it is running for free. Hopefully will be stable... Useful resources: