On Mon, Oct 11, 2010 at 06:44:20PM -0700, Philip Brown wrote: > BUUT... maybe I am thinking about this all wrong after all. Possibly > the better way is to give facter a custom set of facts... and then > since facter output gets automatically stored on the master when > puppet runs on the client
If you're running storeconfigs, which isn't a given for everybody, not least because it can cause scaling problems of its own (memcached backend for storeconfigs will be such a win). >, that would be a better source for the > repository...? If the data you are feeding back really is directly relevant and important to your puppet configuration rather than incidental, then yes. If you hit scaling issues, though, you'll either need to be looking to an alternative method of delivering and storing the data that does scale well or enhancing your puppet infrastructure (the mcollective suggestion was a good one). Is it crucial that the data be current at the beginning any puppet run? Is the data itself used in configuring the host, or is it just the presence of current data that has an effect on how/when puppet runs? -- Bruce Explota!: miles de lemmings no pueden estar equivocados. -- 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.
