are there places where we really want xcat to fulfill a single request with two different plugins?
the plugin_command code in xcatd and the copy of it in Client.pm will both route requests to every plugin that makes it into the handler_hash for that request's command. this is independent of the behavior that allows preprocess_request to change the requests for that plugin's process_request invocation (to slim down the noderange for service nodes, i guess?). i'm tempted to do one of two things: make it so either you can make a row in site that prevents multiple plugins from being called to fulfill the same request. allow the plugin to alter the actual request in plugin_command, probably with a callback like &do_request, only sent to preprocess_request. are either or both of these really objectionable? i'm not sure i understand the impetus for this multi-plugin behavior in the first place. thanks, - jonathan ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
