search for: puppetbestpractices

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

I''m sure everyone has read and committed the Puppet Best Practice to memory by now (I joke). One of the things I''ve written in there deals with trailing commas, which I adopted from the way I used to do multiline in Perl, but I''ve noticed that most people don''t tend to do that in Puppet. Should I revise this or should we all start using the trailing commas?

Hi, https://reductivelabs.com/trac/puppet/wiki/DocumentationStart https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction https://reductivelabs.com/trac/puppet/wiki/PuppetMasters https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice - Max

Puppeteers, One of the more ... interesting components of our configuration has been how we''re handling users. We don''t have an LDAP solution (yet), so we''re using Puppet to handle users. This isn''t overly complex, at least at first glance. We have three types of users. * System admins * Web developers * R&D developer The system admins have userids on all

Hi there, If I have a manifest with, say: node default { ..stuff.. } node mymachine { ..stuff.. } What would happen on mymachine: will the stuff in default be executed *as well as* the stuff in default, or only the stuff in mymachine? And, if the latter, should I move global stuff just to global scope outside of nodes? Thanks -Iwan

I''ve moved it to: <http://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Russ, Digant, *! Several times on the IRC channel I noticed people having problems getting to grips with the interaction of scopes when using template nodes[1]. Typically this looks thus: | node genericwebserver { stuff } | | node ''web01.example.com'' inherits genericwebserver { | $influence_genericwebserver =

I use a simple yaml file and and an external nodes script to express each of my nodes. What I''m trying to do is make sure that all individual data is expressed at the node level and not have anything in classes or modules that isn''t generic and shared. the example below works really well but I can''t express it via my external nodes, I have to bury it in a class (or

Hello, Is it possible to group many nodes together? Suppose I have a large number of machines that I all want to have the same config - rather than specify them as individual nodes each inheriting the same config, I''d like to say that a group inherits a config, and define the group elsewhere. Does this sort of construction already exist? Could it be cobbled together from what we

Another point of disparity between how I see others write Puppet manifests and the Best Practice that I''ve adopted at my institution is the use of quoting. In Puppet, you can get away with not quoting values or references if there isn''t a special character or a keyword being used (e.g. package { openssh: ...} or User[agirl]). However, even though that is possible, to make

Hi, I''m a new puppet user (thanks !) and I''m just looking at moving my homegrown manifest structure into something resembling the best practise guide at : http://www.reductivelabs.com/trac/puppet/wiki/PuppetBestPractice. It seems as if the structure here doesn''t map to the default puppet layout (and thus doesn''t work with the standard puppet config

...ce will be important as more and more people consider making shareable modules, etc (mostly the syntax stuffs -- file hierarchy doesn''t matter except for modules, which is already defined quite well in the Module Organization page). <http://reductivelabs.com/trac/puppet/wiki/StanfordPuppetBestPractices>

Because here in Puppet-land we''re all about self-reference and recursion, and because I actually have to give a talk at RubyConf next weekend about abusing self-reference, and because parent nodes aren''t considered harmful in my own world, I give you: http://www.codinghorror.com/blog/archives/000982.html I think it manages to somehow be both on- and off-topic at the same

Since I had my type development epiphany a couple of days ago, I''ve decided to write down my understanding of developing simple types, at http://reductivelabs.com/trac/puppet/wiki/PracticalTypes. I''d appreciate comments from people who already know how to develop types as to correctness, and also comments from people who are new to type development about whether it''s a