perfsonar development work

[Loukik Kudarimoti <>]

Aaron,

I like your suggestion as well. Our current requirement, as Roman 
mentioned, is to be able to replace the complete metadata content known 
to the sql ma. It would be really good if you can extend your suggestion 
to also cover the complete replacement of metadata use case (I see data 
inside data as a challenging point to resolve).

We are unfortunately running short of time for implementation and 
release. I would like to move on with the change spec and merge the two 
messages at a later point in time.

Loukik.




Roman Lapacz wrote:
> 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.


--

---------------------------------------------------------------
L o u k i k   K u d a r i m o t i

     * *              Network Engineer
   *     *            City House, 126 - 130, Hills Road
  *                   Cambridge CB2 1PQ, United Kingdom
  *                   WWW: http://www.dante.net
D  A  N  T  E          Tel:+44 1223 371300 Fax:+44 1223 371371