← Prev in month ← Prev in thread

Mapping Service

From
Herbert Souza <>
Date
2006-06-16T20:27:52+00:00
ID
Thread
Mapping Service
<nmwg:message type="RegisterRequest"
              id="msg1" 
              xmlns:perfsonar="http://teste.test">
     
  <!-- Metadata is service info that other people can contact you with, it will
       be listed in the LS this way. -->     
     
  <nmwg:metadata id="meta1">
    <perfsonar:subject id="sub1">
      <psservice:service id="UDelMA1">
        <psservice:serviceName>UDel MA-1</psservice:serviceName>
        <psservice:accessPoint>http://stouel.edu:8080/services/RRDMA</psservice:accessPoint>       
 <psservice:serviceType>MA</psservice:serviceType>
        <psservice:serviceDescription>UDel 
 USA</psservice:serviceDescription>
      </psservice:service>
    </perfsonar:subject>  
  </nmwg:metadata>   
      
  <!-- Data is all of the capabilities (interfaces) you are monitoring, in the
       form of metadata blocks.  It is neccessary to wrap these in data blocks
       because they are measurement metadata (not service metadata)  -->        
    
  <nmwg:data id="data1" metadataIdRef="meta1">
    <nmwg:metadata id="meta2">
      <netutil:subject id="sub2">
        <nmwgt:interface>
          <nmwgt:ipAddress type="ipv4">xxx.xxx.xxx.xxx</nmwgt:ipAddress>
          <nmwgt:hostName>udel.edu</nmwgt:hostName>
          <nmwgt:ifName>eth0</nmwgt:ifName>
          <nmwgt:ifDescription>gigE</nmwgt:ifDescription>
          <nmwgt:ifAddress type="ipv4">xxx.xxx.xxx.xxx</nmwgt:ifAddress>
         
 <nmwgt:type>gigE</nmwgt:type>
        </nmwgt:interface>
      </netutil:subject>          
      <nmwg:eventType>interface.utilization</nmwg:eventType>
      <nmwg:parameters id="paramid1">
        <nmwg:parameter name="valueUnits">octets</nmwg:parameter>
      </nmwg:parameters>           
    </nmwg:metadata>
  
 
  </nmwg:data>
← Prev in month ← Prev in thread