EMI EMT-coordination
-
-
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
- 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
- The RPMLint & Lintian reports links are here
-
15:15
→
15:25
EMT Action List
- EMT incidents
- no changes in the last week
- EMT documentation problems
- 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
- EMI 3 RC deployment
- EMI 1 Update 24 RC deployment
- EMI 2 Update 10 RC deployment
- EMI 3 Update 1 RC deployment
- EMT incidents
-
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 23 - released: 28.01.2013
- EMI 2 Update 9 - released 21.02.2013
- EMI 3 (Monte Bianco) - released 11.03.2013
- EMI Updates schedule:
- Next Update Cycle - started 04.03 - to be released on 21.03.2013; Planned
- EMI 1: CREAM, CEMon
- EMI 2: HYDRA, Pseudonymity
- EMI 3: ARGUS-EES, CREAM, CREAM LSF/TORQUE/SLURM modules, BLAH, Cluster, FTS3, SLURM WN config
- Next Update Cycle - started 04.03 - to be released on 21.03.2013; Planned
Status of testing Globus 5.2.4 Update - new update was announced by MattiasE - missing DataManagement, CESNET Security, L&B, 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
EMT report - RfCs status - RfCs reported StoRM - planned Update??, ARC - planned update in April,- RfC listing Dashboard
- 3 for gLite Cluster - planned for April Update
- 2 for StoRM (as above)
- 3 for ARC (as above)
- 2 for L&B - planned fro April update
EMI in EGI/UMD status - to be updated
EMI 3 Build Status- emi_B_3_dev:
- emi_R_3_rc:
EMI 2 Build Status- NBs _dev status - TO BE STOPPED
- SL5/x84_64 - 72,1%
- SL5/i386 - 79,1%
- SL6/x86_64 - 87,2%
- Deb6/x86_64
- SL5/x84_64 - 72,1%
- RC - NBs status:
- SL5/x84_64 - 90,5%
- SL5/i386 - 85,6%
- SL6/x86_64 - 98,7%
- SL6/i386 - 68,5%
- Deb6/x86_64
- SL5/x84_64 - 90,5%
EMI 1 Build Status
- SL5/64b - 85,8% - errors on the new emi-lcgdm-R_1_8_6, FTS (missing m4.macros.location), ARGUS - PDP & PAP, Delegation Java, WMS, CREAM, StoRM (missing cgsi_plugin_voms_gsoap_2.7_cpp),
- SL5/32b - 50,2%
-
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 22.03.2013- 9 "LESS URGENT" 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