You have 2 hierarchies, one flat that is the classifier that contains
fqdn.yaml; each "fqdn.yaml" defined what is the role of the current fqdn.
This hierarchy is filled when you deploy a server (via a webservice,
manually or what you want)
The 2nd hierarchy is what you have today.
Le 09/09/2014 23:02, JeremyCampbell a écrit :
I believe I understand 'Data Source Resolution' but it doesn't address
our issue unless I'm missing something. The question is how to assign
a role to a server so that we can use a new role level in our hierarchy.
On Tuesday, September 9, 2014 7:37:51 PM UTC+2, Poil wrote:
Hi,
I think this is what you want :
https://docs.puppetlabs.com/hiera/1/hierarchy.html
<https://docs.puppetlabs.com/hiera/1/hierarchy.html> "Data Source
Resolution"
We are replacing our ENC with this "full hiera" method
Best regards
Le 09/09/2014 11:34, JeremyCampbell a écrit :
We are implementing the profiles/roles pattern with hiera and
using hiera to assign roles i.e. hiera_include('classes').
Current hierarchy:
|
:hierarchy:
-"%{clientcert}"
-"%{environment}"
-global
|
We have several roles which require their own configuration data.
e.g. Firewall role, VPN role (each include several profiles). For
example, using the logrotate module we need to add different
defines for the Firewall role and the VPN role.
The most obvious solution is to create a new hierarchy level
e.g. "%{role}" but then we need to assign machines to a role
outside of hiera. I'm guessing the best way to do this is with a
custom fact during the initial provisioning but I'm not sure.
What would be the best solution for looking up role specific data
using the roles/profiles pattern with hiera?
Thank you for your time!
--
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] <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6510ddf4-2a0b-4a1e-abb8-8d0244ba48f3%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/6510ddf4-2a0b-4a1e-abb8-8d0244ba48f3%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b4b53515-8858-4419-be07-5d7aee9720dd%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/b4b53515-8858-4419-be07-5d7aee9720dd%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/540F6D41.1090204%40quake.fr.
For more options, visit https://groups.google.com/d/optout.
