El 17/07/15 a las 09:31, bjoern pohl escribió:
Hi,
we're currently transforming some ugly perl-based management scripts
(which placed some config data on the client and then configured
something with it) to puppet.
While it is definitely the best idea point to keep all that config data
on the master ( using hiera, puppetdb, etc..) i am currently looking for
an interim solution to incorporate some of this local config data into
centrally managed manifests/classes.
Hiera is always using central hiera data while running the puppet agent
server-based and is not using any hiera files placed on the client by
default, is there some way to get around that ( perhaps with some kind
of a server->client precedence)? Hiera is installed on all clients.
Once you have to transform all your local configuration to yaml (or
other hiera backend), there is no difference storing this data into the
client or into the server. So, you could create a %{fqdn}.yaml file
(considering you have configure hiera to use yaml and %{fqdn} is in the
hiera hierarchy) and store it in the puppet server and all this
information will behave the same way it was place in the client.
Obviously, with this you can't use other hiera features such as reuse
and the hierarchy, but it could a first step for you migration.
--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868887590
Fax: 868888337
--
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/55AC9594.7020308%40um.es.
For more options, visit https://groups.google.com/d/optout.
