Difference: UgradePlansToEMI2 (19 vs. 20)

Revision 202013-03-20 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Upgrade to EMI-2

Line: 45 to 45
 
  • Top-BDII (test: eu.egi.sec.Top-BDII-EMI-1)
  • WMS (test: eu.egi.sec.EMI-1)
Added:
>
>

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
Line: 64 to 87
 
CNR-PROD-PISA 14902 SOLVED  
CRS4 14854 14911 IN PROGRESS entro il 28 marzo
GILDA-INFN-CATANIA 14854 SOLVED  
Changed:
<
<
GRISU-SPACI-NAPOLI 14874 IN PROGRESS entro aprile
>
>
GILDA-INFN-PADOVA 14983 OPEN  
GRISU-SPACI-NAPOLI 14874 14985 IN PROGRESS entro aprile
 
IGI-BOLOGNA 14873 IN PROGRESS aggiornamento nelle prossime settimane
INFN-BARI 14876 14881 IN PROGRESS testing the new CE
INFN-BOLOGNA 14853 14883 IN PROGRESS entro Marzo (18 - 22)
Line: 78 to 102
 
INFN-LECCE 14871 OPEN  
INFN-LNL-2 14870 14919 IN PROGRESS aggiornamento graduale delle macchine, comunque entro il 30 aprile
INFN-MILANO-ATLASC 14867 OPEN  
Added:
>
>
INFN-NAPOLI-ARGO 14984 OPEN  
 
INFN-NAPOLI-ATLAS 14868 IN PROGRESS entro il 19 aprile
INFN-NAPOLI-PAMELA 14856 14953 IN PROGRESS entro il 19 aprile (SE pił avanti)
INFN-PADOVA 14865 14888 14951 IN PROGRESS la prossima settimana
View topic | History: r41 < r40 < r39 < r38 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback