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 article for CHEP (taking me 100% of these next days) - Completed the quarterly report. Thanks for the KPIs. - Please SA2 wiki page http://bit.ly/emisa2 as front window where all we have for others to see and get is presented From PEB: - Platforms are going to be discussed at the PTB and checked with EGI and WLCG. Debian is a likely but not urgent platform (could even be starting SL6 before). Could be different platform for servers and clients + Next Step - Any issue for PEB?
          SA2 Internal Wiki
          Sa2 Meetings
        • TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
          + Status and Progress - No progress to report this week. I couldn't work on SA2.2 this week due to other tasks I had to finish. This looks better for next week. - Release Guidelines: Alberto di Meglio sent me some feedback. I added it and now I'm waiting for final OK to announce them. - The following tasks are assigned to SA2.2 but I'm not working on them due to my workload this week. I think Alberto has assigned this to other people who can maybe give an update tomorrow: - Guidelines for Minimum Required Documentation TOC. - Review the following deliverables (I think this is also with other p: - EMI-1 DEVELOPMENT AND TEST PLANS - DJRA1.6.1 - Integration Work Plan and Status Report + Issues to Discuss - None + Steps Next Week (same as last week) - Announce the new Release Guidelines: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ReleasingGuidelines - Prepare the EMI Production Release Criteria: https://twiki.cern.ch/twiki/bin/view/EMI/ProductionReleaseCriteria - Prepare the EMI release check list: https://twiki.cern.ch/twiki/bin/view/EMI/EMIReleaseChecklist - Prepare an example of the component versioning schema we would like to propose for PTs.
        • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
          + Status and Progress * trying local and remote builds of FTS to obtain FindBugs (still not finished) * expanding/re-defining and visualising the SuccessfulBuilds metric. * reviewing SA2 CHEP paper for Alberto. * updating metric guidelines to include quick start on metric usage. * correcting the User Forum abstract including reviewers comments.
        • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
          + Status and Progress - Infrastructure: - Recover after holidays power-cuts - Migration to CVI for all build nodes - First VM provided to users - New EPEL image availble for users - EPEL packages autoinstall script - Infrastructure Monitoring script - Working on runasroot migration to CVI - Client: - Rebuild client 1.4.15 for DM after packager error - client 1.5.0 testing - ETICS Client bugfix: packager error when brp-compress gzips man pages - Support - Building/Packaging 3 externals for DM - GGUS tickets handling for problems during Christmas - New configurations for EMI requested by Cristina (6 configurations) - Problem in MyProxy build - Services: - Testing performed with Firefox 4 beta - Cancel option in the submission tab: security improvement - Memory leaks error investigation - QA: - Report generator progressing. Meeting this Friday. - PyLint plugin in progress - Coordination: - Iteration #3 started + Issues to Discuss + Steps Next Week - Work on Deliverable SA2.2.2 - Client 1.5.0 testing
        • TSA2.5 – QA Implementation Review and Support 5m
        • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
          + Status and Progress INFN-CNAF: twiki updated HW updates (kernel + voms cert) New storm for EMI-1 release: CERN: testbed administration solved issue with publishing GlueSite information on Top-level BDII corrections on CERN nagios instance (few tests of Grid services did not work properly) JUELICH: currently setting up a batch system to run jobs on several of the virtual nodes. This is to make the UNICORE installation more production like and allow for more jobs to be run in parallel. KOSICE: --- CESNET: --- DESY: worked on ticket : * https://gus.fzk.de/ws/ticket_info.php?ticket=65512 --> reason found,but had no time to fix it yet. It is a bit of a mystery why it does notcome up after restart, it seems to be a timing issue, because I can start it up by hand. * Renewing certificates and voms server entries * Error diagnosis after reconfiguring dcache instances * Getting testbed into DESY monitoring + Issues to Discuss MS24? TESTBED: Introduction of Integration Ready STATUS??? FOR EMI-1 release? Not properly a RC release BDII data verification via e.g. gstat? Service View
      • 11:10 → 11:30
        Issue and Topics to Discuss 20m
        • AOB