Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: Functional Testing the E2EMon MP

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: Functional Testing the E2EMon MP


Chronological Thread 
  • From: Verena Venus <>
  • To: Loukik Kudarimoti <>
  • Cc: "Matthias K. Hamm" <>, Michael Michalis <>, Luis Marta <>, "Matthias.Hamm" <>, "Mark.Yampolskiy" <>, "" <>, Nicolas Simar <>, Szymon Trocha <>
  • Subject: Re: [pS-dev] Re: Functional Testing the E2EMon MP
  • Date: Mon, 9 Jul 2007 13:58:25 +0200
  • Organization: DFN

Hi again,

Am Monday 09 July 2007 13:43 schrieb Loukik Kudarimoti:
> Verena Venus wrote:
> > Hi Loukik,
> >
> > Am Monday 09 July 2007 13:16 schrieb Loukik Kudarimoti:
> >
> > [...]
> >
> > > I think its very beneficial to have this functionality and is very easy
> > >
> > > to implement it (It shouldn't take more than a couple of hours). But I
> > >
> > > would say that its up to you guys. All services in perfsonar 2.0
> > > (except
> > >
> > > bwctl mp) support this functionality.
> >
> > In fact we do support this feature in the 0.2.1 release of our service.
>
> Ok, we weren't aware of your new micro-release. Can you drop an email to
> release management whenever you produce a new micro-release?
>

OK, no problem.

> > > As far as a "definition of what is a proper perfSONAR service" is
> > >
> > > concerned, we don't have any such document yet.
> > >
> > > Nicolas, Szymon, any thoughts?
> >
> > I'd like to bring up the idea of a perfSONAR validator (again), which
> > should be easy to accomplish, now that we have the SOAP UI test
> > projects for the services. Just extract what all these test files have
> > in common, and you have testing script for common perfsonar services.
> > This could also be the starting point for defining what a "proper"
> > perfSONAR service is.
> >
> > And obviously, we have a need for such a thing (see Mark and Matthias).
>
> I take your point on the need for such a validtor. However, I think such
> a validator would still need a documented definition of what exactly
> does it need to validate (i.e., what features should it be checking
> for). I think we need an initial list (like echo functionality, ls
> registration, result codes, doc/lit style, logging, wsdl, etc)
>

This already looks like a list :)

Just my two cents:

Maybe you can put it on the wiki, then we have this as a starting point quite
fast. I think, it does not have to be perfect for the beginning, but is has
to be there so that people can have a look at, and easily get an impression
what they have to do to be compliant. This could be completed by a FAQ and
the validation test scripts for SOAP UI (once they are ready).

Kind regards,
Verena

--
Verena Venus - DFN Labor

Regionales Rechenzentrum Universitaet Erlangen-Nuernberg
Martensstrasse 1, D-91058 Erlangen



Archive powered by MHonArc 2.6.16.

Top of Page