Upgrade to EMI-2

Start of EMI 1 decommissioning campaign on 04-03-2013

EMI 1 software will reach end of security updates and support on 30-04-2013 (http://www.eu-emi.eu/releases#MajRel).

In compliance to the EGI Service Operations Security Policy (https://documents.egi.eu/document/669) [1], unsupported software SHOULD be decommissioned before its End of Security Updates and Support, and MUST be retired no later than 1 month after its End of Security Updates and Support. After this date, if a critical vulnerability were to emerge in the software, EGI CSIRT can request the service to be turned off immediately [2].

Because of this, as of March 04 2013, Resource Centre Administrators will start getting alerts about EMI 1 products deployed in their site. Please check the list of your affected service end-points on the Operations Dashboard of your site: https://operations-portal.egi.eu/dashboard.

Purpose of these alarms is to:

1. pro-actively alert administrators about the need to upgrade EMI-1 services before they reach end of security updates and support;
2. collect information about decommissioning/upgrade plans of the affected products.

IMPORTANT. According to the EGI decommissioning policy [2], the decommissioning deadline expires one month after the end of security updates and support of the software. For EMI 1 products this is: 31-05-2013 [3].

EMI 1 software versions are in general detected through nagios tests, which query the information discovery system (BDII), on whose accuracy they depend on. On March 04 2013 alarms will be generated for the following service types (additional service types will get alarms after March 04 as soon as more tests are ready):

• ARC-CE (test: eu.egi.sec.ARC-EMI-1)
• CREAM-CE (test: eu.egi.sec.EMI-1)
• LB (test: eu.egi.sec.LB-EMI-1)
• MyProxy (eu.egi.sec.EMI-1)
• Site-BDII (test: eu.egi.sec.Site-BDII-EMI-1)
• SRM (test: eu.egi.sec.dCache-EMI-1)
• SRM (test: eu.egi.sec.StoRM-EMI-1)
• Top-BDII (test: eu.egi.sec.Top-BDII-EMI-1)
• WMS (test: eu.egi.sec.EMI-1)

DPM decommission (20-03-2013)

The EGI monitoring infrastructure is now ready for detecting DPM services whose software version is affected by one of the following conditions:

• DPM is part of the EMI 1 release or subsequent updates, thus getting unsupported after 30-04-2013
• DPM is part of the EMI 2 release or subsequent updates AND the software version is < 1.8.6.

All EMI 2 version older than 1.8.6 are affected by vulnerability EGI-SVG-2012-2683 (https://wiki.egi.eu/wiki/SVG:Advisory-SVG-2011-2683). The advisory recommends that sites update their DPM software as soon as possible.

Site administrators are requested to upgrade/retire EMI 1 DPM instances, and EMI 2 DPM instances affected by vulnerability SVG-2011-2683 by 30-04-2013. The hard decommissioning deadline is: 31-05-2013.

As of tomorrow, alarms will appear in the site operations dashboard:https://operations-portal.egi.eu/dashboard

Sites affected by DPM alarms will be contacted through a GGUS ticket by their NGI operators and will be requested to report on their upgrade plans and on any technical issue encountered.

DPM instances (EMI 1 + EMI 2 versions < 1.8.6) are detected through the following three tests:

• eu.egi.sec.DPM-EMI-1 - looking for EMI-1 DPM in GLUE1 branch (doesn't cover version 1.8.6)
• eu.egi.sec.DPM-GLUE2-EMI-1 - looking for EMI-1 DPM in GLUE2 branch (covers version 1.8.6)
• eu.egi.sec.DPM-GLUE2-EMI-2 - looking for EMI-2 DPM in GLUE2 branch with version different than 1.8.6

Tickets for the middleware update

Tickets will need to be raised against sites by ROD teams to inquire sites about their upgrade plans. A template for these tickets can be found at: https://wiki.egi.eu/wiki/ROD_MW_alarm_template#EMI_1_retirment_campaign

For these tickets the special escalation procedure will be applied which is described at: https://wiki.egi.eu/wiki/PROC01#Escalation_for_operational_problem_with_unsupported_MW_at_site.C2.A0

Information on the nagios probes

the middleware probes are executed by https://midmon.egi.eu/nagios/

Information on these probes are in https://wiki.egi.eu/wiki/MW_SAM_tests

Sites status

SITE NAME	TICKET	STATUS	ADDITIONAL INFO
BIOCOMP	14852 14896	SOLVED	sito sospeso per problemi imprevisti
CIRMMP	14854 15015	SOLVED
CNR-PROD-PISA	14902	SOLVED
CRS4	14854 14911	SOLVED
FBF-Brescia-IT	14986	SOLVED
GILDA-INFN-CATANIA	14854	SOLVED
GILDA-INFN-PADOVA	14983	SOLVED
GRISU-SPACI-NAPOLI	14874 15078 14985	SOLVED
IGI-BOLOGNA	14873	SOLVED
INAF-TS	15079	SOLVED
INFN-BARI	14876 14881	SOLVED
INFN-BOLOGNA	14853 14883	SOLVED
INFN-BOLOGNA-T3	14859 14882 14884 14994	IN PROGRESS	some issues found when installing the EMI-2 CREAMCE on sl6
INFN-CAGLIARI	14875	SOLVED
INFN-CATANIA	14862	SOLVED
INFN-CNAF-LHCB	14878 14885 14897	SOLVED	some issues found when installing the EMI-2 CREAMCE on sl6
INFN-COSENZA	14886 14898	SOLVED
INFN-FERRARA	14863 14887	SOLVED	entro il 16 marzo
INFN-GENOVA	14877 14924	SOLVED
INFN-LECCE	14871	SOLVED
INFN-LNL-2	14870 14919	SOLVED
INFN-MILANO-ATLASC	14867	OPEN
INFN-NAPOLI-ARGO	14984	SOLVED
INFN-NAPOLI-ATLAS	14868	SOLVED
INFN-NAPOLI-PAMELA	14856 14953	SOLVED
INFN-PADOVA	14865 14888 14951 14993 15002 15016	SOLVED
INFN-PARMA	14866 14912	SOLVED
INFN-PISA	14864	SOLVED
INFN-ROMA1-CMS	14860	SOLVED
INFN-ROMA2	14861	SOLVED
INFN-T1	14851 14889 14890 14892 14916 14197 14954 15021	> IN PROGRESS	some issues found when installing the EMI-2 CREAMCE on sl6
INFN-TORINO	14850	SOLVED
UNI-PERUGIA	14849	SOLVED	just updated
UNINA-EGEE	14848 14891	SOLVED

-- AlessandroPaolini - 2013-03-04