Decommission of EMI-2 and upgrade to EMI-3
Start of EMI-2 decommissioning campaign on 03-03-2014
The EMI-2 software will reach end of security updates and support on 30-04-2014 (Official EMI page
)
In compliance to the EGI Service Operations Security Policy
(
https://documents.egi.eu/document/669), unsupported software SHOULD be
decommissioned or updated to a supported version 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 shut
down immediately (
https://wiki.egi.eu/wiki/PROC16#Policy).
Because of this, as of March 03 2014, Resource Centre Administrators will
start getting alerts about EMI 2 products deployed in their site. The list of
the affected service end-points will be available 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-2 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 (
https://wiki.egi.eu/wiki/PROC16#Policy), the
decommissioning deadline expires one month after the end of security updates
and support of the software.
For EMI 2 products the hard deadline is: 31-05-2014 (
https://wiki.egi.eu/wiki/Software_Retirement_Calendar#Decommissioning_Calendar_EMI2).
EMI 2 software versions are in general detected through nagios tests, which
query the information discovery system (BDII), on whose accuracy they depend
on.
Decommissioning Calendar EMI2
The EMI 2 decommissioning deadline is 31-05-2014.
Details:
- by 01-03-2014: new EMI 2 version probes are tested returning WARNING
- on 05-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard
- 30-04-2014: end of security updates and support of EMI 2
- 31-05-2014: EMI 2 decommissioning deadline after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime.
Affected middleware version
- ARC v2.*
- ARGUS v1.5.*
- BDII Site older than v1.2.0
- BDII Top older than v1.1.0
- CREAM v1.14.*
- dCache v2.2.*
- DPM older than v1.8.6
- EMI-UI v2.*
- EMI-WN v2.*
- FTS v.2.2.8
- StoRM older than v.1.11.0
- VOMS v.2.*
Operations Calendar EMI2
- From 03-03-2014 Nagios probes (run by a dedicated EGI instance of SAM) will detected unsupported service end-points according to the version information available from BDII - where possible. Probes detecting unsupported service end-points, will generate alarms that can be tracked by administrators on the site operations dashboard.
- After 03-03-2014 administrators of the affected Resource Centres will receive notification tickets, and will be requested to provide information about their upgrade plans within 10 working days from the day the ticket is received.
GGUS Ticket template for RODs
Dear site administrators,
According to our monitoring, your site is running EMI 2 software,
which will reach end of security updates and support on 30-04-2014
(http://www.eu-emi.eu/releases#MajRel).
EMI 2 software versions are detected through queries to the information
discovery system (BDII). Information published should accurately reflect
the version of the running software, however, if you think the software
run by the service end-points indicated in the dashboard is not EMI 2,
please report a false positive in this ticket.
Please check the nagios failing probes:
<link ai test di nagios che falliscono>
Unsupported software MUST be retired no later than 1 month after its
End of Security Updates and support (https://wiki.egi.eu/wiki/PROC16#Policy)
In case of upgrade:
EMI-3 generic guide: https://twiki.cern.ch/twiki/bin/view/EMI/GenericInstallationConfigurationEMI3
EMI-3 product page: http://www.eu-emi.eu/products
In case of service decomission, please follow the appropriate
procedure PROC12: http://wiki.egi.eu/wiki/PROC12 as the community must
be informed about your decommissioning of services.
Please provide feedback about your upgrade plans within 10 working days
from the date this ticket is received.
Resource Centres that do not respond to this ticket, do not provide
acceptable upgrade plans and timelines, or show no progress risk suspension
after the decommissioning deadline (https://wiki.egi.eu/wiki/PROC16#Policy).
Production services status
Information got from gridit-bdii-01.cnaf.infn.it on Feb 11th 2014:
$ ldapsearch -x -LLL -H ldap://gridit-bdii-01.cnaf.infn.it:2170 -b GLUE2GroupID=grid,o=glue "(&(objectclass=GLUE2Endpoint)(GLUE2EntityOtherInfo=MiddlewareVersion=2.*))" GLUE2EntityOtherInfo GLUE2EndpointURL
| SITE NAME |
HOSTNAME |
EMI-2 VERSION |
 |
|
ADDITIONAL INFO |
| INFN-ROMA1-CMS |
cmsrm-bdii.roma1.infn.it |
2.0.0-1 |
| INFN-NAPOLI-ARGO |
argoce01.na.infn.it |
2.10.1-1.el5 |
| INFN-NAPOLI-ARGO |
argodpm01.na.infn.it |
2.10.1-1.el5 |
| INFN-FRASCATI |
atlasbdii.lnf.infn.it |
2.10.3-1.el5 |
| INFN-ROMA1 |
atlas-bdii.roma1.infn.it |
2.10.6-1.el5 |
| INFN-ROMA1 |
atlas-ce-01.roma1.infn.it |
2.10.2-1.el5 |
| INFN-ROMA1 |
atlas-ce-02.roma1.infn.it |
2.10.5-1.el5 |
| INFN-FRASCATI |
atlasce1.lnf.infn.it |
2.10.4-1.el5 |
| INFN-FRASCATI |
atlasce3.lnf.infn.it |
2.10.3-1.el5 |
| INFN-ROMA1 |
atlas-creamce-01.roma1.infn.it |
2.10.3-1.el5 |
| INFN-ROMA1 |
atlas-creamce-02.roma1.infn.it |
2.10.2-1.el5 |
| INFN-FRASCATI |
atlasse.lnf.infn.it |
2.10.4-1.el5 |
| INFN-GENOVA |
bdii02.ge.infn.it |
2.10.6-1.el5 |
| CIRMMP |
bdii-enmr.cerm.unifi.it |
2.10.6-1.el6 |
| INFN-CAGLIARI |
bdii-site.ca.infn.it |
2.10.3-1.el5 |
| INFN-BOLOGNA |
oce.bo.infn.it |
2.10.1-1.el5 |
| INFN-CAGLIARI |
cecream.ca.infn.it |
2.10.1-1.el5 |
| CIRMMP |
ce-enmr.cerm.unifi.it |
2.10.6-1.el6 |
| INFN-PADOVA |
cert-39.pd.infn.it |
2.10.6-1.el5 |
| UNI-PERUGIA |
cex.grid.unipg.it>/strike> |
2.10.6-1.el5 |
| INFN-ROMA1-CMS |
cmsrm-cream01.roma1.infn.it |
2.10.5-1.el6 |
| INFN-ROMA1-CMS |
cmsrm-cream02.roma1.infn.it |
2.10.2-1.el5 |
| INFN-ROMA1-CMS |
cmsrm-cream03.roma1.infn.it |
2.10.5-1.el6 |
| INFN-GENOVA |
creamce01.ge.infn.it |
2.10.5-1.el5 |
| INFN-PERUGIA |
cream-ce.pg.infn.it |
2.10.0-1.el6 |
| CRS4 |
egridglitece.crs4.it |
2.10.0-1.el5 |
| UNINA-EGEE |
emi-ce01.scope.unina.it |
2.10.6-1.el6 |
| INFN-PADOVA |
eu-india-03.pd.infn.it |
2.10.6-1.el5 |
| GILDA-INFN-PADOVA |
gilda-02.pd.infn.it |
2.10.6-1.el6 |
| INFN-FERRARA |
grid0.fe.infn.it |
2.10.5-1.el6 |
| AREA-BO |
grid1.ira.inaf.it |
2.10.6-1.el5 |
| INFN-PISA |
gridbdii0.pi.infn.it |
2.10.4-1.el5 |
| INFN-PAVIA |
grid-bdii.pr.infn.it |
2.10.4-1.el6 |
| INFN-PISA |
gridce0.pi.infn.it |
2.10.2-1.el5 |
| INFN-PISA |
gridce1.pi.infn.it |
2.10.2-1.el5 |
| INFN-PISA |
gridce2.pi.infn.it |
2.10.0-1.el5 |
| INFN-PISA |
gridce3.pi.infn.it |
2.10.5-1.el5 |
| INFN-PISA |
gridce4.pi.infn.it |
2.10.5-1.el5 |
| INFN-PAVIA |
grid-ce.pv.infn.it |
2.10.2-1.el5 |
| INFN-ROMA1 |
grid-cert-03.roma1.infn.it |
2.10.6-1.el5 |
| SNS-PISA |
gridce.sns.it |
2.10.2-1.el6 |
| INFN-PAVIA |
grid-se.pv.infn.it |
2.10.1-1.el5 |
| INFN-FERRARA |
gridsite.fe.infn.it |
2.10.1-1.el6 |
| GRISU-UNINA |
grisuse.scope.unina.it |
2.10.1-1.el6 |
| GRISU-UNINA |
grisusitebdii.scope.unina.it |
2.10.6-1.el6 |
| UNI-PERUGIA |
ng-ce.grid.unipg.it |
2.10.4-1.el5 |
| CIRMMP |
pbs-enmr.cerm.unifi.it |
2.10.6-1.el6 |
| INFN-PADOVA |
prod-ce-01.pd.infn.it |
2.10.4-1.el5 |
| INFN-PADOVA |
prod-se-02.pd.infn.it |
2.10.6-1.el5 |
| INFN-PADOVA |
prod-ui-02.pd.infn.it |
2.10.6-1.el6 |
| RECAS-NAPOLI |
recasna-ce01.unina.it |
2.10.5-1.el6 |
| RECAS-NAPOLI |
recasna-sitebdii.unina.it |
2.10.6-1.el6 |
| UNINA-EGEE |
se.scope.unina.it |
2.10.1-1.el6 |
| INFN-TORINO |
se-srm-00.to.infn.it |
2.10.4-1.el6 |
| UNINA-EGEE |
sitebdii.scope.unina.it |
2.10.6-1.el6 |
| INFN-TORINO |
t2-bdii-01.to.infn.it |
2.10.2-1.el6 |
| INFN-MILANO-ATLASC |
t2-bdii.mi.infn.it |
2.10.3-1.el6 |
| INFN-LNL-2 |
t2-ce-01.lnl.infn.it |
2.10.1-1.el6 |
| INFN-TORINO |
t2-ce-01.to.infn.it |
2.10.5-1.el6 |
| INFN-LNL-2 |
t2-ce-02.lnl.infn.it |
2.10.1-1.el6 |
| INFN-LNL-2 |
t2-ce-03.lnl.infn.it |
2.10.1-1.el6 |
| INFN-LNL-2 |
t2-ce-04.lnl.infn.it |
2.10.1-1.el6 |
| INFN-MILANO-ATLASC |
t2-ce-04.mi.infn.it |
2.10.5-1.el6 |
| INFN-LNL-2 |
t2-ce-05.lnl.infn.it |
2.10.1-1.el6 |
| INFN-LNL-2 |
t2-ce-06.lnl.infn.it |
2.10.1-1.el6 |
| INFN-NAPOLI-ATLAS |
t2-dpm-01.na.infn.it |
2.10.6-1.el5 |
| INFN-LNL-2 |
t2-sbdii.lnl.infn.it |
2.10.2-1.el5 |
| INFN-ROMA1-VIRGO |
virgo-ce.roma1.infn.it |
2.10.1-1.el6 |
| INFN-LECCE |
bdii-1.le.infn.it |
2.2.0-1 |
| INFN-PAVIA |
grid-bdii.pv.infn.it |
2.4.0-1 |
| INFN-PISA |
gridce5.pi.infn.it |
2.5.1-1 |
| INFN-CATANIA |
alifarm10.ct.infn.it |
2.6.1-1 |
| INFN-BOLOGNA |
bobdii.bo.infn.it |
2.6.1-1 |
| INFN-ROMA3 |
ce-01.roma3.infn.it |
2.6.1-1 |
| INFN-NAPOLI-CMS |
cmsse02.na.infn.it |
2.6.1-1 |
| INFN-PARMA |
emi-ce.pr.infn.it |
2.6.1-1 |
| GRISU-COMETA-INFN-CT |
infn-se-03.ct.pi2s2.it |
2.6.0-1 |
| CIRMMP |
se-enmr.cerm.unifi.it |
2.6.1-1 |
| INFN-BOLOGNA-T3 |
sgbo-t3.cr.cnaf.infn.it |
2.6.1-1 |
| INFN-BOLOGNA-T3 |
cebo-t3-03.cr.cnaf.infn.it |
2.7.1-1 |
| INFN-CAGLIARI |
grid003.ca.infn.it |
2.8.0-1 |
| INFN-ROMA3 |
gridsrv-02.roma3.infn.it |
2.8.0-1 |
| AREA-BO |
arcserv.ira.inaf.it |
2.9.0-1 |
| INFN-NAPOLI-ATLAS |
atlasce02.scope.unina.it |
2.9.0-1 |
| INFN-LECCE |
ce-1.le.infn.it |
2.9.0-1 |
| UNINA-EGEE |
ce.scope.unina.it |
2.9.0-1 |
| INFN-TRIESTE |
gridbdii.ts.infn.it |
2.9.0-1 |
| GRISU-UNINA |
grisuce.scope.unina.it |
2.9.0-1 |
| RECAS-NAPOLI |
recasna-se01.unina.it |
2.9.0-1 |
TICKETS STATUS
--
AlessandroPaolini - 2014-02-11
Home 
Site map
CEMon web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Account 
Copyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.