EMI SA2 Weekly Meeting 20100609

Meeting Information

• Indico Agenda: http://indico.cern.ch/categoryDisplay.py?categId=3001
• Action List: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ActionList
• Mailing List Archive: http://mail.eu-emi.eu/mailman/private/emi-sa2/
• Wiki for SA2 Internal: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2-internal

Actions Review

• A.Aimar - Learn/setup EVO conferencing for the WP. DONE

• A.Aimar - Prepare wiki page describing how to use the infrastructure, wiki, mailing list, indico, etc... Started, to be completed

• A.AImar - Publish the members of the mailing list DONE

• Partners send the representatives for the TSA2.2 task (QA Process Definition and Monitoring) DONE

• Testbeds survey should be completed and sent to D.Dongiovanni by end of the week. Danilo will send a first proposal by end of next week DONE, a proposal will be made next week

• G.Pucciani will set up a first task in Savannah. DONE, but not all tasks are adopting this solution

• All partners should send clarifications about who participates to each task. DONE

New Action: New participants need to have an account.

Minutes

Participants:(in the disorder, mail me if I have forgoteen your name)

Marek Kocan, Jozef Cernak, , Giuseppe Fiameni, Andrea Ceccanti, Claudio Cacciari, Danilo Dongiovanni Gianni Pucciani, Tomasz Wolak, Maria Alandes Pradillo, Andres Abad Rodriguez, Alberto Resco Perez, Bjoern Hagemeier Anders Waananen, Eamonn Kenny, Alberto Aimar

Task Reports and Progress

TSA2.1 – Work Package coordination (Task leader: CERN, all partners participate to the meetings and reviews)
This task deals with the regular coordination of the Work Package, reporting and review of milestones and deliverables.

• CERN Accounts are needed for external new participants. Participants to EGEE and previous projects should have their accounts re-activated.

• Decision on Meeting Minutes: Was agreed that the minutes of meeting should be created in the wiki pages and linked from the meeting's agenda.

---

TSA2.2 – Quality Assurance Process Definition and Monitoring (Task leader: CERN. Participants: CINECA, INFN, UPJS)
This task deals with the definition of a standard compliant software engineering process and the continual activity of monitoring its correct application within the activities of the EMI project. The success criteria of this task are the availability of an agreed, documented and regularly updated process and the minimization of deviation in its application by the project members

• Maria Alandes Pradillo will be the Task leader.
• DSA2.1 Software Quality Plan is for M1 will be probably given a bit more time.
• She contacted C.Cacciari and J.Cernak. Claudio already replied.
• A list of all processes will be prepared and discussed.
• A.Aimar noted that a first proposal is needed next week for the deliverable.
• G.Fiameni asked for a task meeting in the week as he is leaving next week. Was agreed that the contibutions shoudl be written before such meeting is organised.
• G.Fiameni (SA1) and A.Ceccanti (JRA1) are leading the Quality Control tasks in the other WPs.

Action:

• Partners send the representatives for the TSA2.2 task (QA Process Definition and Monitoring)

TSA2.3 – Metrics and KPIs Definition and Reporting (Task leader: CERN. Participants: TCD)
This task deals with the definition and continual collection and reporting of software quality metrics according to the A�QCM model or other suitable models. This task provides information to the Project Executive Board and other project This task provides information to the Project Executive Board and other project decisional bodies on the status of the software as an instrument to take corrective actions. The success criteria of this task are the regular production of reports and their use to identify improvement areas

• E.Kenny asked for input from ARC on the metrics and KPIs.
• Input will be from the existing tools, metrics and previous experience in other grid projects.
• A kick-off meeting is already scheduled for the following day (Thu 10 June).
• Metrics and KPIs will be calculated and then the consequences are that the reports will describe metrics below thresholds in detail. Reports will be automatically generated and then sent to the PEB which will decide on actions.
• E.Kenny added that more manual reviews should also check that the PTs do not fudge the metrics by artificially pass the threshold
• A,Abad reported that he is preparing the list of metrics that are currently extracted in ETICS.

TSA2.4 – Tools and Repositories Selection, Maintenance and Integration (Task leader: CERN. Participants: CINECA, GRNET, INFN, UPJS)
This task deals with the definition and when necessary maintenance of the tools required to support the QA process. The task includes any supporting activity to software providers to integrate required information to and from other tools maintained outside the EMI project. The task also include the setup and maintenance of repositories for storing the EMI software packages, tests, build and test reports and metrics generated during all software development activities within EMI.

• L.Dini reported that the kick-off meeting done, and a wiki is describing minutes, actions and how do work was split.
• An inventory of all tools used and known is beeing made.
• No answer from ARC yet, needs input from the other tasks (SA2.2 for processes and SA2.3 for metrics and KPIs)
• created several subtasks all doing inventory (repository, build, etc )
• A proposal will be made next week.
• The repository is now available for the release managers.

TSA2.5 – QA Implementation Review and Support (Task leader: UPJS. Participants: CERN, INFN, TCD, UPJS)
This task includes review activities of the QA, test and certification implementations done by the Product Teams, such as sample review of test plans and tests, compliance with packaging and porting guidelines, validation of and tests compliance with packaging and porting guidelines validation of documentation, etc. The task also includes supporting the Product Teams in effective design and implementation of tests to be used with testing tools such as ETICS. The success criterion for this task is the correct usage of tools and procedures by all project members to be measured by regular surveys and verifications

• Jozef Cernak reported that they could participate to the 2.2 and 2.4 tasks.

TSA2.6 – Testbeds Setup, Maintenance and Coordination (Task leader: INFN. Participants: CERN CESNET FZJ)
This task consists in the setup and maintenance of distributed testbeds for the project continuous integration and testing operations and the coordination and provision of larger�scale testbeds from collaborating resource providers. The success criteria for this task are the availability and reliability metrics of the execution nodes.

• D.Dongiovanni asked for mailing lists specific to the "testbed" task.
• A deadline for the answer to the survey is needed. Was agreed that the answer should be provided by end of the next week.

New Action: A.Aimar asks for creation of mailing lists emi-sa1, sa2, etc

Issue and Topics to Discuss 25'

• AOB
  • Timesheets for May will be filled with the ones of June, when PPT will be ready

Next Steps:

-- AlbertoAimar - 03-Jun-2010