This page keeps track of our ongoing effort towards Debian Stretch deprecation, which happened upstream on July 6, 2021.
Tell me exactly what I need to do
Cloud VPS project maintainers
- Check https://os-deprecation.toolforge.org/ for reports about your project(s)
- For each reported deprecated instance:
- Create a new instance using Debian Bullseye (longest time until future deprecation) or Debian Buster
- Move content and configuration from the old Stretch instance to the new instance
- If you are using a web proxy on the old instance, delete the proxy and the add a new one with the same name pointing at the new instance
- Shutdown the old Stretch instance
- Update any maintainer documentation to reference the new instance rather than the old Stretch instance
- When you are sure you have all the content and configuration moved, delete the old Stretch instance
If you need additional quota to create new virtual machine instances, follow the instructions on Phabricator to request a temporary quota increase.
Toolforge tool maintainers
TBD; that said, the following webservice types for the kubernetes backend are already based on Buster containers:
The following are based on Bullseye containers:
Why are we doing this?
On July 6, 2021 the Debian project stopped providing security patch support for the Debian 9 "Stretch" release. It did, however, move to LTS support and will receive updates other than backports from the LTS team.
Timelines. What will change? What has changed already?
Cloud VPS projects
The timeline for the remainder of the process is:
- In August 2021, create a Phabricator task, a page on Wikitech. An announcement needs to be scheduled and set up.
- January 1st, 2022: Stretch VM creation disabled in all projects, deprecation nagging begins in earnest.
- May 1, 2022: All active Stretch VMs will be shut down (but not deleted) by WMCS admins.
- June 30, 2022: LTS support for Debian Stretch ends, all Stretch VMs will be deleted by WMCS admins
- See News/Toolforge_Stretch_deprecation
- Some Kubernetes runtimes are currently using Debian Stretch as a base layer. The Toolforge administration team will be working to ensure that suitable Buster/Bullseye replacements are available.
- The Toolforge Kubernetes cluster used Debian Buster instances for its control plane and runtime environment. No work is needed there at this time.
- Alternatvies to Stretch will be available for tool migration in Toolforge
- Stretch grid nodes will be shut down