On Wed, Jan 9, 2013 at 2:08 PM, Craig Dunn <cr...@puppetlabs.com> wrote: > The point was not a 1-1 mapping between nodes and roles (although that was > mentioned), the key point I was trying to make is to add layers of classes > to provide abstraction between your node definition (whether thats in an ENC > or site.pp) and the components that get pulled in.
So what's the advantage of managing roles explicitly in Puppet as opposed to managing them in an ENC of some kind? I get the re-usability point (you can swap out ENC, use node definitions, etc). Is that all? > I have two modules called 'roles' and 'profiles', And as I mentioned I find profiles to be quite useful. Its the role concept that I'm not necessarily > * A role contains business logic Could you give an example here? What else are roles, but a flat collection of profiles? Thanks, Roman. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
