On Wednesday, 12 October 2011 at 13:44, Stu Teasdale wrote: > On Tue, Oct 11, 2011 at 02:13:36AM -0700, Lucian Holland wrote: > > I've been pondering something not dissimiliar to this recently, a sort > of "config introspection", for some of our live services (e.g. load > balancers). My initial thoughts were geared around collected resources, > but I'm not sure the model works well for them. We already use puppet > manifests to provide control info to mcollective, so feeding mcollective > discovery back into puppet might be an interesting way to do some of > this information gathering. The scope of what we're thinking about is a > fair bit smaller than the sort of holistic, whole system stuff Lucian is > talking about though. > (Hi Stuart!) Isn't this essentially what http://www.devco.net/archives/2010/09/18/puppet_search_engine_with_mcollective.php is doing using mcollective registration? Although it's very cool I wonder about having another fact store at another level of indirection from the original information (machine properties -> puppet -> yaml -> mcollective -> mongodb) - it feels a bit like a cache hierarchy without enough in the way of proper cache management. But I suppose that's a soluble problem with a bit of work.
Lucian -- Lucian Holland Sent with Sparrow (http://www.sparrowmailapp.com/?sig) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
