perfsonar development work

[maxim <>]

Hi Matthias,
Comments are inline. 

-------------------
> Hi Maxim,
> 
> thanks again for your valueable contribution !
> 
> I attached your tarball to the perfSONAR E2Emon Page 
> (unrestricted access !), see 
> http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR_suppor
> t_for_E2E_Link_Monitoring
> 
> I have just a few comments to your software:
> 
> (*) what are the prerequisites besides of PERL (Apache, CGI ...?)
> 
  I've tried to express it in the readme file and install file. Also,
every config file is documented. Except for perl ( with several modules)
 and webserver there is no other prerequisites ( only optional one for the
Google maps API key
if someone wants to see position of the topology point on the map).
Of courese if perl module requires some C library then it should installed (
like gd graphical library for
GraphViz or net-snmp library  for the Net::SNMP package).

> (*) it would be good to have some kind of doc about how your 
> module fits in the E2Emon deployment (how the domains can use 
> that tools in their
> tasks) and how it relates to other pieces of software. To get 
> an idea, you can have a look at the deployment guide 
> (http://wiki.perfsonar.net/jra1-wiki/images/3/3b/E2EMonitoring
> _DeploymentGuide_v07.doc). 
  
  Some of that could be found  in the readme/install files but I can write
something like that, just give
me some time.

> We can integrate your contribution here (the doc needs an 
> update anyway
> ;-) ).
> 
> (*) to help people not to get confused, it would be good to 
> use a unambigious naming schema. As E2Emon is the common 
> prefix, E2Emon MP is our Measurement Point - so what about 
> E2Emon MP_config for you contrib? 
 
  yes, that will work. Altough I am aiming for the MA as well.
So, its more like E2Emon config, because thats what its trying to be - a
configuration manager for the E2E monitoring MP and MA.


> To prevent release clashes (we plan significant changes to 
> the MP), please also exclude all "foreign" code from your tarball.
> 
    I;ve added it only as reference to give people a picture how it could be
deployed and used
together( its not relying on  G2_E2E_MP code  and all "foreign" code can
removed from the tarball)

> We could also have a VC/TC to discuss about that points.

sure, let me know if you have a time  and date in mind.
   Thanks for your review,
                                Maxim.