The list below matches the criteria:
- Status: Active in Netbox
- Replacement date (= 5 years from purchase for servers, 8 years for most other equipment) is before 2019-07-01.
Effectively, this means that this is equipment that should had already been replaced in the fiscal years FY15-16, FY16-17, FY17-18 and FY18-19.
The asks here are:
- Track down all existing decom/replacement tasks where they exist and link them here
- If a replacement is underway (e.g. msw1-eqiad, scs-a8-eqiad), execute it with priority
- Reach out to service owners to get those tasks unstuck if they exist or...
- Reach out to service owners to ask them to start replacing their hardware ASAP and file procurement and/or decom tasks when tasks do not exist.
This is old to very old (2011-era!) hardware and is affecting our capability to plan and maintain. In some cases it may just be just forgotten decoms (e.g. labsdb1002-array1) or wrong statuses in Netbox.
Due to the FY20-21 planning being already in motion, I'd like to ask for this to be fully fleshed out (replacements planned and underway, most if not all equipment on this list decommissioned) **by mid-April** at the latest. That way we can use FY19-20 budget for some of these if necessary. @wiki_willy, do you think that's feasible?
| **Hostname** | **Purchase date** | **Replacement date** | **Suggested refresh** | **Decom/replacement task** | **Notes** |
| analytics1028-1041 | 2014-06-26 | 2019-06-26 | FY18-19 | T227485 | Currently used for Kerberos migration, decom at end of quarter, will be replaced by T242148 |
| bismuth | 2014-05-01 | 2019-05-01 | FY18-19 | T248516 | |
| dbproxy1002-1003 | 2011-01-27 | 2016-01-27 | FY15-16 | T245384 | @marostegui |
| dbproxy1007-1011 | 2011-01-27 | 2016-01-27 | FY15-16 | T228768 T245385 | @Marostegui |
| es2001-es2004 | 2011-10-31 | 2016-10-31 | FY16-17 | T222592 | @Marostegui |
| fmsw-c8-codfw | 2009-01-01 | 2017-01-01 | FY16-17 | T253154 | Upgrading in Q1 #dc-ops |
| francium | 2014-05-01 | 2019-05-01 | FY18-19 |T249903 | decom blocked by T242009 |
| ganeti1001-1004 | 2014-03-24 | 2019-03-24 | FY18-19 | T255553 | @akosiaris |
| helium | 2011-01-27 | 2016-01-27 | FY15-16 | T260717| No refresh. It has been already superseded by backup1001. @jcrespo/@akosiaris |
| heze | 2012-12-13 | 2017-12-13 | FY17-18 | T260717| No refresh. It has been superseded by backup2001 @jcrespo/@akosiaris |
| labsdb1002-array1 | 2013-02-27 | 2018-02-27 | FY17-18 | T146455 | |
| msw1-eqiad | 2010-11-23 | 2018-11-23 | FY18-19 | T225121 | upgrading via T225121 |
| msw-a1-eqiad - msw-a8-eqiad | 2011-02-18 | 2019-02-18 | FY18-19 | T259758 | Upgrading in Q2 #dc-ops |
| msw-b1-eqiad - msw-b8-eqiad | 2011-02-18 | 2019-02-18 | FY18-19 | T259758 | Upgrading in Q2 #dc-ops |
| msw-a1-codfw - msw-a8-codfw | 2009-01-01 | 2017-01-01 | FY16-17 | T259758 | Upgrading in Q2 #dc-ops |
| msw-d4-codfw | 2009-01-01 | 2017-01-01 | FY16-17 | T259758 | Upgrading in Q2 #dc-ops |
| oresrdb1001-1002 | 2014-05-01 | 2019-05-01 | FY18-19 | T254238, T254240 | No refresh. @akosiaris |
| samarium | 2013-01-22 | 2018-01-22 | FY17-18 | T197630 | |
| scb1001-scb1004 | 2013-01-11 | 2018-01-11 | FY17-18 | | No refresh. The cluster is to be decomissioned, services move to kubernetes. @akosiaris |
| scs-a8-eqiad | 2011-02-02 | 2019-02-02 | FY18-19 | T228919 | #dc-ops Upgrading via T228919 |
| tungsten | 2011-01-27 | 2016-01-27 | FY15-16 |T260395 | Currently running XHGui, being migrated to Ganeti instances in T180761 - xhgui* now on buster, just waiting for data migration from MongoDB now @dzahn |