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 - No PEB. Alberto DM will distribute the offical news from now on. - Asked for review of Testbeds deliverable and of Quarterly Report - Review starts today 22/9 - Metrics and Guidelines should be completed and used. - GGUS for Testbeds and tools? - "EMI Testbeds" and "EMI Tools" or "EMI QA ..." ? - Deliverables and Milestones TODO DSA2.2 - QA Tools Documentation 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
        + Status and Progress - Applying comments to QA Periodic Report. Waiting for more feedback before creating and uploading a new version. - Reminded pending actions on Change Management Guidelines. + Issues to Discuss - pending actions on Change Management Guidelines. + Steps Next Week - Changes in the SQAP. See: https://twiki.cern.ch/twiki/bin/view/EMI/SQAP#Forseen_changes
      • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
        + Status and Progress - Meeting last week to discuss ETICS XML format for Metrics - TestCoverage will change to UnitTestCoverage metric. A few other small changes resulted from last weeks discuss. - Each metric must have a set of defined inputs and units for those inputs. So far we've just had defined outputs and their units. - Bringing static code analysers into line with ETICS defined analysers. + Issues to Discuss - Can each middleware produce a MySQL dump of their bug-tracker with deleted tables to retain privacy? - Is each middleware prepared to assist in defining the exchange format mapping, but let ETICS/SA2.3 produce the Python/XML/SQLITE3 queries on the dumped database to produce the metrics? - Is a daily dump agreeable, pending a bug-tracking dump being agreeable? + Steps Next Week - Finish input definitions in Internal Metrics document. - seek agreement on database dumping. - define prototype ETICS code for PriorityBugs metric for all middlewares.
      • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
        + Status and Progress - Moving to CERN Virtual Infrastructure - Convert VMDK images to VHD format. - Deploy Hiper-V testing VM. - Testing the new Hyper-V VM. - Several meetings with CVI group. - Testing ETICS release 3.1 - Multi-Node bugfixes - ETICS Support - Cleaning GGUS tickets - Fixing runasroot not cleaned nodes - Problems JDK and apr-util externals - Scripting POSTINSTALL in ETICS Packager - Investigation on Jira Administration features for Cristina - Meeting about Metrics XML exchange format - Multi-Node Testing presentation available for public + Issues to Discuss + Steps Next Week - Deliverable
      • TSA2.5 – QA Implementation Review and Support 5m
        + Status and Progress -5.4 -test plans for all ARC PTs - discussions and preparation -twiki page (testing and certification guidelines) -basic procedures to test scalability in Unicore information was taken from e-mail. + Issues to Discuss Last week I proposed to change input of metric calculations (bugs instead metrics). I verified that to collect information about bugs in ARC Bugzilla is technically possible- set of MySQL queries. The output a) remote access or b)report in XML format. I assume that projects or PTs will afraid to provide these data. However,one of advantage of this approach is that all input data are consistent and calculation of metrics could be uniform. -creation of twiki page where test plans of PTs will be collected. + Steps Next Week -First draft of ARC PTs test plans. -gathering information about status of test plans
      • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
        + Status and Progress - Contacted Mathilde Romberg from SA1, about the setup of GGUS Support Unit for emi-testbed + VO testers.emi.eu - administration of servers - Unicore HW resources should be available on Sept. 28. + Issues to Discuss + Steps Next Week - Updates on deliverable depending on GGUS SU setup - DSA2.4 review feedback?
    • 11:10 → 11:30
      Issue and Topics to Discuss 20m
      • AOB