EMI SA2 Weekly Meeting

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

Wednesday 30 Jun 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 - Followed Open Issues with the PEB. In particular platforms and 2.5 task. See action list. - CESNET in contact now, not very happy of the collaboration proposed. No news from GRNET. - CERN accounts all solved. - Templates available for deliverables, milestones, trip reports and PRESENTATIONS. We must us the templates available for presentations. - EMI repo is been filled. GLite and ARC in. No UNICORE last time I checked. - User support SA1 has clarified the role of first level support. - PTB is collecting the PTs development plans. Area leaders are consolidating the individual PT plans to come up with a more consistent area workplan. +Issues to Discuss - We receive very little feedback but is our interest to have the users clearly exposed to the proposals (and not come later to give us problems...). Should we organize presentations (phone conf) of the Deliverable and Milestones? PEB, first then PTs. All together? + Step for Next Week - Deliverable DSA2.1 reviewed. We should have several iterations. But would include the PEB soon. - 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
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress Defining a template for metric descriptions Defining coding metrics including PTs input, process metrics based on DSA2.1 draft. SA 2.3 metrics meeting on Thursday morning at 10:30CEST. + Issues to Discuss Who has been the beneficiaries of the Savannah statistics in the past projects? How have the statistics improved the Q/A process in the past? + Steps Next Week Define real metrics based on coding tools and process lifecycle. Categorize according to middleware applicability and programming language. Ensure the tools actually work and are reasonable (this will be ongoing work).
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Finalizing the Tools Plan to be sent out tonight/tomorrow + Issues to Discuss - Internal task tracking in SA2.4 + Steps Next Week (for SA2.4) - Write Milestone report out of the tools plan - Take over Jira from TOM - Install an EMI ETICS instance - Collect feedback of the plan - ETICS bugfixes (repository and client) - Repository extraction into a separate service - Externals import tool
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress task participants are known + Issues to Discuss input from PB what is the most important to check in the first 3 months + Steps Next Week Distribution of subtasks for first 3 months If no proposal from PB we may concentrate on -review of proposed plans -communication channels -existence an functionality of basic tools for -project management -QSAP metrics
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress * Submitted Savannah tasks under group EMI-SA2 deriving from proposed draft planof testbed implementation and started working on them. (high priority 16285, 16300, 16304, 16305, 16306, 16337, 16307; medium priority 16308, 16309; low priority 16311,16310, 16301) o task 16304: defined a basic template for testbed description, and each server status logbook o task16285: created a squad for sa2.6, will be used for tracking testbed requests o task 16337: opened on the sa26 squad: requested to all members to fill the twiki with HW currently available for testbed (mentioned in the survey) + Issues to Discuss * One point in savannah task is the way we communicate with developers aand track actions on them. We asked 1 person for PT to be involved in testbed activities. PT replied it is better to use savannah squads (for redundancy), but we have a technical issue in savannah: can't create more squads than members in a group so we should ask all PT members to join savannah and sa2 group. Is that ok? Do other SA2 tasks have similar needs? should we coordinate the request to join savannah groups? + Steps Next Week * task 16337: opened on the sa26 squad: requested to all members to fill the twiki with HW currently available for testbed (mentioned in the survey). Tracking available HW and service installed with the new template standard * task 16307: survey on what services in task 16337 have nagios, plan to monitor all services in sa2 testbed.
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB

Choose timezone

EMI SA2 Weekly Meeting

CERN