perfsonar development work

[Guilherme Fernandes <>]

Sorry, I should have noted that I manually renamed the rpm file to have 
the RC3 tag, but the actual name of the package is 'perfsonar-clmp' and 
the version is '2.0'.

Besides, the new package_maker script makes the package name lower case 
but maintains the name inside the webapps directory as is. So the new 
package for clmp will be 'perfsonar-clmp' and not 'perfSONAR-CLMP' (but 
for running the script I still give the name perfSONAR-CLMP, which is 
the name of the service inside the webapps directory), which is a 
different package for the rpm system (so upgrade doesn't works).

Also note that packages must have only numbers and dots in their version 
(as given to the package_maker script). So if the developers/testers 
want to make the RC's packages upgradeable they should adopt something 
like  <service version>.<rc_number> (i.e. 2.0.3 for CL-MP 2.0 RC3).

As an example to test the upgrade command of RPM you can use:

http://150.162.248.42:8081/perfsonar-clmp-2.0.3-1.i386.rpm

Between, the new package_maker had a bug in the symbolic link creation 
of the service's webapps directory, so the last rpm for the clmp 
wouldn't work 'out-of-the-box'. Please use this one.

Thanks,

Guilherme

Jochen Reinwand wrote:
> Just a small note. RPM update mechanism is failing:
>
> ]# rpm -Uhv perfsonar-clmp-2.0-RC3-1.i386.rpm
> Preparing...                ########################################### [100%]
>         
> file /home/perfsonar/webapps/perfSONAR-CLMP-2.0/WEB-INF/classes/perfsonar/conf/eventType-map.xml 
> from install of perfsonar-clmp-2.0-1 conflicts with file from package 
> perfSONAR-CLMP-2.0-1
>         
> file /home/perfsonar/webapps/perfSONAR-CLMP-2.0/WEB-INF/classes/perfsonar/conf/log4j.properties 
> from install of perfsonar-clmp-2.0-1 conflicts with file from package 
> perfSONAR-CLMP-2.0-1
>         
> file /home/perfsonar/webapps/perfSONAR-CLMP-2.0/WEB-INF/classes/perfsonar/conf/service.properties 
> from install of perfsonar-clmp-2.0-1 conflicts with file from package 
> perfSONAR-CLMP-2.0-1
>         
> file /home/perfsonar/webapps/perfSONAR-CLMP-2.0/WEB-INF/lib/perfsonar-clmp-2.0.jar 
> from install of perfsonar-clmp-2.0-1 conflicts with file from package 
> perfSONAR-CLMP-2.0-1
>         
> file /home/perfsonar/webapps/perfSONAR-CLMP-2.0/WEB-INF/lib/perfsonar-web-admin-0.5b.jar 
> from install of perfsonar-clmp-2.0-1 conflicts with file from package 
> perfSONAR-CLMP-2.0-1
>
>
> Jochen
>
> On Monday 17 March 2008 22:09, Guilherme Fernandes wrote:
>   
> > Hi all,
> >
> > CL-MP RC3 can be found in deb and rpm format at:
> >
> > http://150.162.248.42:8081/perfsonar-clmp-2.0-RC3-1.deb
> > http://150.162.248.42:8081/perfsonar-clmp-2.0-RC3-1.i386.rpm
> >
> > For the deb version you will also need the perfsonar-tomcat deb package:
> >
> > http://150.162.248.42:8081/perfsonar-tomcat-6.0.16-1.deb
> >
> > Changelog:
> >
> > Added: Autentication functionality based on eventType
> > Updated: Using version 1.0.20080310 of perfsonar-base.
> > Bug Fix: CronComponent had a bug in the new eventType's handling
> > Bug Fix: RNCs fixed with right eventType (bug id 254)
> > Bug Fix: Ping RNC PingParameters definition fixed (id 361)
> > Bug Fix: CL MP not reporting ping measurement with less than 8 bytes (id
> > 365) Bug Fix: packetSize parameter missing in Interface Specification
> > description of Traceroute (id 375) Bug Fix: traceroute bug for RedHat based
> > distributions (id 376)
> >
> >
> > I actually forgot to update the documentation to add the details about
> > the authentication process (and also the changelog for RC3). You can
> > configure which tool needs authentication editing the file
> > webapps/perfSONAR-CLMP/WEB-INF/classes/perfsonar/conf/eventType-map.xml
> > (just change 'no' to 'yes').
> >
> > This has yet to be integrated to the webadmin servlet, I'm waiting for
> > the new version which comes out this week?
> >
> > Best regards,
> >
> > Guilherme
> >     
>
>