Hi there,
I was going to ask exact same questions too.
I am also interested in how people solve these problems.
On Wednesday, 13 February 2013 23:17:40 UTC, Chad Huneycutt wrote:
>
> I have been following the various blog posts about the roles and
> profiles pattern for classifying hosts, and I like it. It doesn't
> provide a perfect fit for our infrastructure, but it is much better
> than the ad-hoc classification we do now. I have a couple of
> questions for those that use it, though:
>
> 1. Where are you putting your role classes and profile classes? A
> role module and a profile module makes sense to me, but it seems like
> something more tightly integrated with the Puppet DSL might be nice?
>
> 2. Assuming you have roles and profiles in modules, at what point do
> you specify the parameters to your modules? I am particularly
> interested in the answer to this question with regards to hiera. I
> find that I want to add roles and profiles to the hiera hierarchy, and
> I cannot come up with a way to do it.
>
> I think if hiera supported lookup by the class containing the hiera
> call, I could achieve what I want. For instance:
>
> class profiles::oneofmyprofiles {
> include myparameterizedclass
> }
>
> I would like to have a hiera.yaml like so:
>
> ---
> :backends:
> - yaml
> :hierarchy:
> - nodes/%{::hostname}
> - profiles/%{class_name}
> - common
> :yaml:
> :datadir: /etc/puppet/environments/%{environment}/data
>
>
> Am I just completely off-base?
>
> --
> Chad M. Huneycutt
>
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
