{"id":2955,"date":"2013-02-03T17:02:47","date_gmt":"2013-02-03T16:02:47","guid":{"rendered":"http:\/\/www.devco.net\/?p=2955"},"modified":"2013-02-03T17:02:47","modified_gmt":"2013-02-03T16:02:47","slug":"managing-puppet-using-mcollective","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2013\/02\/03\/managing-puppet-using-mcollective.php","title":{"rendered":"Managing Puppet Using MCollective"},"content":{"rendered":"
I recently gave a talk titled “Managing Puppet Using MCollective” at the Puppet Camp in Ghent.<\/p>\n
The talk introduces a complete rewrite of the MCollective plugin used to manage Puppet. The plugin can be found on our Github repo<\/a> as usual. Significantly this is one of a new breed of plugin that we ship as native OS packages and practice continuous delivery on.<\/p>\n The packages can be found on apt.puppetlabs.com and yum.puppetlabs.com and are simply called mcollective-puppet-agent<\/em> and mcollective-puppet-client<\/em>.<\/p>\n This set of plugins show case a bunch of recent MCollective features including:<\/p>\n It’s a bit of a beast coming at a couple thousand lines but this was mostly because we had to invent a rather sizeable wrapper for Puppet to expose a nice API around Puppet 2.7 and 3.x for things like running them and obtaining their status.<\/p>\n The slides from the talk can be seen below, hopefully a video will be up soon else I’ll turn it into a screencast.<\/p>\n\n