EMI SA2 Weekly Meeting

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

Wednesday 3 Nov 2010, 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
    
    + Status and Progress - PEB is taking place now. I have asked for SA2 presentation needed? - Book flights for AHM meeting, information on the location has been distributed by NA1 REGISTER HERE http://indico.cern.ch/conferenceDisplay.py?confId=108375 - Side meetings needed? - GGUS for Testbeds and tools: "EMI Testbeds" and "EMI QA Tools". Available and is it working? - PEB asked for when on the Testbeds there will be installed the Production and RCs version of all products. For general usage by the PTs. - Asked for review of Testbeds deliverable and of Quarterly Report - Discussed deliverables with the work plans authors.
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Discussions with Alberto di Meglio and Francesco to understand who is responsible for the information providers existing in gLite. - Reviewed the JRA1 QC report. - Discussions with Giuseppe on how to improve checklists for reviews. - EMI 0 should be ready by now according to https://twiki.cern.ch/twiki/bin/view/EMI/TSA13#EMI_0 but deadlines haven't been met. Contacted Cristina to check what the status is and see how we can improve the current process. + Issues to Discuss - The following documents are part of the SQAP and haven't been finished yet: - DSA1.1 Software Maintenance and Support Plan -> Ready for review. Deadline is 18/10. Missing review from SA2. - DSA1.2 - Software Release Plan -> New version on 25.10. - DSA2.4 Continuous Integration and Certification Testbeds -> Under review. Deadline is 29/09 - DJRA1.1.1 – Compute Area Work Plan and Status Report -> Under Review (SA2 done by Maria and Jozef). - DJRA1.2.1 – Data Area Work Plan and Status Report -> Under Review (SA2 done by Maria and Jozef). - DJRA1.3.1 – Security Area Work Plan and Status Report -> Under Review (SA2 done by Maria and Jozef) - DJRA1.4.1 - Infrastructure Area Work Plan and Status Report -> Seems to rejected by JRA1?> Seems to rejected by JRA1? + Steps Next Week Still finish the new version of the SQAP!
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - ARC XML bug-tracking listing issues resolved and under development. - UNICORE bug-tracking listing modified slightly due to problems in XML. - dCache XML bug-tracking listing started. - Documented a description of XML schema in Internal metrics document v0.29. - GGUS meeting postponed due to Torsten Antoni's absense. + Issues to Discuss - None + Steps Next Week - SA2.3 will look at BackLog metric in parallel to PriorityBug SA2.4 development. - SA2.3 will look at checkstyle/PMD in parallel to FindBugs SA2.4 visualisation.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Bug fixing and testing for ETICS 3.2 - Deliverable preparation - Externals preparation - Bugfix for ETICS client to solve EL5-SL5 mismatch - GIT registration for DM - D4Science MoU modifications - sl5 to EPEL platform migration, DB cleaning - JDepend fixes to solve ARC problem - ETICS Documentation improvements in WIKI + Issues to Discuss + Steps Next Week - ETICS 3.2 release - Deliverable
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress 2.2 I finished review DJRA1.7.1 Software Development Quality Control Report - deadline 27/10 2.5 I check status of https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA131 My initial impression is that delay of this document could affect quality of associated documents. 2.6 recovery of ARC testbed slow progess + Issues to Discuss During testing activities in EMI we developed revision testing suite: http://arc-emi.grid.upjs.sk/revisionTests.php It prevents to spread code errors in very early stage of development. We tested ARGUS, etc We started development of test suite for automatic functional tests for night builds. etc However it is hard to report about these activities in SA1 or SA2, after reading DoW and last deliverables I understood that these activities belong in JRA1, however we are not officially listed in this package. My question is how to solve this situation by correct way.
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress * CNAF: o Testing ggus tkt: mails are sent in digest form, even though it is configured otherwise. Anders is looking on it. o Sent review comments on deliverable DJRA1.6 o new version of DSA2.4 including review comments by Morris. o new version of Milestone MS23 with document restructuring according to Florida suggestion o Added in the testbed twiki info on VO testers configuration * CERN: testers.eu-emi.eu VO deployment / testing * JUELICH: firewall issues such that the Nagios monitoring and UNICORE are now available from everywhere. + Issues to Discuss - PEB comments on large scale testbed milestone proposed approach + Steps Next Week * add bdii configuration info in the twiki * add use cases description in the twiki
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB