Hi Wolf,
At the top of the hierarchy, yes (the hash merge is done top to bottom,
where the top is the highest of the hierarchy, see mine below). I have
this in place already and you're right it will work elegantly, however
it moves the 'decision' of what to do into Hiera and you have to "know"
Hi Luke,
Would adding fqdn to the bottom of your hierarchy give you the ability to
override the values on the outliers that you can't automagically set while
retaining elegance in your class? Or am I missing something?
Wolf Noble
Datapipe Managed IT Services
On May 11, 2012, at 12:45 PM, J
I have a similar issue with Hiera when decisions depend on more than facts
alone... thus exluded from the hierarchy.
In example, the hostname can tell a node is a database server (fact: role)
but only a custom group will tell it should run Oracle 10g or 11g (product)
and the proper sysctl t
I see (and I saw your post on create_resources - I tested it out and also
noticed that inheritance didn't work as expected for me either). My
initial thought would be to try and break down the individual sysctl
entries as individual resources that could be declared with a defined type
(as Aaron me
I suppose you could create a separate class for the entries that will
be fact-driven versus Hiera-driven. You wouldn't be able to use a
single template, but either augeas or concat should work. I wouldn't
call it elegant, but the code might be less ugly.
On Fri, May 11, 2012 at 9:47 AM, Luke Big
Hi Gary,
Not quite... Let me go into more detail.
I'm trying to handle sysctl "perfectly" which is probably my real
problem. Hiera's ability to merge hashes together makes it perfect for
arriving at one set of sysctl options for a server based on "business
logic" (my hierarchy). For Hiera da
I see this with people looking to move to the hierarchical system that
Hiera brings. It essentially boils down to "How do I do this without
having a ton of hierarchy levels?". Usually we tend to recommend using the
hierarchy to hit the 80% mark for the data you need in your modules.
Anything tha
Hi all,
I've been improving our sysctl module and come across an interesting
design problem I'd like feedback on.
I approached the re-factor with Hiera in mind - I would put all our
sysctl data in Hiera hash and pull that into a hiera_hash, merging the
hierarchy of data and allowing higher p
