Ubuntu Trusty is gone (at least, from our project) and Debian Jessie instance creation just got disabled (see {T218119}).
Therefore the following instances are not reproducible in their current state. If they get lost to a hardware failure and are not able to be set up on stretch, the service they ran may be SOL.
So it's time to begin migrating our 34 Jessie instances towards Stretch.
You'll notice a Buster prerelease image is available to deployment-prep alongside Stretch. Please don't use this unless production is running the same service on buster, or you are setting up a fresh service that will be on buster when deployed to production, or you are working on migrating the production service to buster.
The following deployment-prep instances are running Jessie:
|Name|Status/task|
|---|---|
|deployment-sessionstore01.deployment-prep.eqiad.wmflabs|New, {T218609}|
|deployment-eventgate-analytics-1.deployment-prep.eqiad.wmflabs|New, {T218609}|
|deployment-cpjobqueue.deployment-prep.eqiad.wmflabs||
|deployment-cumin.deployment-prep.eqiad.wmflabs|deployment-cumin02 set up as a replacement, just need to shut the old one down and tell people to use the new one|
|deployment-memc06.deployment-prep.eqiad.wmflabs|Buster plans for memc in {T213089}, should we go to stretch or buster? A mix of different hosts on different distros?|
|deployment-memc07.deployment-prep.eqiad.wmflabs|Buster plans for memc in {T213089}, should we go to stretch or buster? A mix of different hosts on different distros?|
|deployment-etcd-01.deployment-prep.eqiad.wmflabs||
|deployment-ms-be03.deployment-prep.eqiad.wmflabs||
|deployment-ms-be04.deployment-prep.eqiad.wmflabs||
|deployment-ms-fe02.deployment-prep.eqiad.wmflabs||
|deployment-zookeeper02.deployment-prep.eqiad.wmflabs||
|deployment-mcs01.deployment-prep.eqiad.wmflabs||
|deployment-pdfrender02.deployment-prep.eqiad.wmflabs||
|deployment-sca04.deployment-prep.eqiad.wmflabs||
|deployment-poolcounter04.deployment-prep.eqiad.wmflabs||
|deployment-fluorine02.deployment-prep.eqiad.wmflabs|prod mwlog* hosts are jessie|
|deployment-parsoid09.deployment-prep.eqiad.wmflabs||
|deployment-changeprop.deployment-prep.eqiad.wmflabs||
|deployment-imagescaler01.deployment-prep.eqiad.wmflabs|02 and 03 are stretch, plus {T216815} - is 01 needed? if not can it go, otherwise is it a candidate to become a buster testing instance?|
|deployment-ircd.deployment-prep.eqiad.wmflabs|prod host kraz is jessie|
|deployment-mathoid.deployment-prep.eqiad.wmflabs|Puppet broken due to T200832|
|deployment-memc04.deployment-prep.eqiad.wmflabs|Buster plans for memc in {T213089}, should we go to stretch or buster? A mix of different hosts on different distros?|
|deployment-memc05.deployment-prep.eqiad.wmflabs|Buster plans for memc in {T213089}, should we go to stretch or buster? A mix of different hosts on different distros?|
|deployment-restbase01.deployment-prep.eqiad.wmflabs||
|deployment-sca01.deployment-prep.eqiad.wmflabs||
|deployment-sca02.deployment-prep.eqiad.wmflabs||
|deployment-conf03.deployment-prep.eqiad.wmflabs||
|deployment-sentry01.deployment-prep.eqiad.wmflabs||
|deployment-cache-upload04.deployment-prep.eqiad.wmflabs|cache-text is stretch, can be migrated - making deployment-cache-upload05 as a replacement|
|deployment-logstash2.deployment-prep.eqiad.wmflabs||
|deployment-restbase02.deployment-prep.eqiad.wmflabs||