puppetmanaged.org http://www.puppetmanaged.org en Welcome to puppetmanaged.org http://www.puppetmanaged.org/welcome <p>Welcome to the (new) website of <a href="http://puppetmanaged.org">puppetmanaged.org</a>, a project by the <a href="http://www.ergo-project.org">Ergo Foundation</a> (<em>Stichting Ergo</em>).</p> <p>Here you will find a set of modules for <a href="http://projects.reductivelabs.com/projects/puppet/wiki">Puppet</a>, the next generation of Enterprise Configuration Management suites by <a href="http://reductivelabs.com">Reductive Labs</a>.</p> <div class="og_rss_groups"></div> Sat, 20 Mar 2010 12:43:04 +0000 jmeeuwen 3 at http://www.puppetmanaged.org Puppet Common Modules http://www.puppetmanaged.org/articles/2010/03/20/puppet-common-modules <p><a href="http://puppetmanaged.org">Puppetmanaged.org</a> is a collection of modules for <a href="http://projects.reductivelabs.com/projects/puppet/wiki">Puppet</a>, the next-generation enterprise configuration management suites. When we say "configuration management" however, we are not talking about the ITIL or ITSM configuration management. Read more on what configuration management also means.</p> <h2>The Value of Modules</h2> <p>Using modules for Puppet can help you in a variaty of ways. For one, modules are supposed to be portable between different environments because they let you adjust the exact configuration applied to a node. The portability allows efficient development, and effective deployment. Secondly, environments that apply configuration management through the use of modules are often more consistent, which makes all of our lives a lot easier.</p> <p>When using modules however, you would want to choose to share that module with others, so that the module may evolve and become better, while helping others solve their problems very efficiently as well.</p> <p>Some will argue that Puppet modules you get from the Internet will never work exactly the way you want them too, but luckily some of the module developers use the Open Source development model; you can contribute back –and you should.</p> <p>Modules for Puppet can be created using three different approaches, or a mixture thereof:</p> <ol> <li><a href="#file-based-distribution"><strong>File-based Distribution</strong></a><br />Override anything on a per-file basis, putting the right configuration file in the right location on the Puppet master.</li> <li><a href="#module-function-logic"><strong>Module Function Logic</strong></a><br />Set variables (in the node manifest) to influence the end-result (file) that is generated from a template.</li> <li><a href="#per-setting-augeas"><strong>Per Setting</strong></a><br />Let Puppet control only some settings in a configuration file through Augeas, leaving the rest of the (original) file intact.</li> </ol> <p>There is something to say for each of these methods. Each of them may have its advantages and disadvantages. Also, none of these different types of approaches is mutually exclusive with any other approach. However, I would recommend that you stick with one single approach for an entire environment as much as you can.</p> <p>A given module (including those from puppetmanaged.org) using either of the aforementioned approaches can still include one or two types using the other method. For example, the puppetmanaged.org <a href="http://git.puppetmanaged.org/?p=webserver;a=summary">webserver module</a> allows you to specify a template for a webserver's virtualhost.</p> <div class="og_rss_groups"></div><p><a href="http://www.puppetmanaged.org/articles/2010/03/20/puppet-common-modules" target="_blank">read more</a></p> Sat, 20 Mar 2010 12:32:13 +0000 jmeeuwen 2 at http://www.puppetmanaged.org