EMI SA2 Weekly Meeting

→ Europe/Zurich
CERN

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)
 
Action List
Minutes
    • 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 - Must complete the quarterly report. Thanks for the KPIs. - Prepared the SA2 wiki page http://bit.ly/emisa2 as front window where all we have for others to see and get is presented - PEB: AHM meeting summary sent by A. Di Meglio. - GGUS for Testbeds and tools: "EMI Testbeds" and "EMI QA Tools". Friendly tell that we can only receive via GGUS in order to provide better support and account it. + Next Step - Prepare for initial QA reports and analyse them. - Any issue for PEB?
        SA2 Internal Wiki
        Sa2 Meetings
      • TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
        - Created the RSS feed - Preparing the guidelines for distribution this week. - New versionof the SAQP by Christmas but will announce what we have as asked by the PEB.
      • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
        + Status and Progress - still working on bug state transitions in gLite bug-tracking XML description. - XSD XML schema definitions seem to be defined correctly. - Rewriting/structuring Metric Guidelines to conform to new format. - Planning metric report visualisations/structure for Thursdays SA2.3 phone meeting. - investigating cppcheck definitions and static analysis metrics. + Issues to Discuss - Do we only generate metric graphs to be interpreted by SA1 QC or do we interpret the information ourselves? + Steps Next Week - still need to give feedback to Christian on dCache prototype XML format. - distribute good examples of RfC XML examples to all middlewares and include in metric guidelines. - document ETICS metric plugin requirements for product teams in the metrics guidelines. - watch progression of sample quarterly reports.
      • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
        +++ Items to Discuss and Issues +++ On-going and Coming Tasks - EMT, PT support - Object History - ETICS Locking Modification - PyLintPlugin work in progress - RPMLintPlugin, SLOCCountPlugin improved - ETICS Virtual Infrastructure Migration - Report Generator PDF generation Next Week: - Deliverable
      • TSA2.5 – QA Implementation Review and Support 5m
        2.4 Testing of functional test suite (Marek) development of frontend for functional test suite (Eva) 2.5 review of two documents EMI-DSA1.1 EMI DJRA!1.4.1_v8 support product teams Discussion about testing guidelines and its introduction in a practice 2.6 sending data about availability of resources > + Issues to Discuss Feedback from ARC PTs- all product teams agree that testing and verification activities of PTs will be performed by testers (not the same people as developers), procedures and reports should be simplified (comments on quidelines are collected), > + Steps Next Week 2.6 Update ARC on v0.8.3.1 5.4 record about reviews which were done
      • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
        > + Status and Progress > ALL - sa2.6 KPI for aug-oct period sent. CNAF - Deliverable DS2.4: Morris approved. Now ready for EU. Florida will follow the thing. - Broadcast about testbed sent to EMI all members: no tkt opened, or replies. - LARGE SCALE ACCEPTANCE TESTBED: I had a meeting with Balazs about large scale acceptance test. Agreed on the general model of "on demand" creation proposed, but from his point of view instead of volunteers, he wants some "promises" of availability for 2-3 campaign of testbed setup (HW+ effort, for X days period) from partners participating to the large scale testbed (EMI + NGIs). So that somehow sa2.6 must guarantee resources on PTs request. We agreed on that I start defining the whole model in a twiki, with procedures and so on, start contacting "volunteers", and if nobody ends up being available the issue will be discussed in PEB. CERN - system administration, migrating some testbed services to other machines (some physical machines at CERN will be retired) - some support, helping people with issues, few questions to check/investigate this week, also some details of testbed services improved, like available diskspace on DPMs which was not sufficient for some data management tests > + Issues to Discuss - More discussion with some developers about the release guidelines: need to clarify who is responsible for integration testing. I will have a meeting on thursday/friday with italian developers and SA1 leader (Francesco) on the issue. - KPI definition is cryptic. Difficult to produce automatic report for reliability defined as "availability - downtime not depending on SA2" > + Steps Next Week - Italian EMI meeting, with slot on testing adn testbed. - Large scale twiki setup.
    • 11:10 → 11:30
      Issue and Topics to Discuss 20m
      • AOB