perfsonar development work

[Roman Lapacz <>]

Hi Aron,

I like the approach you suggested but I understand that Loukik's 
document derives from E2EMon MP and JRA4 requirements (Loukik could say 
more).

Roman


Aaron Brown wrote:
> Looking at the CompleteMetadataStoreRequest message, I think we need 
> to define some messages for directly modifying the store file, instead 
> fully replacing it or implicitly modifying it with other messages.
>
> My idea was something along the lines of a MetadataUpdateRequest which 
> could be used to add new metadata to the metadata store, update the 
> data in the store, and, if needed,  remove metadata from the store.
>
> It'd look similar this:
>
> Adding metadata:
>
> <message type="MetadataUpdateRequest">
>   <metadata>
>      <eventType>metadata</eventType>
>   </metadata>
>
>   <data>
>      <metadata>
>          ...
>      </metadata>
>   </data>
> </message>
>
> which would respond with:
>
> <message type="MetadataUpdateResponse">
>  <metadata>
>    ...
>  </metadata>
>  <data>
>     <key> a key for the metadata just added. This key can be used to 
> update/delete the metadata </key>
>  </data>
> </message>
>
> You could replace metadata:
>
> <message type="MetadataUpdateRequest">
>   <metadata>
>      <key> ... </key>
>      <eventType>metadata</eventType>
>   </metadata>
>
>   <data>
>      <metadata>
>          ...
>      </metadata>
>   </data>
> </message>
>
> Or you could delete it:
>
> <message type="MetadataUpdateRequest">
>   <metadata>
>      <key> ... </key>
>      <eventType>metadata</eventType>
>   </metadata>
>
>   <data>
>      ...
>   </data>
> </message>
>
> I'm definitely not married to the specific implementation modes above, 
> but what does everyone think of the concept?
>
> Cheers,
> Aaron
>
> Loukik Kudarimoti wrote:
> > Hi all,
> >
> > In attachments you can find word documents that detail all the 
> > changes expected from RRD MA and SQL MA for release 3.1. Please note 
> > that there is a section on syslog that is not complete and should be 
> > filled with a reference to another document at some point in time in 
> > the future.
> >
> > The focus is on the introduction of the new fields (keyword 
> > parameters) as well as e2emon sync support from SQL MA.
> >
> > The document is of interest to the following
> >
> > Roman, Szymon - implementation
> > Nina et. al, David et. al, - visualisation tool implementation
> > Michalis et. al. - Web admin changes and Test scripts update
> > Matthias and Mark - e2emon sync spec
> >
> > The next step is for the document to be reviewed and if there aren't 
> > any comments, necessary changes to be undertaken including upgrade of 
> > documentation (interface spec). Comments are welcome on these 
> > documents until 10th of June 2008 after which changes will have to be 
> > moderated.
> >
> > If you have any questions, let me know.