Page MenuHomePhabricator

Cloud VPS "packaging" project Buster deprecation
Closed, ResolvedPublic

Description

Upstream LTS support for Debian Buster ends on June 30, 2024, and soon after that we'll need to start deleting and removing those VMs.

Please either remove Buster VMs from your project or respond here with a proposed plan and timeline.

Buster VMs remaining after July 15th with no activity on their associated phab task will be shut down and/or deleted at the convenience of WMCS administrators.

Remaining Debian Buster instances (live report):

Listed administrators are:

See also:

More info on current project instances is available via openstack browser

Event Timeline

StrikerBot triaged this task as Medium priority.Fri, Jun 14, 2:46 PM
StrikerBot created this task.

packager02.packaging.eqiad1.wikimedia.cloud

According to the etherpad upgrade docs this host is used to build the etherpad Debian package. I also used the host in the past to build the etherpad package. The dedicated host is used because "etherpad builds fetches npm modules during the build time".

packager02.packaging.eqiad1.wikimedia.cloud

According to the etherpad upgrade docs this host is used to build the etherpad Debian package. I also used the host in the past to build the etherpad package. The dedicated host is used because "etherpad builds fetches npm modules during the build time".

When rebuilding it on Bullseye or Bookworm, best to expliclitly name it etherpad-build1001 or so.

packager02.packaging.eqiad1.wikimedia.cloud

According to the etherpad upgrade docs this host is used to build the etherpad Debian package. I also used the host in the past to build the etherpad package. The dedicated host is used because "etherpad builds fetches npm modules during the build time".

This is probably a good time to discuss whether it makes sense to move etherpad to Kubernetes (aux-k8s cluster?). We now know more that we used to and should be able to make it happen. That should also free us from the maintenance burden of keeping around and sharing knowledge of these things.

It might be possible to schedule another Etherpad upgrade (T362432) before the packager02.packaging.eqiad1.wikimedia.cloud host is deleted.

Instead of creating another packaging VM on Bookworm, we should consider either investigating the move of Etherpad to Kubernetes, as suggested by @akosiaris, or migrating to GitLab and wmf-debci, if feasible.

builder-envoy-03.packaging.eqiad1.wikimedia.cloud

Any objections to just remove the VM since we moved to (re-)packaging upstream (https://wikitech.wikimedia.org/wiki/Envoy#Building_envoy_for_WMF)?

builder-envoy-03.packaging.eqiad1.wikimedia.cloud

Any objections to just remove the VM since we moved to (re-)packaging upstream (https://wikitech.wikimedia.org/wiki/Envoy#Building_envoy_for_WMF)?

None from me.

Change #1049180 had a related patch set uploaded (by Jelto; author: Jelto):

[operations/puppet@production] package_builder: don't install python-all on bookworm

https://gerrit.wikimedia.org/r/1049180

Change #1049180 merged by Jelto:

[operations/puppet@production] package_builder: don't install python-all on bookworm

https://gerrit.wikimedia.org/r/1049180

I created the bookworm host packager-etherpad01.packaging.eqiad1.wikimedia.cloud to replace packager02.packaging.eqiad1.wikimedia.cloud. I successfully rebuilt Etherpad version 1.9.7 (the current production version) on the new bookworm host.

I have shut down the old host and will delete it tomorrow. I updated the Etherpad documentation to point to the new host. Besides that, I did not find any other Wikitech documentation referencing this machine. From examining the old instance, it was used for building etherpad-lite and logstash-plugins (a very old version 0.0.1). So, cc @fgiunchedi because it's in your home directory.

Jelto updated the task description. (Show Details)

I deleted packager02.packaging.eqiad1.wikimedia.cloud, which was the last buster instance. So I'll resolve the task. All buster instances are replaced or deleted.