EMI SA2 Weekly Meeting

Name: EMI SA2 Weekly Meeting
Start: 2011-02-02T10:30:00+01:00
End: 2011-02-02T12:00:00+01:00
Location: CERN

Wednesday 2 Feb 2011, 10:30 → 12:00 Europe/Zurich

CERN

Description

Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoGate/koala.jnlp?meeting=e8eteDvBvDataDa9I8
- Phone Bridge
ID: 62440
- Phone Bridges Numbers
http://evo.caltech.edu/evoGate/telephone.jsp

NOTE: THE MEETING IS RECORDED (for minutes-taking only purposes, then the files are deleted)

- 10:30 → 10:40
  
  Action List Review 10m
  
  Emi Sa2 Action List
- 10:40 → 11:10
  Task Reports and Progress 30m
  
  In this first meeting we will discuss on who is working on which task(s).
  - TSA2.1 – Work Package coordination 5m
    
    PEB: - Platforms will be officially announced but will be. SL5/64 for EMI-1 and also SL6/64 for EMI-2. Possible debian 6 but we should not invest too much for now (first focus only on EMI-1 release). - Distributed the Documentation Guidelines to PEB (thanks Gianni) for comments. We send them to SA1 QC for comments? - SA2 Training. Poll or not poll maybe we will be asked to give the training. I let NA2 to organize it. ADM thinks is very important as users claim they do not know the guidelines. We can do one hour training for each guideline. Poll still open. In-reach training topics survey at http://www.surveymonkey.com/s/FHHZLL8 and also to fill in the doodle poll for the dates http://www.doodle.com/e6ke35358khw5nmb - EGI UF and EMI TF joint conference. I have asked/obtaind to have all talk in a good sequence and together. Wedn afternoon. https://www.egi.eu/indico/conferenceTimeTable.py?confId=207#all - EMI All Hands Meeting. Lund University from 30 May-1 June 2011. Please reserve already these dates in your calendar. The very preliminary event page (just a placeholder for now) is at: http://indico.cern.ch/conferenceDisplay.py?confId=124206 + Next Step - Any issue for PEB? - Send QA report to the PEB - Need some input for the QR report but I will send you the previous QR report as starting point. Dead line next week.
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Nothing to report. No progress done this week either due to tasks for gLite. + Issues to Discuss - None + Steps Next Week - Production Release Criteria: https://twiki.cern.ch/twiki/bin/view/EMI/ProductionReleaseCriteria - EMI release check list: https://twiki.cern.ch/twiki/bin/view/EMI/EMIReleaseChecklist - Prepare an example of the component versioning schema we would like to propose for PTs. - Work on the next version of SQAP. - Testing and Certification guidelines improvements suggested by Giuseppe.
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - Improvements to Metrics reporting documentation template. - Animated slides for SA2.4 tools presentation on metrics - Overview description of process metrics added to the Internal Metrics document for Andres and in preparation for UF2011 - FindBugs guidelines fully documented. + Issues to Discuss - None + Steps Next Week - Still awaiting ARC/dCache bug-tracker listings. -oversight on PyLint, cppcheck and cyclomatic complexity
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Client 1.5.0 testing: - Client regression testing: new version fix a lot of problems. Two problems remaining to consider the tests as Passed. - Multinode testing: A few problems found. Already fixed & committed one of then. - Memory leaks investigation. Due to a memory allocation problem in the ETICS production server, I left running a monitor, some scripts doing some calls and refreshing the web page during 24 hours; but nothing relevant found. A deeper analysis is needed. (Collected charts and data available if someone what to see then) - Support: - Several issues by Maria (builds, C-ARES, configuration versioning, etc.) - Debugging GCC issue by Pedro (still in progress) - EMI support to Cristina - 4 new configurations for Cristina - 5 externals registered - Many GGUS tickets by Pablo, Laurence, Valery, Dennis van Dok, etc. - Working on SA2.2.2 deliverable - Missing Report from Alberto Resco on the infrastructure - 100% of the ETICS pool is now on CVI - Debian was restarted but it keep failing due to disk size problem - PyLint plugin implementation completed. Now testing - QA Report generator work in progress. Some charts have already been circulating via EMT. - New member of SA2.4: Vitor Emanuel Gomes Gouveia + Issues to Discuss - EMAIL BY EGI: Process automation, repositories and release metadata + Steps Next Week - Client 1.5.0 testing - Working on SA2.2.2 deliverable - Monitoring scripts
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress Task: 2.4 reading documentation and analyzing XML schema provided by other partners (EVA) Task: 2.5 (Jozef) -final remarks to Francesco deliverable (phone meeting) -comment to TOC of DSA1.3.2 Software Maintenance Quality Control Report -update twiki task page Task 2.6 Marek will report about progress. + Steps Next Week update twiki 2.5 task table contribution to SA2.4
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress KOSICE: JUELICH: DESY: * fixing the problem restarting (narrowed it down to problems on thehost machine), * stability problem is under control * reading testbed guidelines and making plans to adapt testbed in accordance CNAF: testbed administration. discussion on fake CA, Storm deployment. CERN: * Worked on (support and tkts handling, documentation, HW/SW administration...): - preparation to use new virtualization infrastructure at CERN (where most part of the testbed will be migrated) - changes in security infrastructure (mostly internal, concerning accessing the machines, no changes for Grid services itself) - usual testbed maintenace - mail discussion about fake CA + Issues to Discuss UPDATES on MS24? - Claudio Cacciari gave me a contact person for PRACE. Will contact him after news about the milestone. * Where are the definition what availability and reliability? ... so that I can provide the right monitoring data for the testbed. Is it just the ping that is measured? UPDATE on DESY participation? + Steps Next Week CERN: - continuing preparing and testing new infrastructure DESY: * starting to implement the planned changes to the testbed * working on automated reporting of availability
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB