I can't begin to describe how helpful it is to read this. I also started 
down the same path using a profile::base. A slightly different setup where 
all other profiles inherited from ::profile::base. Luckily, shortly after 
going down this path I ran into a major roadblock (better now than 9 months 
in) when I tried to override a value from profile::base in another profile. 
Can't really be done. Puppet Support also pointed me in a similar direction 
as Ramin using custom facts. 

I really wish there was more guidance on this from Puppetlabs. When reading 
through learning sites and documentation, the first thing you read is that 
Roles/Profiles are the be all end all. Then you find out you actually don't 
want ANY data in code. So you have to go rewrite your all your profiles you 
already wrote, to work with hiera. In my opinion, the lack of guidance in 
this area is the single biggest barrier to deploying Puppet. Actually 
writing the code is fairly easy. The issue is finding the best place to 
organize the code. Most of the examples from Puppetlabs (or the blogs 
written by puppet employees before they were) are over-simplified and tend 
to lead down a path that's a dead-end. I'm not a professional developer, 
I'm a sysadmin simply trying to puppetize my infrastructure. There is a lot 
of work to be done in clearing this up for those of us who don't develop 
for a living. In my honest opinion.

On Friday, August 30, 2013 6:48:37 PM UTC-4, Frederiko Costa wrote:
>
> Hi everyone,
>
> Do you guys know any article/doc talking about the use of roles/profiles 
> approach with hiera?
>
> I'm particularly interested in how to organize the manifests when having 
> multiple data centers, parametized classes and wants to use hiera. 
>
> Being even more specific, how to organize the code using the Craig's 
> article (http://www.craigdunn.org/2012/05/239/) and use hiera to  provide 
> node specific data.
>
> thank you,
> -fred
>
>  

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ca33d5be-5f90-4c90-afd1-1dd154699516%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to