How to divide the rules in the manifestos?
I see some variants:
1. Write all rules in one file. It''s not good idea.
2. Write any manifestos like bsd.pp, linux.pp and do check on some
parameters in this manifestos.
3. Write manifestos for each machine, by hostname or IP.
4. Includeв in the site.pp all checks like this:
case $operatingsystem {
''sunos'': { include solaris/* } # apply the solaris
class
''redhat'': { include redhat/* } # apply the redhat class
default: { include generic/* } # apply the generic class
}
5. Something else?
What is true way?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/lNYZ1EVECW0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
On Monday, January 14, 2013 2:29:39 AM UTC-6, Евгений Верещагин wrote:> > How to divide the rules in the manifestos? > > I see some variants: > > 1. Write all rules in one file. It''s not good idea. > > 2. Write any manifestos like bsd.pp, linux.pp and do check on some > parameters in this manifestos. > > 3. Write manifestos for each machine, by hostname or IP. > > 4. Includeв in the site.pp all checks like this: > > case $operatingsystem { > ''sunos'': { include solaris/* } # apply the solaris class > ''redhat'': { include redhat/* } # apply the redhat class > default: { include generic/* } # apply the generic class > } > > 5. Something else? > > What is true way? >There is no one true way. However, Puppetlabs recommends, and Puppeteers around here seem generally to agree, that configurations managed by Puppet benefit greatly from being broken down into reusable modules that can be shared across all nodes that require them. OS-specific details are typically accounted for within such modules, instead of at a higher level such as your alternatives (2) and (4) suggest. You should consider looking at a few modules from the module forge for examples of how this can be done. Note also that Puppet modules often can be written so that most or even all manifest code can be shared across operating systems -- especially across different Unix operating systems. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/kux0CqRr_K0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
This might help, watch/read this from Ken Barber; Modern Module Development http://youtu.be/zNXSKv6987g http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-cam -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/OeR5THb3zp0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
OK, my alternative (4) contains all needed terms: a) I can write manifestos for diffrent groups of nodes (IP, OS, etc) b) I can collect terms for write it only once. c) I do not get confused in their own settings. понедельник, 14 января 2013 г., 19:40:28 UTC+4 пользователь jcbollinger написал:> > > > On Monday, January 14, 2013 2:29:39 AM UTC-6, Евгений Верещагин wrote: >> >> How to divide the rules in the manifestos? >> >> I see some variants: >> >> 1. Write all rules in one file. It''s not good idea. >> >> 2. Write any manifestos like bsd.pp, linux.pp and do check on some >> parameters in this manifestos. >> >> 3. Write manifestos for each machine, by hostname or IP. >> >> 4. Includeв in the site.pp all checks like this: >> >> case $operatingsystem { >> ''sunos'': { include solaris/* } # apply the solaris class >> ''redhat'': { include redhat/* } # apply the redhat class >> default: { include generic/* } # apply the generic class >> } >> >> 5. Something else? >> >> What is true way? >> > > > There is no one true way. > > However, Puppetlabs recommends, and Puppeteers around here seem generally > to agree, that configurations managed by Puppet benefit greatly from being > broken down into reusable modules that can be shared across all nodes that > require them. > > OS-specific details are typically accounted for within such modules, > instead of at a higher level such as your alternatives (2) and (4) > suggest. You should consider looking at a few modules from the module > forge for examples of how this can be done. Note also that Puppet modules > often can be written so that most or even all manifest code can be shared > across operating systems -- especially across different Unix operating > systems. > > > John > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/YqFrcWAJ4gIJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
понедельник, 14 января 2013 г., 21:54:32 UTC+4 пользователь Stefan Heijmans написал:> > This might help, watch/read this from Ken Barber; Modern Module Development > http://youtu.be/zNXSKv6987g > > http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-cam > >Thank you very much, but link to text is 404 :-( -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/XooTF3VPsn0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Jan 14, 2013 at 10:03 AM, Евгений Верещагин <e.vereschagin@gmail.com> wrote:>> http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-camThat should be: http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-camp Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Евгений Верещагин
2013-Jan-14 18:35 UTC
Re: [Puppet Users] Re: Plan the manifests structure
Yes! понедельник, 14 января 2013 г., 22:27:10 UTC+4 пользователь Josh Cooper написал:> > On Mon, Jan 14, 2013 at 10:03 AM, Евгений Верещагин > <e.vere...@gmail.com <javascript:>> wrote: > >> > http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-cam > > That should be: > > > http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-camp > > Josh > > -- > Josh Cooper > Developer, Puppet Labs >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_AjC7cKgi6kJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.