On Jan 11, 1:05 am, Carles Amigó <fr...@fr3nd.net> wrote: > What data is exactly discarded with "thin" storeconfigs?
Effectively only facts and exported resources are stored for each node[1]. This is opposed to storing the complete set of resources (and other stuff?) for each node. For normal puppet usage there's no loss to using thin_storeconfigs. The full set is useful if you want to query it as part of an external process. A monitoring or inventory service, for example. Bryce F did most of the work that actually made storeconfigs useful. There are some very good posts on his blog[2]. [1] http://docs.puppetlabs.com/references/2.6.3/configuration.html#thinstoreconfigs [2] http://www.masterzen.fr/tag/storeconfigs/ On Jan 11, 1:47 pm, Adrian Bridgett <adrian.bridg...@gmail.com> wrote: > It may also be worth looking at some form of improved scheduling in > order to avoid a thundering herd of requests to your puppetmasters. Using a cron resource with fqdn_rand() interval works pretty well and is dead simple. cron { puppet_agent: command => 'puppet agent -- onetime', minute => [fqdn_rand(30), (fqdn_rand(30) + 30)] } -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
