Bug 3017 - RFT auto-registration doesn't register enough resource properties
: RFT auto-registration doesn't register enough resource properties
Status: RESOLVED FIXED
: RFT
RFT
: development
: PC Linux
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-03-26 19:24 by
Modified: 2005-03-27 19:25 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-03-26 19:24:55
This is what webmds shows about RFT resources:

  0 active transfer resources, transferring files.
  bytes transferred in files since start of database.

Both webmds and the container was install from trunk last night.
------- Comment #1 From 2005-03-26 19:44:43 -------
When creating the summary line, WebMDS looks at four RFT resource properties: 
ActiveResourceInstances, TotalNumberOfActiveTransfers, NumberOfBytesTransferred,
and NumberOfTransfers.  It looks like when the RFTFactoryService starts up, it
only advertizes ActiveResourceInstances, and not the other three.
------- Comment #2 From 2005-03-26 20:02:24 -------
I have RFT resource which has been up for a long time being presented the same
way. Querying the service also shows more info:

[rynge@devrandom ~]$ wsrf-query -s
https://128.9.72.178:9000/wsrf/services/ReliableFileTransferFactoryService
<ns0:RFT_RP_SET xmlns:ns0="http://www.globus.org/namespaces/2004/10/rft"
xmlns:ns1="http://mds.globus.org/metadata/2005/02"
xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:ns3="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:ns4="http://schemas.xmlsoap.org/ws/2004/03/addressing">
 <ns1:TotalNumberOfTransfers
xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">66365</ns1:TotalNumberOfTransfers>
 <ns1:ActiveResourceInstances
xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">0</ns1:ActiveResourceInstances>
 <ns1:DelegationServiceEPR xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">
  <ns2:Address
xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/03/addressing">https://128.9.72.178:9000/wsrf/services/DelegationFactoryService</ns2:Address>
  <ns3:ReferenceProperties
xmlns:ns3="http://schemas.xmlsoap.org/ws/2004/03/addressing"/>
  <ns4:ReferenceParameters/>
 </ns1:DelegationServiceEPR>
 <ns1:RFTFactoryStartTime
xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">2005-03-27T02:00:16.954Z</ns1:RFTFactoryStartTime>
 <ns1:TotalNumberOfActiveTransfers
xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">0</ns1:TotalNumberOfActiveTransfers>
 <ns1:TotalNumberOfBytesTransferred
xmlns:ns1="http://www.globus.org/namespaces/2004/10/rft">666568577</ns1:TotalNumberOfBytesTransferred>
 <ns1:ServiceMetaDataInfo>
  <ns1:startTime>2005-03-27T02:00:16.961Z</ns1:startTime>
  <ns1:version>3.9.5</ns1:version>
  <ns1:serviceTypeName>unspecified</ns1:serviceTypeName>
 </ns1:ServiceMetaDataInfo>
</ns0:RFT_RP_SET>
------- Comment #3 From 2005-03-26 20:22:56 -------
Ah -- what's going on is that the aggregator source for the RFT factory service
is configured to query only for the ActiveResourceInstances property (you can
see a prettier version of this if you click on the detail line for the RFT
factory service in the webmds display):

<ns11:AggregatorConfig>
  <ns11:GetResourcePropertyPollType>
    <ns11:PollIntervalMillis>300000</ns11:PollIntervalMillis>
   
<ns11:ResourcePropertyName>rft:ActiveResourceInstances</ns11:ResourcePropertyName>
  </ns11:GetResourcePropertyPollType>
</ns11:AggregatorConfig>

The RFT factory should probably use the GetMultipleResourcePropertiesPollType
and get more resource properties (there's an example of this configuration for
RFT in $G_L/etc/globus_wsrf_mds_aggregator/example-aggregator-registration.xml).
------- Comment #4 From 2005-03-27 18:44:55 -------
I commited changes suggested by Laura. Let me know if it works well