perfsonar development work

Hi Fausto,

That way to modify an existing entry you would have to pass the whole  
original request and the modification, basically making the id being  
the whole request. An entryId is just for simplification in the  
process of listing, modifying or deleting an entry.

Guilherme

Quoting Fausto Vetter 
<>:

> Hi,
>
> I suggest to entryId be ignored, once if exists and agenda like that
> just use it, other way, create it. Not based on Ids.
>
> Fausto
>
>
>  wrote:
>
> > Hi Guys,
> >
> > Before the release process started I was developing a cron-like    
> > scheduler for the CL-MP. The logical structure of the code is done,  
> >  I  now need to define the schemas for this communication. I have   
> > attached some examples of what I was thinking for the schemas,   
> > these are just  sketches, I would really appreciate your opinions.
> >
> > Some background: So CL-MP currently does on-demand measurements   
> > using  command-line tools. This new component allows the CL-MP to   
> > schedule  measurements using a structure very similar to unix cron.  
> >  The user  will request CL-MP to add the measurement he wants   
> > executed (in the  requestCron.xml example it's an owamp   
> > measurement) and the scheduling  information. The scheduled   
> > measurements will be identified by an  entryId (these will be   
> > unique in some way). The measurements results  are stored in a SQL   
> > MA. The user should be able to choose to which MA  he wants the   
> > data sent.
> >
> > In the examples I used different namespaces for each action, these   
> >  could be put inside the same namespace 'cron' and identified by a   
> >  'action' parameter. I've initially put the MA IP address as an    
> > attribute of the <nmwg:messsage> element, I think this was   
> > suggested  by Jeff before, but this isn't actually currently   
> > supported by the  nmwg schema. So maybe it should go also as a   
> > parameter in the cron  metadata.
> >
> > Any suggestions/comments are welcome!
> >
> > Thanks,
> >
> > Guilherme
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> > ------------------------------------------------------------------------
> >
> > <nmwg:message type="MeasurementRequest" id="msg1"
> >         ma="150.162.248.15:8080" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
> >         xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";
> >         xmlns:owamp="http://ggf.org/ns/nmwg/tools/owamp/2.0/";
> >         xmlns:cron="http://ggf.org/ns/nmwg/tools/cron/modify/2.0/";>
> >
> >         <nmwg:metadata id="owamp">
> >                 <owamp:subject id="sub2">
> >                         <nmwgt:endPointPair>
> >                                 <nmwgt:src type="ipv4" value="1.1.1.1" />
> >                                 <nmwgt:dst type="ipv4" value="2.2.2.2" />
> >                         </nmwgt:endPointPair>
> >                 </owamp:subject>
> >                 
> > <nmwg:eventType>http://ggf.org/ns/nmwg/tools/owamp/2.0</nmwg:eventType>
> >                 <owamp:parameters id="param2">
> >                         <nmwg:parameter name="direction">to</nmwg:parameter>
> >                         <nmwg:parameter name="count">5</nmwg:parameter>
> >                         <nmwg:parameter 
> > name="portRange">2500-2999</nmwg:parameter>
> >                 </owamp:parameters>
> >         </nmwg:metadata>
> >
> >         <nmwg:metadata id="cron" metadataIdRef="owamp">
> >                 <nmwg:eventType>
> >                         http://ggf.org/ns/nmwg/tools/cron/modify/2.0
> >                 </nmwg:eventType>
> >                 <cron:parameters id="param1">
> >                         <!-- if entryId is missing, considered new entry -->
> > 			<nmwg:parameter name="entryId">1</nmwg:parameter>   
> > 			<nmwg:parameter name="minutes">20-30</nmwg:parameter>
> >                         <nmwg:parameter name="hours">*</nmwg:parameter>
> >                         <nmwg:parameter name="dom">*</nmwg:parameter>
> >                         <nmwg:parameter name="months">*</nmwg:parameter>
> >                         <nmwg:parameter name="dow">*</nmwg:parameter>
> >                 </cron:parameters>
> >         </nmwg:metadata>
> >
> >         <nmwg:data id="data" metadataIdRef="cron" />
> >
> > </nmwg:message>
> > ------------------------------------------------------------------------
> >
> > <nmwg:message type="MeasurementRequest" id="msg1"
> >         xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
> >         xmlns:cron="http://ggf.org/ns/nmwg/tools/cron/list/2.0/";>
> >
> >         <nmwg:metadata id="meta1">
> >                 <schedule:subject id="sub1"></schedule:subject>
> >                 
> > <nmwg:eventType>http://ggf.org/ns/nmwg/tools/cron/list/2.0</nmwg:eventType>
> >                 <cron:parameters id="param1">
> >                         <nmwg:parameter name="entries">all</nmwg:parameter>
> >                 </cron:parameters>
> >         </nmwg:metadata>
> >
> >         <nmwg:data id="1" metadataIdRef="meta1" />
> >
> > </nmwg:message>
> > ------------------------------------------------------------------------
> >
> > <nmwg:message type="MeasurementRequest" id="msg1"
> >         xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
> >         xmlns:cron="http://ggf.org/ns/nmwg/tools/cron/remove/2.0/";>
> >
> >         <nmwg:metadata id="meta1">
> >                 <nmwg:eventType>
> >                         http://ggf.org/ns/nmwg/tools/cron/remove/2.0
> >                 </nmwg:eventType>
> >                 <cron:parameters id="param1">
> >                         <nmwg:parameter name="entryID">1</nmwg:parameter>
> >                 </cron:parameters>
> >         </nmwg:metadata>
> >
> >         <nmwg:data id="1" metadataIdRef="meta1" />
> >
> > </nmwg:message>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.