Ubuntu Trusty is gone (at least, from our project) and Debian Jessie instance creation just got disabled (see T218119: Disable jessie VM creation in VPS).
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. Buster is now released and available publicly, go nuts.
The following deployment-prep instances are running Jessie:
|deployment-memc04.deployment-prep.eqiad.wmflabs||WIP, Buster plans for memc in T213089: Upgrade memcached cluster to Debian Stretch/Buster|
|deployment-memc05.deployment-prep.eqiad.wmflabs||WIP, Buster plans for memc in T213089: Upgrade memcached cluster to Debian Stretch/Buster|
|deployment-memc06.deployment-prep.eqiad.wmflabs||WIP, Buster plans for memc in T213089: Upgrade memcached cluster to Debian Stretch/Buster - is this one used though? See subtask|
|deployment-memc07.deployment-prep.eqiad.wmflabs||WIP, Buster plans for memc in T213089: Upgrade memcached cluster to Debian Stretch/Buster - is this one used though? See subtask|
|deployment-changeprop.deployment-prep.eqiad.wmflabs||Appears at T198901|
|deployment-cpjobqueue.deployment-prep.eqiad.wmflabs||Appears at T198901|
|deployment-mcs01.deployment-prep.eqiad.wmflabs||Appears at T198901|
|deployment-restbase01.deployment-prep.eqiad.wmflabs||Appears at T198901, but we're doing T250574|
|deployment-restbase02.deployment-prep.eqiad.wmflabs||Appears at T198901, but we're doing T250574|
|deployment-sca01.deployment-prep.eqiad.wmflabs||Runs eventstreams, graphoid, recommendation-api, and apertium, which all appear at T198901|
|deployment-sca02.deployment-prep.eqiad.wmflabs||Runs eventstreams, graphoid, recommendation-api, and apertium, which all appear at T198901|
|deployment-sca04.deployment-prep.eqiad.wmflabs||Appears to just run recommendation-api which appears at T198901|
|deployment-imagescaler01.deployment-prep.eqiad.wmflabs||02 and 03 are stretch, plus T216815: Upgrade Thumbor to Buster - is 01 needed? looks like it serves as a memc host for the other imagescalers, can we give that responsibility to one of the others?|
|deployment-etcd-01.deployment-prep.eqiad.wmflabs||prod etcd* hosts are jessie - T224549: Track remaining jessie systems in production - some work might be done in T239835: setup new, buster based, kubernetes etcd servers for staging/codfw/eqiad cluster though our one is not for k8s|
|deployment-fluorine02.deployment-prep.eqiad.wmflabs||prod mwlog* hosts are jessie - T224565: Migrate mwlog/udp2log servers to Buster|
|deployment-ircd.deployment-prep.eqiad.wmflabs||prod host kraz is jessie - T224579: Migrate irc.wikimedia.org/kraz to Buster|
|deployment-sentry01.deployment-prep.eqiad.wmflabs||spoke to tgr, SRE might be making Sentry inside k8s later this year, in the mean time this is currently unused but people may want to use it to test frontend logic - probably no point migrating it to stretch though|
|deployment-logstash2.deployment-prep.eqiad.wmflabs||WIP, see subtask|