On 3/20/2013 3:37 PM, Andy Parker wrote:
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast <[email protected]
<mailto:[email protected]>> wrote:
My Hiera tree is turning into a chaotic mess. I'm guessing that my
tree structure is one problem source. So I'm wondering how other
real users have setup hiera. Here are the core problems that are
giving me headaches.
I'd be interested in seeing some of these as well. I'm looking for real
world examples of what people are putting in their hierarchies that we
might be able to make better in a hiera 2, which is something that my
team is looking at working on.
We've been using this hierarchy for the last couple of months.
---
:hierarchy:
- %{clientcert}
- %{environment}/%{role}/%{calling_module}
- %{environment}/%{role}
- %{role}
- %{environment}
- common
:backends:
- yaml
- json
:yaml:
:datadir: '/home/puppet/etc/environments/%{environment}/hieradata'
:json:
:datadir: '/home/puppet/data/%{environment}/hieradata'
Couple of notes.
We have processes that publish data via json so that versions are
always correct in Puppet if new machines are spun up. Most of the data
is in environment, role, and env/role. clientcert (aka fqdn) and
calling_module are mostly to deal with internal test systems or one off
machines. IIRC calling_module doesn't work in Puppet 3.x.
Ramin
--
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.
