On Tue, Mar 20, 2012 at 9:44 PM, Pablo Fernandez wrote:
> **
>
> Thanks,
>
>
>
> Yes, I was thinking about something like:
>
>
>
> :hierarchy:
>
> - %{fqdn}
>
> - %{secundary_group}
>
> - %{primary_group}
>
> - %{productname}
>
> - all
>
>
>
> So, each machine goes and picks up the information fro
Thanks,
Yes, I was thinking about something like:
:hierarchy:
- %{fqdn}
- %{secundary_group}
- %{primary_group}
- %{productname}
- all
So, each machine goes and picks up the information from the more specific to
the more generic group. So, I guess if the fqdn.yaml file is not there,
Hi Pablo,
I have done a number of on-site consultations and implemented Hiera with
very positive results. To answer a couple of your questions:
1. You don't NEED to have a YAML file for every node in your
infrastructure, but if you need to overwrite values that are set at lower
levels of the hi
Hi,
After some time playing with Puppet, I came to realize simple node inheritance
with includes is not enough, and you may experience unwanted results. Then I
started playing with the External Node Classifier that Puppet Dashboard brings
in, and even though they implement node groups the way o
