==================================================
Yves Perrin
+ Actions done and progress
- Savannah
. rescued 424 bugs for which the category was deleted by accident
. restored squads deleted by accident
. approved new projects, help users with login pbs, etc
. improved the project statistics report (on Rene's request)
by providing links to lists of items having a field set to
a given value.
- Drupal
. created a Drupal database and user on the SPI db server
so that it could be used by the new SLC5 Cervm drupal
host implemented by Carlos
- Other
. helped Geant4 to move their database to the SFT db server
+ Next actions
. install the required modules on the new SLC5/SFT db Drupal
host
. improve Savannah documentation and write a set of how-to's
==================================================
Ana Gaspar
+ Actions done
- Installed Gcc 4.4.2 on slc5 machines
- Worked on the new scripts
-Added new ignore warnings and ignore errors to configuration.xml
-Changes made in the server to avoid problems while dispatching tasks
-Still working on the checkout problem
-Installed cx_oracle 5.0.1 and 4.3.1 for oracle 11.2.0
+ Next actions
- Check if the current version is stable enough to put in production
==================================================
Jakob Blomer
+ Actions done
by having CernVM as platform of LCG nightly builds we aim
- to test, if SLC4 binaries cleanly run the test suite on the CernVM
platform
- to stress the (S)CVMFS file systems, i.e. the software is installed
similar to the CernVM production environment.
Currently, CernVM is a pure testing platforms, no builds are made.
The procedure is as follows:
1) Once nightly are finished, for all projects slc4-gcc34-dbg 32bit and
64bit platforms are copied into a temporary directory. This is done on
lxbuild113 and lxbuild115 resp.
2) Inside this mirror directory, we create a CVMFS repository (i.e. a
particluar format of the directory ready to be served by a web server
for CernVM clients). We do this on the build servers for performance
reasons. This does not include the externals (see step 4).
3) The repository is transferred via tar-pipe to our web server
(cernvm-devwebfs.cern.ch).
4) Once the files are transferred, the tests run on two CernVM Xen
virtual machines, lxbuild116-vm5 and lxbuild116-vm6, for 32bit and 64bit
resp.
Some of the test suites require write access. Therefore, we run
LCGCMT, RELAX, COOL on CVMFS, and
POOL, CORAL, ROOT on SCVMFS.
All the externals will be accessed from AFS.
5) The test logfiles are slightly adjusted to reflect CernVM as
operating system instead of SLC4
6) The test results are sent back to
http://lcgapp.cern.ch/spi/cgi-bin/nightlies.py.
Steps 1)-3) are scripted and already run during nightly builds for
32bit. I have scriptlets for steps 4) to 6). They still have to be
assembled to a chain. Once this works, I will check them in into CVS.
==================================================
Stefan Roiser
+ Actions done
- Preparation and release of LCG 57. The release was done on Oct. 19th. It is the first release of LCG based on ROOT 5.24 (5.24.00b) and includes new versions for all projects, and upgrades of several external packages. Most notably Python 2.5.4p2, oracle 11.2 and several grid middleware packages. More info is available at http://lcgsoft.cern.ch soon.
- Upgraded macphsft02 to Mac OSX 10.6 - the machine is ready. We need to fix one more problem with home directory allocation before giving access to users.
+ Next actions
- Preparation of LCG 57a. This is an urgent bug fix release for LHCb including a patch in CORAL and a fix for cx_Oracle compiling against a new version of the oracle client libs.
There are minutes attached to this event.
Show them.