Thanks and I'm glad it helped point you in the right direction. Here
are two more (from me at least) to add to your collection on
role/profile and Hiera. And yes I feel your oversimplified example pain.
It's very unhelpful though Puppet is better than most projects.
https://ask.puppetlabs.com/question/5235/what-goes-in-the-profile-part-of-roleprofile/
https://ask.puppetlabs.com/question/3146/how-to-build-a-proper-hiera-hierarchy/
What goes in profile? is the basis of my proposed Puppet Conf talk.
With any luck that will be accepted and force me to spend the 40+ hours
getting it out of my head and into a coherent presentation. Now I'm
thinking I should have called it "If you're not embarrassed of your
profile:: manifests you're doing it wrong!"
I agree that documentation is lacking, but there are some mitigating
circumstances. Parameterized classes, Hiera, role/profile, and automatic
lookup of parameters in Hiera only recently arrived on the scene.
Without all parts and some community consensus the way forward was still
unclear in my opinion. And I say that as someone who went down every
blind alley from 0.24 on. As always good ideas usually appear obvious in
hindsight.
On the flip side I was surprised with just how little reference to
role/profile there was on *.puppetlabs.com. You might consider opening a
Documentation bug to create a Role/Profile doc or at least collection of
the 20-30 external links that most people refer to in one place.
Ramin
On 3/27/2014 7:07 PM, Mike Lehner wrote:
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/
<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 puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ca33d5be-5f90-4c90-afd1-1dd154699516%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ca33d5be-5f90-4c90-afd1-1dd154699516%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/533507EB.3030303%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
