EMI SA2 Weekly Meeting

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

Wednesday 13 Oct 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 - Preparing the presentation for CHEP on the SA2 activities. Is 15 minutes only, so I think I have enough material. - Who is going to CHEP? - Book flights for AHM meeting, information on the location will be distributed by NA1. Link to the agenda (empty for now) http://indico.cern.ch/conferenceDisplay.py?confId=108375 - GGUS for Testbeds and tools - "EMI Testbeds" and "EMI QA Tools". SUs will appear as "Testbeds" and "QA Tools" under the label of EMI. Release date 27 October. - 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. - Use the EMI templates for presentation of work done in EMI or by people paid by EMI - Asked for review of Testbeds deliverable and of Quarterly Report - Review started 22/9. Balasz input only. Sent also milestones. - Asked to review: DJRA1.1.1 Compute Area Work Plan and Status Report DJRA1.2.1 Data Area Work Plan and Status Report DJRA1.3.1 Security Area Work Plan and Status Report Reviewers: Maria, Jozef, Alberto DNA1.2.1 - Service Level Agreement Template Reviewers: Alberto - SA2 Deliverables and Milestones DONE MSA2.2 - Continuous integration and certification testbeds in place TODO DSA2.2 - QA Tools Documentation LATER MSA2.3 - Large-scale acceptance certification testbeds are in place
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Received comments from Giuseppe and Morris for DSA2.3.1 (Periodic QA reports) and created new versions of the deliverable after their comments. Everything available in: https://twiki.cern.ch/twiki/bin/view/EMI/DSA231ReviewSA1 - A list of missing deliverables relevant to the SQAP is now presented every week (this was suggested in DSA2.3.1). - Read TOC sent by Giuseppe for the first QC report. - Reviewed the following deliverables: - Compute Area Plan - Security Area Plan - Data Area Plan (about to finish it!) - Working on a new version of SQAP containing the guidelines among other things. + Issues to Discuss The following deliverables are part of the SQAP and haven't been finished yet. Any news? DSA1.2 - Software Release Plan (No new version since 2nd August). It should contain the initial Software Release Schedule. The following deliverable is now ready for review (since 6th October): DSA1.1 Software Maintenance and Support Plan + Steps Next Week - New version of SQAP (but I hope to finish on Friday). - I expect more comments on DSA2.3.1 that I would finish as soon as I get them. - I would like to start reviewing the minimum required documentation for SW components since this is an exercise we have to do for gLite when moving to the new web page anyway.
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - Updated: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2MetricsGuidelines - Added subversion link with sample XML and schema's for bug-mapping and glite bug listing example. - sample mysqlToXML python routines included. - 3rd level user incident detection must be included in metrics as specified by DSA 1.1. - Key performance indicators in metrics must match exactly the DoW description KSA 1.1-1.5. + Issues to Discuss + Steps Next Week - make gLite bug listing conform to schema. Mapping isn't applied yet, so xmllint validation will fail. - circulate full examples (partial examples already circulated last Thursday). - help other middleware partners to generate their XML files and valid against SQAPDefinitions.xsd. - help SA2.4 to produce bug related metric generation examples. - we need as many metrics for end of October as are humanly possible to collect.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Discussions with SA1 and PTs about the EMI project in ETICS - Configuration cloning script - ETICS 3.1 release - Several bugfixes released - RPMLint and JDepend plugins released - ETICS Infrastructure optimization - ETICS documentation re-organization + Issues to Discuss - NONE + Steps Next Week
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress SA2.5 task meeting internal review of DJRA1.1.1_v06 SA2.6 a part of testbed is working, however still we do not reach final solution. + Issues to Discuss Determine internal deadlines for reviews planned in 2.5 + Steps Next Week finish 2 internal reviews (Friday) -finish Test Plan for ARC PTS -confirm XML schemas
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress JUELICH: 16 virtual nodes on it. Today, I put a distributed UNICORE production version installation on four of the nodes as also described in the Testbed table. Testbed monitoring changed, because the testbed hardware had to be moved to a different DMZ. CERN: - testbed site architecture discussion - some services upgraded (replacing glite 3.1 with 3.2) - many tests with egee-nagios - new BDII setup - already working but might need reconfiguration and more tests (discussion about sites...) CNAF: still working on deliverable worked on table matching EMI technical plan component list to testbed deployment status: need some feedback from ARC and Unicore testbed site architecture discussion population of GGUS SU mailing list + Issues to Discuss - JUELICH: The UNICORE components need certificates, where can I get them? Have we taken a final decision about which CA to use? + Steps Next Week JUELICH: * Equip the UNICORE services with proper certificates. * Open ports to gateway and monitoring system. ARC + UNICORE: feedbacks on table of service deployment
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB