The hierarchy.xml file controls which servers Index Service resource
properties are propagated to, but it doesn't control which resource
properties are sent. By default, only the "Entry" resource property
(which is what is generally thought of as the index service data) is
sent. When you use usefulrp, you create and publish a different
resource property (the "resourcePropertyName" element of the resource
property config file specifies what this resource property name will
be). You can edit the index service upstream.xml to change the set of
resource properties sent -- basically, you'd want to change:
<agg:GetResourcePropertyPollType
xmlns:wssg="http://docs.oasis-open.org/wsrf/sg-2";>
<!-- Specifies that the upstream index should refresh
information
every 10 minutes -->
<agg:PollIntervalMillis>600000</agg:PollIntervalMillis>
<!-- specified that the upstream index should collect the
Entry resource properties from this index -->
<agg:ResourcePropertyName>wssg:Entry</agg:ResourcePropertyName>
</agg:GetResourcePropertiesPollType>
to
<agg:*GetMultipleResourcePropertiesPollType*
xmlns:wssg="http://docs.oasis-open.org/wsrf/sg-2";
*xmlns:/myns/="/http://my/namespace/"*>
<!-- Specifies that the upstream index should refresh
information
every 10 minutes -->
<agg:PollIntervalMillis>600000</agg:PollIntervalMillis>
<!-- specified that the upstream index should collect the
Entry resource properties from this index -->
<agg:ResourceProperty*Names*>wssg:Entry</agg:ResourceProperty*Names*>
*<agg:ResourcePropertyNames>/myns/:/MyRPName/</agg:ResourcePropertyNames>*
</agg:*GetMultipleResourcePropertiesPollType*>
using the appropriate values for your namespace and resource property name.
-- Laura
Shayan Shahand wrote:
Dear Neill,
Sorry to contact you directly, I thought it would be better to contact
you as my question is based on your tutorial at this link:
http://www.globus.org/toolkit/docs/development/4.1.2/info/usefulrp/usefulrp-howto-external-element.html
I wrote a simple bash script (based on fortune_script.sh) to gather
some system information and publish it in DefaultIndexService (the
script is attached: sysmon_script.sh and a sample output is also
attached : test.xml)
Then I edited $GL/etc/globus_wsrf_mds_index/server-config.wsdd and
$GL/etc/globus_wsrf_mds_index/rp-provider-config.xml as described in
tutorial.
The script works fine and publishes information on the
http://headnode:8080/wsrf/services/DefaultIndexService.
Then I set up the same script on 15 more containers on 15 other nodes
of a cluster (assume c0-0 to c0-15).
The script works fine on every single node and system information is
published on *MailScanner has detected a possible fraud attempt from
"c0-x:8080" claiming to be* *MailScanner has detected a possible fraud
attempt from "c0-x:8080" claiming to be
http://c0-X:8080/wsrf/services/DefaultIndexService*
<http://c0-X:8080/wsrf/services/DefaultIndexService>* as well.
Then I registered all these containers on
$GL/etc/globus_wsrf_mds_index/hierarchy.xml file on the headnode (as
upstream).
But when I try to query the aggregated information on the headnode,
only the local sysmon information is available.
I can see the GRAM and RFT and JobManager info (and not sysmon info)
from other containers so the upstream is working.
[a sample unformatted xml from the headnode: headnode.xml and from a
cluster node c0-0.xml is also attached]
Could you please help me to publish sysmon information from other
containers on the headnode too?
one more question: is it possible to define more than one <parameter
name="rpProviderConfigFile"
value="/etc/globus_wsrf_mds_index/some-other-rp-provider-config.xml"/>
in the $GL/etc/globus_wsrf_mds_index/server-config.wsdd? I tried to
keep both Ganglia and sysmon configuration but only the last one
appeared on the IndexService.
Many thanks
Regards,
Shayan
PS. of course if anyone else knows how to solve it, he/she is most
welcome :)
*
