----- Original Message ----- > From: "R.I.Pienaar" <r...@devco.net> > To: puppet-dev@googlegroups.com > Sent: Thursday, June 28, 2012 4:49:20 PM > Subject: Re: [Puppet-dev] Export and collect data, not just resources. > > > > ----- Original Message ----- > > From: "Luke Kanies" <l...@puppetlabs.com> > > To: puppet-dev@googlegroups.com > > Sent: Thursday, June 28, 2012 4:42:13 PM > > Subject: Re: [Puppet-dev] Export and collect data, not just > > resources. > > > > > > > >> On Jun 22, 2012, at 12:48 PM, Andrew Forgue wrote: > >> > >> > >> On Wednesday, June 20, 2012 9:24:20 PM UTC-4, Ryan Bowlby wrote: > >> > >> We solved this problem using Volcane's registration system. It's > > > > What are the problems with this approach? > > > > > > Are there functions you use beyond 'search_nodes'? > > > > > > If you look at all of your search_nodes functions, are they similar > > calls, or do you have a wide variety of types of calls? > > the ones I wrote supports simple class and fact matchers and returns > just a list of nodes.
Actually just to clarify this is not quite correct - the search hash gets passed direct to MongoDB and its query language is very complete. Additionally the data in the MongoDB that gets fed from MCollective is data from a user provided plugin - so you can literally chuck anything in there keyed to the fqdn and search against it. The load_node() function will fetch everything there. By default this is facts, classes, collectives a node belong to and list of agents installed on that node but this is not a limitation, u can put anything in there -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
