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)
-
- 10:30 → 10:40
-
10:40
→
11:10
Task Reports and Progress 30mIn this first meeting we will discuss on who is working on which task(s).
-
TSA2.1 – Work Package coordination 5m+ Status and Progress - Participated to the EGI- EMI meeting on repository and release. Not much to get from EGI for the moment. Will come with another proposal or will copy our proposal. + PEB Report - CERN accounts should being solved. Who still has no news about it? - Announced that the EMI repository is available and SA1 EMT agrees that will go on from there. - Templates available for deliverables, milestones and trip reports. +Issues to Discuss - Who still has no information on (lack of) participation? + Step for Next Week - Deliverable DSA2.1 is now really urgent. Internal review in SA2 and the circulation. - M2 - DSA2.1 - Quality Assurance Plan (task 2.2) Reviewers: Francesco Giacomini (SA1), Andrea Ceccanti (JRA1) - M3 - DSA2.2.1 - QA Tools Documentation (task SA2.4) Reviewers: to be defined
-
TSA2.2 – Quality Assurance Process Definition and Monitoring 5m+ Status and Progress - Second draft of SQAP sent to Technical area leaders + WP leaders + Release Manager - Started to write down the SQAP document - Started to collect information about status of the Minimum Documentation Requirements for gLite, ARC, Unicore and dCache for the first periodic QA report. gLite and ARC already done. + Issues to Discuss - None + Steps Next Week - Get first version of the SQAP approved by PEB or at least get feedback to improve it.
-
TSA2.3 – Metrics and KPIs Definition and Reporting 5m+ Status and Progress We are currently writing up a page on metrics based on the proposal document and existing metrics, taking into account the evolution of the project: https://twiki.cern.ch/twiki/bin/view/EMI/TSA23contributionToDSA41 + Issues to Discuss We must have faster feedback from product teams. If anyone in SA2 is associated with the product teams, please inform them of our requirements. + Steps Next Week Continue to expand out the list of metrics. More background reading and information gathering. Complete survey and write up results, taking top 3 metrics of each product team into account. Insert programming language statistics into the the SA2.4 tools inventory.
-
TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m+ Status and Progress - EMI repository control given to SA1 - Tools Plan document under preparation - Discussion on virtualization with CERN people + Issues to Discuss NONE + Steps Next Week - Get feedback on the plan and then start the work
-
TSA2.5 – QA Implementation Review and Support 5mStatus: Task slowly stated Discuss: minimal requirement for QA reviews before the first reporting period Next: Steps for the next week provide more detail input for SA2.2 Collect minimal requirements for QA
-
TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m+ Status and Progress We had a meeting with developers on monday with minutes here https://twiki.cern.ch/twiki/bin/view/EMI/TSA26 Still waiting for contributions from JRA1, SA1, which are expected to come with PTB decisions on M2. By the way, there is substantial agreement about proposed approach/implementation model. + Issues to Discuss - CESNET Contribution to task - What contribution are expected for SA2 Quality plan deliverable? - testbed twiki and on line material: under sa2.6 section or should we set up a different place? + Steps Next Week - Integrate draft with collected feedback from developers - Assign tasks in savannah and start working on them.
-
-
11:10
→
11:30
Issue and Topics to Discuss 20m
-
AOB
-