1. Introduction

The goal is to “realign” all Virgo packages with a special emphasis on data analysis software installation at CCIN2P3 and CNAF. Recent changes have been introduced in the Virgo software management (virgoStaging / virgoDev suppression, PackageBuild to install external packages, Pm to install software in /virgoStaging…). Migration to SL6 has also already started for a number of packages.

2. Sites & platforms:

Sites: Cascina, CCIN2P3 and CNAF

Linux:

RealTime:

Linux-i686-SL4-2.6.32.11-x86-hal-2.6.03-rtai-3.8.1: Real Time Linux running on the RTPC machines, need strongly to be supported

RIO806X: obsolescent, should disappear soon. Existing applications which need to still run there could remain at frozen version level. There should be no need to be part of the realignment process. To Be Confirmed

VMTR2X: CETIA of Environment Monitoring, frozen for long time, being substituted, no need to be part of the realignment process

OS9: The Vacuum subsystem has been already out of the realignment effort for some time. No need to realign for OS9 now that is getting substituted

Testing hosts:

At CNAF and CCIN2P3, SL6 migration is possible. At CCIN2P3, there is not yet any precise schedule nor any queue available for SL6 but a test machine for software compilation is available. At CNAF, a dedicated queue is available for SL6 jobs.

3. Package alignment program

Step 0: CMT package version: v1r24

Step 1: "basic" packages preparation.

Here is the order of preparation:

1. VirgoPolicy

2. Cset/TCm/Cm/El/Su/Db

3. Cbf/Cfg

4. PackageBuild

5. root/FFTW

6. Fr/Frv

7. Fd

Remarks:

1/ A new version of VirgoPolicy (v2r6) will be prepared first. Obsolete tags removal and compilation flags check up are the major goals of this new version of VirgoPolicy. Any requests are welcome. Note that VirgoPolicy/v2r6 will also provide the CMT pdflatex fragments. If other fragments are available for general use, they could be integrate in VirgoPolicy v2r6

2/ We need to agree on an upgraded version of root that satisfies all root clients (bug free and compliant with Virgo software). Version 5.34.05 has been proposed. This choice must still be validated for SL4 (see Franco's SL4 problems with v5r34p4) and by Dy on all platforms. That means that root and thus PackageBuild should be available asap.

3/ There exists a FFTW 3.3.3 release. We are using 3.3.2. It does not seem that FFTW 3.3.3 fixings are fundamental for our use (http://www.fftw.org/release-notes.html), but we would like to hear from users. Any opinion against fftw 3.3.3 ?

4/ Are all basic packages ready for realignement?

5/ A new package Pm dedicated to the software installation @ Cascina is still under development/tests. It has been proposed to extend its application to any remote site (Tiers 1/2 and personal laptops).

Step 2: All other external packages (installed from sources)

• lalsuite

• omega

• gsl

• mysql

• ...

The list needs to be completed. What are the requested packages, and versions? This is the right moment to collect demands of new packages/versions

Step 3: All other packages

4. Schedule/manpower:

Goal : VCS-9.0 ready for ER4.

Step 1 milestone: April 15th

Manpower:

• Franco + all package managers for Cascina alignment.

• Alberto to check installation @ CNAF.

• MAB for CCIN2P3

Step 1 must be validated at Tiers 1 before April 15th.

VirgoPolicy ready March1 15th.

5. Packages' versions

5.1 Basic packages

5.2 Other packages