• Europe/Zurich
  • English
  • Login
Filter
 
Focus on:  Hide Contributions
iCal export

EMI EMT-coordination

chaired by Doina Cristina Aiftimiei (INFN)
Monday, 29 April 2013 from to (Europe/Zurich)
Video Services
Vidyo public room : EMI_EMT-coordination More Info | Join Now!
Chat rooms
EMI_EMT-coordinationMore Info|Join now!
Go to day
  • 15:25 - 15:50 EMI Releases Status Report on status of releases:

    EMI-1 (Kebnekaise)
    EMI-2 (Matterhorn)
    EMI-3 (Monte-Bianco)
    EMI Components Releases tracker

    Important Dates

    Components status:
    • Current Update Cycle - started 01.04 - to be released on 18.04.2013; Planned
      • EMI 1: -
      • EMI 2: 12 products - CREAM GE module, L&B, DPM, LFC, GFAL/lcg_util, ARC CE, Core (Clients, InfoSys, GridFTP server), EMI UI
      • EMI 3: 24 products - APEL parsers, publisher, SSM, ARC CE, Core (Clients, InfoSys, GridFTP server), ARGUS, CANl, dCache, DPM, LFC; HYDRA, glite-proxyrenewal, glite-yaim-core, gridsite, L&B, Pseudonymity, STS, UNICORE/X6, UNICORE HILA, VOMS-admin, EMI UI

    Status of testing Globus 5.2.4 Update - missing StoRM

    Status of testing XRootd 3.3.1 Update - new update was announced by MattiasE, testing & rebuild of dependent products should start ASAP - ARC & CERN DataMan planned updaes for April cycle
    Material: slides powerpoint file pdf file
  • 15:50 - 16:00 EMI Support Status Report on EMI support status
    GGUS Dashboard - EMI User support Procedure

    Support status report - as of 26.04.2013
    • 4 assigned, 0 SLA violations
    Ticket closing campaign - announced by MathildeR 
    Dear EMI product teams,

GGUS still holds 178 open tickets for EMI products (22 of them date back
to 2011, 67 were filed in 2012).
With the release of EMI-3 and its first update release the expectation
is that most of the GGUS tickets currently in an open state are solved
now and can be closed.

Therefore, for each open ticket in the support unit(s) you are
responsible for please proceed as follows:

- in case a solution has been released with EMI-3, _close_ the ticket as
_solved_

- in case a solution will be implemented with the final EMI-3 update
release, _comment_ this in the ticket

- in case a solution will not be implemented at all, _close_ the ticket
as _unsolved_

- in case a solution will be implemented in your product after the end
of EMI, _state_ this in the ticket with a realistic date, when it will
be fixed (ETA)
  • 16:00 - 16:30 AOB