1. Unsupported middleware migration update
Peter Solagna – EGI.eu
OMB – 18/12/12
12/4/2018
V1.4

2. One month, what changed? Services involved 210 82
14 Nov
12 Dec
Services involved
Excluding DPM, LFC, WN
210 82
Open GGUS tickets to report unsupported middleware (opened by COD)
Excluding DPM,LFC,WN tickets
120 44
Sites eligible for suspension 4 5
DPM, WN and LFC
Still supported
Unsupported

3. The trend in the past two months in the security dashboard
Added new probes
Added new probes

4. Tickets opened in October and still open
44 Sites still deploying gLite: BDII, CREAM, LB, dCache, lcg-CE, VOMS and WMS
26 Sites who provided plans to upgrade within the end of November and failed to meet the timeline
Sites must provide a new timeline
New deadline for the upgrade was yesterday.
After that date sites must open a downtime for the affected services still deployed
18 Sites who initially reported plans beyond November already have their affected services in downtime
These tickets have been opened by COD handling alarms on the Security dashboard (not in the ROD dashboard)

5. dCache and VOMS dCache services Deadline for the upgrade 31 Jan 2013
7 sites provided plan for the upgrade
2 sites opened a downtime
1 site still unresponsive
VOMS services
15 upgraded
22 to go
8 with lack of information from sites/NGI

6. gLite DPM, LFC and WN Unsupported since Dec 1st
Alarms redirected to the usual operations (ROD) dashboard
Issues followed up by ROD and not by COD
ROD teams have been instructed to open alarm tickets using a specific template
44 DPMs
130 CEs with glite3.2 WN
Timeline expected
Dec 11th: Related alarms start to appear on ROD dashboard
ROD teams open GGUS tickets asking for a plan in 10 working days
Alarms not handled properly by ROD, and tickets assigned to unresponsive sites are escalated to NGIs and then COD
Jan 31st: all DPM, LFC and WN must be upgraded to EMI or decommissioned
ROD teams already opened ~60 tickets vs sites deploying these unsupported components

7. Not responsive sites NGI_BY, BY-UIIP NGI_DE, UNI-FREIBURG
Still alarms in the security dashboard, no downtime opened
NGI_DE, UNI-FREIBURG
NGI_AP, MY-MIMOS-GC-01
ROC_LA, UNIANDES
NGI_BG, BG-INRNE
Sites must provide an updated schedule for the upgrade and open a downtime
COD will follow up in the next two days, if there are no progress sites will be suspended

8. Next steps
Deploy a probe for GLUE2 publication, it will raise CRITICAL alarms if the site-BDII has not enabled the GLUE2 branch
Dec 19th
Add Nagios probes for ARC unsupported middleware
ARC products prior to EMI-1.0 are unsupported
Only one site affected, if confirmed probe will not be needed
Deploy probes for EMI-1 products
Under development expected by January 2013
Warning will start to appear on the operations dashboard starting from January
Turn into alarms from March
Alarms to be handled by ROD team

9. Backup slide: timeline
: GLUE2 alarms in the dashboard
: upgrade of unsupported Cache, ARC-CE, DPM, WN
: Begin of EMI-1 monitor
: Begin of critical alarms raised in ROD dashboard