Hi,
my 2 cents below:
2016-09-04 22:32 GMT+02:00 Berkeley <berkeleychurch...@gmail.com>:
> [...]
>
> :hierarchy:
> - "fqdn/%{clientcert}"
> - "env/%{environment}"
> - "roles/%{role}"
> - "os/%{osfamily}
> - common
>
>
> I should add that I'm very comfortable writing ruby code, but for
> something so basic I don't feel like I should be trying to write custom
> facts. Even a simple way to just specify, per-node, an extra fact I could
> use for hiera's hierarchy would be helpful.
>
I use https://forge.puppet.com/abstractit/puppet to define custom facts.
Then, in hiera, for each node I do something like:
nodeXYZ.yaml
facts::custom_facts: { role: sge_execution_node }
during the first puppet run, it creates the custom fact, the second, the
node know what role it is and does what its expected (same when you switch
roles in a node).
I prefer using a custom fact cause I can interrogate the node about its
role:
# facter -p role
sge_execution_node
I also use the role yaml file in hiera for including classes based:
role/sge_execution_node.yaml
---
classes:
- role::sge_execution_node
sge::node_type: 'execution'
Best,
Arnau
--
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/CAM69jx9Mod8c-z-Pd05DLR0hVt7qPxuV3Cj1LZnBdCfM6Z9MAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
