ROD MW alarm template
Revision as of 06:39, 19 March 2013 by Tferrari (talk | contribs) (→DPM: Retirement campaign of EMI 1 versions and EMI 2 versions < 1.8.6)
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
EGI Infrastructure Operations Oversight menu: | Home • | EGI.eu Operations Team • | Regional Operators (ROD) |
This page provides templates for the tickets which should be send by ROD team to sites in case of software version or service type decommission campaign.
DPM: Retirement campaign of EMI 1 versions and EMI 2 versions < 1.8.6
Dear site administrators, According to our monitoring, your site is running a DPM software version that needs to be upgraded. Purpose of this ticket is to notify you about the need to update your DPM software and to collect information about your upgrade plans. DPM 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 EMI 2 v. 1.8.6, please report a false positive in this ticket. Why should your DPM service be updated? One of these cases may apply to you. (1) You are running a EMI 1 DPM software version EMI 1 software will reach end of security updates and support on 30-04-2013 (http://www.eu-emi.eu/releases#MajRel). 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) - see the details below. (2) You are running a EMI 2 DPM software version affected by vulnerability EGI-SVG-2012-2683 (https://wiki.egi.eu/wiki/SVG:Advisory-SVG-2011-2683). All DPM versions older than EMI2 1.8.6 are affected. The advisory recommends that sites update their software as soon as possible. With this ticket we request you two actions: ACTION 1. PROVIDE FEEDBACK ABOUT YOUR UPGRADE PLANS Please provide information about you upgrade plans according to the following template. Information about your upgrade plans must be supplied within 10 working days from the date this ticket is received. ***************************************************** TEMPLATE Your site name: Affected service end-points (please list them): Expected date for the completion of the upgrade of the end-points above (specify target date): Technical issues preventing you from upgrading (provide input only if applicable): ***************************************************** ACTION 2. UPGRADE of DPM Side 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 decommissioning hard deadline is: 31-05-2013 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). If you decide to decommission services, please follow the appropriate procedure PROC12: http://wiki.egi.eu/wiki/PROC12 as the community must be informed about your decommissioning of services. HOW TO HANDLE THIS TICKET Please provide feedback about your upgrade plans within 10 working days from the date this ticket is received. If you think the DPM instances detected are a false positive, please report this in the ticket. Also report any technical issue that may prevent you from upgrading according to the proposed timeline. Site administrators who provide information about their upgrade plans MUST NOT close a ticket until the alarm disappears in the site Operations Dashboard (https://operations-portal.egi.eu/dashboard). Please keep the ticket in status "in progress" until the DPM service is decommissioned or upgraded. Thanks for your cooperation. ROD team Information about the probes used to detect DPM software versions 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 The probes are documented at: https://wiki.egi.e/wiki/MW_SAM_tests#Middleware_monitoring_SAM_instance
EMI 1 retirement campaign
Dear site administrators, According to our monitoring, your site is running EMI 1 software, which will reach end of security updates and support on 30-04-2013 (http://www.eu-emi.eu/releases#MajRel). Please check the list of affected service end-points on the Operations Dashboard of your site: https://operations-portal.egi.eu/dashboard EMI 1 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 1, please report a false positive in this ticket. 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) - see the details below. With this ticket we request you two actions: 1. PROVIDE FEEDBACK ABOUT YOUR UPGRADE PLANS Please provide information about you upgrade plans according to the following template. Information about your upgrade plans must be supplied within 10 working days from the date this ticket is received. ***************************************************** TEMPLATE Your site name: Affected service end-points (please list them): Expected date for the completion of the upgrade of the end-points above (specify target date): Technical issues preventing you from upgrading (provide input only if applicable): ***************************************************** 2. UPGRADE of EMI 1 SERVICES Side administrators are requested to upgrade/retire unsupported software before it gets unsupported (by 30-04-2013). The decommissioning deadline expires one month after the end of support of the software, for EMI 1 products this is: 31-05-2013 * https://wiki.egi.eu/wiki/Software_Retirement_Calendar#Decommissioning_Calendar_EMI1 * https://wiki.egi.eu/wiki/PROC16#Decommissioning_deadline 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). If you decide to decommission services, please follow the appropriate procedure PROC12: http://wiki.egi.eu/wiki/PROC12 as the community must be informed about your decommissioning of services. HOW TO HANDLE THIS TICKET Please provide feedback about your upgrade plans within 10 working days from the date this ticket is received. Site administrators who provide information about their upgrade plans MUST NOT close a ticket until the alarm disappears in the site Operations Dashboard (see link above). Please keep the ticket in status "in progress" until all unsupported products are either decommissioned or upgraded. Thanks for your cooperation. ROD team
gLite 3.2 DPM, LFC and/or Worker Nodes campaign
Dear site administrators, According to our monitoring, your site is running gLite 3.2 DPM, LFC and/or Worker Nodes, whose software reached end of life on 30-11-2012. Please check the list of affected service end-points on the Operations Dashboard of your site: https://operations-portal.egi.eu/dashboard gLite software products 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 supported, please report a false positive in this ticket. This ticket is to warn you about the deployment of unsupported gLite 3.2 DPM and/or WN software in your site and to request an upgrade/decommissioning of these according to the following guideline. 1. PROVIDE FEEDBACK ABOUT YOUR UPGRADE PLANS Please provide information about you upgrade plans according to the following template. Information about your upgrade plans must be supplied within 10 working days from the date this ticket is received. TEMPLATE Your site name: Affected service end-points (please list them): Expected date for the completion of the upgrade of the end-points above (specify target date): Technical issues preventing you from upgrading (provide input only if applicable): 2. UPGRADE of gLite 3.2 UNSUPPORTED DPM/LFC/WN DEADLINE for the upgrade/decommissioning is: 31-01-2013 End-points that cannot be upgraded by that time, must be put in downtime as of: 01-02-2013 Resource Centres that do not respond to this ticket, do not provide acceptable plans and timelines, or show no progress risk suspension. Suspension does *not* concern Resource Centres that are actively working to solve the issue, have documented plans with acceptable timelines, or are facing technical issues that prevent them from decommissioning/upgrading unsupported products. If you decide to decommission services, please follow the appropriate procedure PROC12: http://wiki.egi.eu/wiki/PROC12 - the community must be informed about the decommissioning of services. HOW TO HANDLE THIS TICKET Please provide feedback about your upgrade plans within 10 working days from the date this ticket is received. Site administrators who provide information about their upgrade plans MUST NOT close a ticket until the alarm disappears in the site Operations Dashboard (see link above). Please keep the ticket in status "in progress" until all unsupported products are either decommissioned or upgraded. Thanks for your cooperation. ROD team