Tags:
, view all tags

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)

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 TICKETSorted ascending STATUS ADDITIONAL INFO
UNINA-EGEE 14848 14891 IN PROGRESS per la fine di marzo
UNI-PERUGIA 14849 SOLVED just updated
INFN-TORINO 14850 OPEN  
INFN-T1 14851 14889 14890 14892 OPEN  
BIOCOMP 14852 14896 IN PROGRESS entro il 16 marzo
INFN-BOLOGNA 14853 14883 IN PROGRESS entro Marzo (18 - 22)
CIRMMP 14854 IN PROGRESS aggiornamenti a partire dal 20 marzo
CRS4 14854 OPEN  
GILDA-INFN-CATANIA 14854 OPEN  
INFN-NAPOLI-PAMELA 14856 OPEN  
INFN-BOLOGNA-T3 14859 14882 14884 IN PROGRESS entro Marzo (18 - 22)
INFN-ROMA1-CMS 14860 IN PROGRESS entro questa settimana
INFN-ROMA2 14861 IN PROGRESS entro il mese
INFN-CATANIA 14862 OPEN  
INFN-FERRARA 14863 14887 IN PROGRESS entro il 16 marzo
INFN-PADOVA 14865 14888 IN PROGRESS la prossima settimana
INFN-PISA 14865 OPEN  
INFN-PARMA 14866 OPEN  
INFN-MILANO-ATLASC 14867 OPEN  
INFN-NAPOLI-ATLAS 14868 IN PROGRESS entro il 19 aprile
INFN-LNL-2 14870 IN PROGRESS aggiornamento graduale delle macchine, comunque entro il 30 aprile
INFN-LECCE 14871 OPEN  
IGI-BOLOGNA 14873 IN PROGRESS aggiornamento nelle prossime settimane
GRISU-SPACI-NAPOLI 14874 IN PROGRESS entro aprile
INFN-CAGLIARI 14875 OPEN  
INFN-BARI 14876 14881 OPEN  
INFN-GENOVA 14877 IN PROGRESS fine marzo/inizio aprile
INFN-CNAF-LHCB 14878 14885 14897 IN PROGRESS by next week
INFN-COSENZA 14886 14898 IN PROGRESS  
CNR-PROD-PISA 14902 IN PROGRESS il CE è già aggiornato, il test fallisce perchè il site-bdii sta pubblicando informazioni vecchie
-- AlessandroPaolini - 2013-03-04
Edit | Attach | PDF | History: r41 | r10 < r9 < r8 < r7 | Backlinks | Raw View | More topic actions...
Topic revision: r8 - 2013-03-06 - AlessandroPaolini
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback