EMI EMT-coordination
→
Europe/Zurich
Doina Cristina Aiftimiei
(Istituto Nazionale Fisica Nucleare (IT))
Description
NOTE: THE MEETING IS RECORDED** (for minutes-taking only purposes, then the files are deleted)
-
-
15:00
→
15:10
Welcome
list pf participants
Mandatory & Recommended participants: ALL PTs representatives -
15:10
→
15:15
SA2 announcements
- -
- EMI Nagios probes Related Tasks / Tickets
- no. of issues increased - ALL mentioned PTs MUST confirm if the solution will be provided in EMI April Update, or not.
- SA1/SA2 presentations at 5th EMI AHM - Budapest - Joint SA1/SA2
- EPEL compliance
- NEW EPEL packages (some EMI's) needing REVIEW
- The RPMLint & Lintian reports links are here
- Description of RPMlint customizations:
- Rpmlint v 1.3
- Ignore 'no-dependency-on' locales error detected when package name ends with a locale code (such as *-en) and doesn't have locales-* package in its dependencies. This was done commenting lines 150-156 in I18NCheck.py.
- Ignore "*debuginfo" packages in the check (implemented in the plugin)
- Ignore "no-packager-tag" and "no-signature" errors, by adding these lines to Rpmlint config file:
addFilter("E: no-signature") addFilter("E: no-packager-tag")
- Description of Lintian customizations:
- use v2.5.6~bpo60+1 without any change in lintian itself
- Description of RPMlint customizations:
- would be good if the PTs update the wiki explaining where they are with EPEL compliance: EMI EPEL-Compliance twiki
-
15:15
→
15:25
EMT Action List
- EMT incidents - 30 (24 regarding RPMLint)
- -
- EMT documentation problems - 27 (18 for EMI 3)
- Many issues found during EMI 3 documentation-verification
- affected products/PTs: GFAL/lcg_utils, EMIR, VOMS, WMS, CREAM, TORQUE WN config, APEL - please COMMENT on the tasks
- It is available a twiki containing EMI Documentation problems and comments
- Many issues found during EMI 3 documentation-verification
- EMT testbed tasks
- no tasks
- EMT incidents - 30 (24 regarding RPMLint)
-
15:25
→
15:50
EMI Releases Status
Report on status of releases:
EMI Maintenance- EMI 1 Kebnekaise maintenance
- EMI 2 Matterhorn maintenance
- EMI 3 MonteBianco maintenance
- EMI Products Releases tracker
Important Dates- EMI 1 Update 24 - released: 28.03.2013
- EMI 2 Update 10 - released 03.04.2013
- EMI 3 Update 1 - released 04.04.2013
- EMI Updates schedule:
- Current Update Cycle - started 01.04 - to be released on 18.04.2013; Planned
- EMI 1: -
- EMI 2: 13 products - CREAM GE module, gLite Cluster, CREAM, L&B, DPM, LFC, GFAL/lcg_util, ARC CE, Core (Clients, InfoSys, GridFTP server), dCache
- EMI 3: 24 products - AMGA Manager, 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
- Current Update Cycle - started 01.04 - to be released on 18.04.2013; Planned
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
EMI in UMD- EMI in UMD 1 - all products status
- EMI in UMD 2 - all products status
- EMI in UMD 3 - all products status
EMI 3 Build Status- emi_B_3_dev:
- emi_R_3_rc:
EMI 2 Build Status- emi_B_2_dev
- SL5/x84_64 - 82,6%
- SL5/i386 - 78,8%
- SL6/x86_64 - 87%
- Deb6/x86_64
- SL5/x84_64 - 82,6%
- emi_R_2_rc
- SL5/x84_64 - 95,9%
- SL5/i386 - 85,8%
- SL6/x86_64 - 91,6%
- SL6/i386 - 68,9%
- Deb6/x86_64
- SL5/x84_64 - 95,9%
EMI 1 Build Status
-
15:50
→
16:00
EMI Support Status
Report on EMI support status
GGUS Dashboard & EMI User support Procedure
Setting up of the ETA - Estimated Time of Availability - slide 4 of Mathilde's presentation at EMI AHM/May 2012
Support status report - as of 12.04.2013- 4 assigned, 0 SLA violations
Ticket closing campaign - announced by MathildeRDear EMI product teams, GGUS still holds 170 open tickets for EMI products (27 of them date back to 2011, 82 were filed in 2012). With the release of EMI-3 last week the expectation was 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 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
-
15:00
→
15:10