EMI SA2 Weekly Meeting

Name: EMI SA2 Weekly Meeting
Start: 2010-09-15T10:30:00+02:00
End: 2010-09-15T12:00:00+02:00
Location: CERN

Wednesday 15 Sept 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
    
    - No special news from PEB. Alberto DM will distribute the offical news. - All Hands meeting: 22-24 November (Prague) - Uploaded the DSA2.4 deliverable (testbeds) , and reviewing it. - Deliverables and Milestones DONE DSA2.1 - Software Quality Assurance Plan TODO DSA2.2 - QA Tools Documentation JOSZEF REVIEW DSA2.3 - Periodic QA Reports REVIEWED INTERNALLY DSA2.4 - Continuous Integration and Certification Testbeds TO REVIEW MSA2.2 - Continuous integration and certification testbeds in place MSA2.3 - Large-scale acceptance certification testbeds are in place
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - Investigating Savannah Statistics as examples of metric collection. - Static code analysers defined in Internal Metrics document v0.20. + Issues to Discuss + Steps Next Week - Meeting at 2:30pm (CEST) to produce XML exchange format for metrics.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress I planed to contribute more to writing testing and certification guidelines. However, I had to solve urgent local issues with Q1 financial issues (this consumes more working time as I assumed). I have observed that usability testing is not mentioned in testing and certification guidelines (Probably activity is doing by other package if I remember correctly information presented on kick-off meeting) -we checked functionality of provided services in testbed SA2.6 (demonstration of ARC client on meeting in Amsterdam) -I informed PTs leaders about need to answer survey about access methods to log files. I do not received consistent answer. I propose the simplest solution for example which covers 70-80 percentages of actual needs. 20-30 per. will be solved adhoc. -I started to read Q1 report produced by Maria (expected final today) + Issues to Discuss I obtained first information about ETICS. ETICS produces a few metrics. What is their relationship to actual metrics? What is future plan? Will be the number of these metric increase? -usability test (status or coordination) + Steps Next Week finish all open issues -testing and certification guidelines -review feedback to Maria Q1 report
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress - logs available to PT users from testbed servers: sent survey with possible solutions, need to understand how frequent is the USE case from Oxana - etics wn installation at cnaf (is this part of sa2 ? ) - EMI test VO name change: now it is testers.eu-emi.eu : if everybody agrees we must start enabling such VO on resources + Issues to Discuss - news from UNICORE testbed? - first requests to EMI testbed: slow responsiveness to emi-sa26 mailing list (basically nobody answer apart from me). Should we use savannah as ticketing system allowing for PT members to directly open tasks on people? + Steps Next Week - deliverable dsa24: integrating Alberto's review - UNICORE testbed resources.
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB