In regard to: [Puppet Users] Hiera Tutorials, Kelsey Hightower said (at...:
> I'm beginning the process of creating Hiera tutorials covering the
> following topics:
>
> *Beginner*
>
> - Getting Started with Hiera (draft<
https://github.com/kelseyhightower/hiera/blob/maint/1.0rc/add_getting_started_tutorial/docs/tutorials/getting_started.md>
> )
> - Understanding hierarchies, sources, and scope
> - Understanding answer resolution (array, priority, hash, resolution
> order, etc)
> - Hiera and Puppet - Using the parser functions and data bindings for
> parameterized classes
>
> *Advanced*
>
> - Hiera backends -- Creating new backends
> - Hiera parser functions -- Creating new hiera parser functions
>
This is fantastic news Kelsey and I'm really looking forward to it.
We've been using hiera with the community edition for about 6 months,
and we're really happy with it, but we're really not using it to its
full potential yet.
One area where there's a dearth of documentation (and best practices
recommendations) relates to how to "namespace" settings within hiera.
What I mean is that when we converted from extlookup() to hiera, we
took the easy route, so we now have stuff in hiera that looks like:
nameserver_type: client
nameserver_primary: XXX.YYY.ZZZ.AAA
nameserver_secondary: XXX.YYY.ZZZ.BBB
nameserver_tertiary: XXX.YYY.ZZZ.CCC
Hiera would support something like
nameserver:
type: client
servers:
- XXX.YYY.ZZZ.AAA
- XXX.YYY.ZZZ.BBB
- XXX.YYY.ZZZ.CCC
in other words, more complicated data structures.
Both recommendations on whether or not that's a good idea *and* examples
on how to successfully access the nested bits from within puppet would
be appreciated.
Advanced examples with create_resources() might also be useful.
Thanks much,
Tim
--
Tim Mooney
Tim.M...@ndsu.edu
Enterprise Computing & Infrastructure
701-231-1076 (Voice)
Room 242-J6, IACC Building
701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164