Cream (Cluster of Competence): Massimo Sgaravatto, Sara Bertocco, Alessio Gianelle
SA3: Juha Herrala, Sara Bertocco (Padova),
SAM: John Shade, Konstantin Skaburskas
The meeting started 10 minutes later due to a typo in the agenda (wrong conference ID)
Service Introduction (by PPS)
Antonio resumed the phases of the pilot.
He proposes to use the page PpsPilotCream as temporary reference (repositories) and to describe the service layout there
The aim of this first phase is to get to a stable version of the installation instruction and to start getting the monitoring tools ready for the new service
The service will be published in the PPS BDII
The involvement of FZK and CNAF in the first phase is confirmed. SCAI_PPS was requested to run the WMS. Their involvement is not confirmed but they cannot however start the installation before next week.
Massimo confirms that the "official" WMS+ICE patch is not built yet (problems with ETICS). They are working to it. This WMS patch will be installed by SCAI (or by FZK as backup) when ready.
Angela pointed out that in the meantime an ICE enabled WMS was already installed at FZK using the instructions given by Alessio and circulated with the agenda.
Massimo: there are some changes in the rpm versions to be used with respect to the original recipe.
Antonio: please use the reference page PpsPilotCream to describe the correct procedure
Update 11-Jun: the WMS used is pps-rb-fzk.gridka.de . A job has already been successfully submitted through it and executed on cream-04.pd.infn.it:8443/cream-lsf-creamcert1 by Massimo
During phase one the pre-certification repository (the one pointed out in Alessio's instruction) will be used for the installation. The content of this repository is likely to be changed often in the future. Therefore, for phase two, a mirror of the repository will be set-up at CNAF in order to decouple the production sites participating to the pilot
PIC will be asked to participate in the second phase
Antonio asks around whether someone wants to coordinate the pilot. Nobody volunteers. Antonio will cover the coordination tasks.
Under proposal from Massimo, the e-mail list egg-pps-pilot-cream is created at cern to host communication related to the pilot.
Use cases (by Users)
The relevant use case in this phase comes from the monitoring tools, notably SAM. From several partd the opportunity arised ot create anew node type in the GOCDB for Cream. John, who is already involved in the clean-up of the existing node types, will find with Gilles (GOCDB) a a name for the new node type.
Update 11-Jun: SAM is an important use case but also gstat and nagios have to work with the new service.
Gstat is connected to the PPS BDII but it is not clear how it will represent the new service type. As soon as th new type os defined, Min will be called in the loop.
Nagios developers want to see the new CE in action too.
As far as SAM is concerned, the goal of the pilot is to identify a suitable set of tests to be run in production. This test should include by default the set currently used to test the lcg-CE
Angela proposes to eliminate the RM tests from the list of tests. To be evaluated
Antonio: One thing that could simply be done is to clone the lcg-CE sensor and to create a cream sensor out of it. This is a configuration to be done both client side and at the level of the display. It can be started as soon as the replication of the SAm server for pre-production, currently in progress, is finished (about one week from now)
John points out the a contribution from the developers would be needed to identify specific features of the cream CE to be tested
update 11-Jun: SAM tests can be produced in theory by everybody. Normally the SAM team at CERN takes care of the integration of tests of general interest in the official production instance of the monitor. Sometimes they develop tests but more and more often they evaluate and integrate tests produced by third parties (experiments, certification etc.). SA3 is an active producer of tests, used within middleware certification. This activity will be presumably be extended to JRA1 within the cluster of competence
The idea for a pre-production use case is to put in touch the SAM coordinator(John) and the SA3 SAM manager (Andreas) to migrate earlier in PPS those tests that are likely to be integrated in the production instance of SAM in the future
Metrics
The success of the phase one, and the consequent transition to phase two will be determined by the successful installation of a working WMS based on Cream CE.
No major incompatibility with the existing monitoring framework are expected. Should they be discovered, this could bring to stretch the foreseen timelines
General Agreement on Service Level and Conditions
no VO users are involved in this phase.
Hardware requirements: The general requirement are the same as for the existing WMS and CEs
WMS: 4GB RAM and disk space depending on sandboxes (80 Gb acceptable for PPS)
Cream CE: 2GB RAM
Antonio points out that, although the requirement could be relaxed for phase one, it is foreseeable that the services set-up will be re-used in phase two as well. Therefore it makes sense to allocate from the beginning a machine powerful enough.
Timeline
The attendees to this meting will meet again the 1st of July at 15.30 as a check point for the evaluation of phase one
Verify behaviour of gstat with Min (as soon as the new service is published)(TASK:7159) UPDATE 3-Sep-2008: TASK closed: Gstat fixed. Now it can see Cream CE. Antonio