Puppet users - May 2014 - Craig Dunn's Roles/Profiles/Components & Conflicts

Hi all,

We use the roles/profiles/components model originally suggested by Craig 
Dunn fairly heavily.  In our case:


   - The role is a business name, like "Application X App Server"
   - The profile is the technical name, like "Base Components" or 
   "Webserver"
   - The components are either wrapper classes around modules or modules 
   themselves, like "PHP" or "Apache".

For the most part, this works well.  We can have, for example:


   - MyFace Application Server
      - Base Components
         - SSSD
         - Sudo
         - NTP
      - PHP Webserver
         - PHP
         - Apache
         - PHP-FPM
         - Memcache
      
However, we're running into trouble how to handle the situation where
you're
running a box with multiple functions... for example, WordPress and Drupal. 
 In that case, how do you handle configuration conflicts?  On the surface, 
it seems like we would create a more generic profile like "PHP
Webserver"
(like I did in the above example).  If I do this, however, I lose the 
ability to define profile specific variables such as firewall rules, cron 
jobs, etc.

Any thoughts on this?

Best,

Matt

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c1157f75-5a08-4e13-8739-abef8bd23cf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.