Hello, On Thu, Aug 02, 2007 at 07:09:45PM +0200, Gabriel Mateescu wrote: > I gather that a configuration file needs to be generated with mds- > gluerp-configure > (which is similar to the procedure for adding support for Ganglia).
Yes, it can be based on that configuration generator. > However, this page does not mention modifying the file > etc/globus_wsrf_mds_index/server-config.wsdd, which is used to add > support for Ganglia (only other files, such as cluster_config.xml and > scheduler-info.xml, are discussed). > > I would like to ask the following: > > 1. How should etc/globus_wsrf_mds_index/server-config.wsdd > to add support for NAGIOS? The DefaultIndexService config block needs to be replaced with the following: http://www.globus.org/toolkit/docs/4.0/info/usefulrp/developer/developer-index.html#usefulrp-developer-config [ NOTE: This is true for any information provider using the RPProvider framework. This config change enables it. ] > 2. Is it possible to have both NAGIOS and Ganglia cluster > information > providers enabled simultaneously? Sort of. You can't have both NAGIOS and Ganglia both reporting the GLUECE RP alongside a scheduler provider. However, you can add a new config block to the gluece-rpprovider-config.xml file that can report either NAGIOS OR Ganglia as a different RP while the other is being reported as the GLUECE RP. > Given that there is only one entry <service > name="DefaultIndexService"> > in etc/globus_wsrf_mds_index/server-config.wsdd, supporting > multiple cluster > providers seems to require either a fil gluece-rpprovider- > config.xml > defining multiple providers, or that the parameter > <parameter name="rpProviderConfigFile" > > in etc/globus_wsrf_mds_index/server-config.wsdd is a list of > files. No, don't modify that parameter in the server-config.wsdd. The gluece-rp-provider-config.xml can have as many entries as it needs. If you have trouble with the syntax, I can attach an example. -Neill.
