EMI SA2 Weekly Meeting

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

Wednesday 9 Mar 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: - PEB approved certification and testing guidelines. See bit.ly/emisa2 for the status of the others. - Question: Can the testbed be used at the EGI TF for training purposes? - PEB wants to have a team to quickly read the material produced and provide feedback. I will be in the team for SA2 if someone else wants to participate he/she is welcome. - The links to the videos of the SA2 training are on the EMI SA2 page http://bit.ly/emisa2 EGI: - Meeting with the Quality Control and received their guidelines https://documents.egi.eu/public/ShowDocument?docid=240 - Reviewed thr EGI guidelines and sent feedback to Balazs. Conferences - EGI UF and EMI TF joint conference. https://www.egi.eu/indico/sessionDisplay.py?sessionId=13&confId=207#20110412 - Participation from the task leaders - EMI All Hands Meeting. Lund University from 30 May-1 June 2011. http://indico.cern.ch/conferenceDisplay.py?confId=124206 + Next Step - Check the reports from the product teams
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Training on Release, Change, Testing, Certification and Documentation policies last week. - Training recorded in: http://connect.ct.infn.it/p65002758/ - More than 20 people connected. - Some questions and clarifications. - Only two people have given feedback so far :-) - Good experience and the possibility to follow the training off line is a very good idea. - Applied changes to Policies after the feedback gathered in the training last week. - Some Policies are still pending PEB approval. Reminder sent on Monday. - Finished the Acceptance Criteria twiki and discussing it with SA1 QC before sending it to PEB: https://twiki.cern.ch/twiki/bin/view/EMI/ProductionReleaseCriteria + Issues to Discuss - Open issues: Inter-component testing. - Who is going to populate the EMI production repository? Who is going to create the web pages for a release? Is this all done by SA1? + Steps Next Week - Work on the SQAP to update it with all the latest changes.
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - described back log management & provided plotting example for SA2.4 - very little else, had large scale operational problems at our site that I've had to troubleshoot. + Issues to Discuss - when to run --autoprofile, given Francesco's comments on EMT list? + Steps Next Week - access next highest priority metrics to obtain, providing examples & description to Lars.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress Incidents: - Problems with CVI web-service on Sunday and Monday investigated and solved - Disk problem solved in the etics-repository server Infrastructure: - Script revertToSnapshot.py script updated according to CVI feedback - Monitoring scripts for ETICS: (two scripts almost ready) - disk space script - process(time spent) script - Swap file Minimal Image SL5 64bits: - Now we have a swap file in the EPEL 64bits minimal image. - 32bits Minimal Image (Started): - On-going (missing condor configuration and setup for runAsRoot) ETICS: - RC1 preparation and nightly builds moved - Client rollback from 1.5.2 to 1.5.1 after potential gLite issues identification - Change in the client to avoid an error creating empty RPMs - Support: - ETICS problems during Saturday - 12 new empty components for EMI - 2 modifications of external components - 7 GGUS tickets closed - 5 components and their configurations cloned (requested by Cristina) - Fabrizio Furano problem with apr, apr-devel and actiemq - Jean Philippe, Pedro and Alejandro problem with oracle-instantclient and AFS - Michael problem in building FTS in VNODE - John White: initial investigation on YUM repos and i386 packages - Christian Bernardt: Dedicated build nodes assigned to dcache for investigation QA: - PyLint plugin: - No much progress. - Findbugs plugin: - FindBugs includes externals when they are added in the jar file. Looking for solution. - Report generator: - Possibility to choose which ETICS config to create report for. - EU-report: - Added Successful Builds chart from the detailed report. - Detailed/Nightly report: - Added a graph showing the distribution between products for each product team. - Added PriorityBug metric charts with a 30 day timeframe. - Added heading showing build config, description and status. - Changed page ordering so PDF page selection match up with the page numbers in the report, added roman numerals to table of contents. - Added Project Overview to table of contents. - Fixed error in chart zooming algorithm. - Fixed error in component duplication alogrithm. - EMT report: - Added Successful Builds chart from the detailed report. - Added heading showing build config, description and status. + Steps Next Week ======================================================= - Client 1.5.3-1 release - sl5_ia32_gcc412EPEL under preparation - sl5_x86_64_gcc412EPEL minimal with run as root under preparation - DSA2.2.2
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress SA2.5 I finished SECOND REVIEW EMI-1 DEVELOPMENT AND TEST PLANS -support of ARC PTs how to implement certification verification and validation procedures. implementation is understood as iterative process. reduction of EMI components is considered for useful step SA2.6 attempt to deploy EMI binaries
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    > + Status and Progress > CERN - GGUS tickets - a lot of security updates on the testbed machines (kernels...) - virtualization infrastructure (updated images on VNODE, library server for CVI) CESNET CNAF: Meetings: EMT, attending guidelines training Working on Large Scale testbed. Twiki integration with pre-deployment activity by Florida. Mail to PTs requesting for thei scalability plans. EMI1-RC1 Deployment Plan HW administration GGUS tkting DESY JUELICH > + Issues to Discuss > WN package: using gLite? vnode support through ggus emitestbed SU? > + Steps Next Week > CERN CESNET CNAF: start actual EMI1 deployment large scale testbed DESY JUELICH
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB