Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    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
          - Completed the quarterly report for quarter Nov-Jan. Thanks for the input and the KPIs. PEB: - Focused only on EMI 1 release - On having checklists for teams to quickly know what to do. - Training for testbeds, tools and policies - Platforms for EMI 1 SL5/64, with EPEL - Question: Can the testbed be used at the EGI TF for training purposes? EGI: - Meeting with the Quality Control and received their guidelines https://documents.egi.eu/public/ShowDocument?docid=240 We need to review the generic QC and compare them to ours (is probably quite quick for the authors of the policies + SA2.5?). I asked JRA1 and PTB to review the ones about the technical matters. Access needs registration on the EGI portal * Compute Capabilities Quality Criteria * Data Quality Criteria -----> Generic Quality Criteria * Information Capabilities Quality Criteria * Operations Capabilities Quality Criteria * Security Capabilities Quality Criteria * Storage Capabilities Quality Criteria - EGI UF and EMI TF joint conference. https://www.egi.eu/indico/sessionDisplay.py?sessionId=13&confId=207#20110412 - Participation from the task leaders? - EMI All Hands Meeting. Lund University from 30 May-1 June 2011. http://indico.cern.ch/conferenceDisplay.py?confId=124206 + Next Step - Training, testbeds, metrics reports, verification of the releases of the PTs (with QC)
          SA2 Internal Wiki
          Sa2 Meetings
        • TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
          + Status and Progress The process to change policies has changed and it's described here: - https://twiki.cern.ch/twiki/bin/view/EMI/SQAP#Guidelines_for_the_Policies The following documents have been finished this week and are pending PEB approval: - New Certification Policy : https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2TestPolicy - Testing Policy: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2CertPolicy https://twiki.cern.ch/twiki/bin/view/EMI/EMITestReport https://twiki.cern.ch/twiki/bin/view/EMI/EMITestPlan - Check list: https://twiki.cern.ch/twiki/bin/view/EMI/EMIReleaseChecklist + Issues to Discuss SA1 should clarify Component Release Testing (deployed internally or in the tested?) and Integration Testing (before or after certification). + Steps Next Week - Get green light from PEB to announce these documents to EMT. - Update Change Management Guidelines with changes in task tracker - Keep on renaming twikis guidelines -> Policy - Write Release Criteria to help QC verify CR.
        • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
        • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
          + Status and Progress Infrastructure: - Creating runasroot EPEL VMs - High profile VM benchmark and production deployment - Many VMs deployed in the infrastructure Process: - Packaging Policy review (Discussions with ARC ongoing) - EMT presentation of the client releases and new process - List of incorrect package.prefix in the EMI project - EGI Meeting on repositories and release.xml ETICS: - Client 1.5.0 and 1.5.1 released - Nightly builds changed to EMI 1 RC0 - EMI RC0 troubleshooting and brainstorming - Support: Tried to clean the support unit. Andres closed 21 tickets, Lorenzo and Alberto also closed some other tickets and we still have 13 open (last Wednesday there were 15)) :( * 21 GGUS tickets closed * 12 new configurations for EMI asked by Critina * 13 new externals registered * 5 existing configurations modified twice (requested by the user) * 1 new user registered * Investigated matching problem with EPEL RunAsRoot machines (some works sent by ADM were not matching) * Helped with a Maven configuration problem * Debugged with Gianni his multi node test QA: - PyLint in progress (no reports lately) - In the process of building the report generator with ETICS - Creating template in JasperReports for nightly metrics updates, with sections for each product team and product. + Issues to Discuss - SA2.2.2 to be discussed with PEB about timing. Deadline extension asked. + Steps Next Week - Tools availability and configuration for EMI 1 RC0 and RC1 - Deploy Minimal EPEL image in production - SA2.2.2 ??
        • TSA2.5 – QA Implementation Review and Support 5m
        • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
          + Status and Progress ALL: • Meeting about EMI1-RC0 deployment plan • new HW installation, waiting for GGUS mail triggering RC0 available to be installed • Meeting about Testbed training preparation • Meeting about training adobe tool • Preparation of material for training CNAF: • meeting with Florida about EMI-Rollout. Probably will be merged with Large Scale testbed activity. Need to involve Release manager, Maria, SA1 into it. + Issues to Discuss • GGUS tkt triggering deployment? + Steps Next Week • EMI-RC0 deployment on sites • Testebed training preparation.
      • 11:10 → 11:30
        Issue and Topics to Discuss 20m
        • AOB