Page MenuHomePhabricator
Create Task
Maniphest T321612

Make tf-bullseye-std point to toolforge-bullseye-sssd rather than toolforge-bullseye-standalone
Closed, ResolvedPublicFeature
Actions

Description

The "standalone" image is a very bare bones image that Brooke made for folks who are using statically compiled rust things and similar as part of T277749: [Toolforge] Generic webservice not working on Kubernetes. The standalone image does not contain the basic tools like curl, awk, and jq that we put in literally all of the other containers we publish. This makes it of very little use for most folks who will be migrating cron jobs from the grid engine to the jobs framework.

Details

SubjectRepoBranchLines +/-
deployment: refresh generic image, try to avoid the standalone imagecloud/toolforge/jobs-framework-apimain+2 -0
Customize query in gerrit

Related Objects

Event Timeline

bd808 created this task.Oct 25 2022, 7:28 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 25 2022, 7:28 PM
bd808 changed the subtype of this task from "Task" to "Feature Request".Oct 25 2022, 7:29 PM
Legoktm subscribed.Oct 26 2022, 12:51 AM

The standalone image does not contain the basic tools like curl, awk, and jq that we put in literally all of the other containers we publish. This makes it of very little use for most folks who will be migrating cron jobs from the grid engine to the jobs framework.

Wouldn't those people use a different container? Or asking a different way, after this proposed change, what's the purpose of the standalone image?

bd808 added a comment.Oct 26 2022, 5:37 PM
In T321612#8344266, @Legoktm wrote:

The standalone image does not contain the basic tools like curl, awk, and jq that we put in literally all of the other containers we publish. This makes it of very little use for most folks who will be migrating cron jobs from the grid engine to the jobs framework.

Wouldn't those people use a different container? Or asking a different way, after this proposed change, what's the purpose of the standalone image?

I honestly don't think there ever was a good reason for the standalone image as I said in T277749#6927178. But maybe my real concerns are that:

  • We do not seem to have a "language agnostic" image today for the jobs framework other than this one
  • This image shows at the top of the list of images
  • "std" expands in my head to "standard" not "standalone"
  • The documentation at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework uses --image tf-bullseye-std in every example which makes it seem like a universal solution
bd808 mentioned this in T294607: Add zstd package to tf-bullseye-std toolforge-jobs image.Oct 26 2022, 5:51 PM
gerritbot added a comment.Nov 28 2022, 1:15 PM

Change 861388 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[cloud/toolforge/jobs-framework-api@main] deployment: refresh generic image, try to avoid the standalone image

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

gerritbot added a project: Patch-For-Review.Nov 28 2022, 1:15 PM
aborrero subscribed.Nov 28 2022, 1:20 PM

For the record:

aborrero@tools-k8s-control-1:~$ sudo -i kubectl get all -A -l app.kubernetes.io/managed-by=toolforge-jobs-framework -o yaml | egrep standalone
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      imageID: docker-pullable://docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone@sha256:d9d1018b87439cdbe4df2244927c7a02cc420f123f52ccba2baa4f95749a793d
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      imageID: docker-pullable://docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone@sha256:d9d1018b87439cdbe4df2244927c7a02cc420f123f52ccba2baa4f95749a793d
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      imageID: docker-pullable://docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone@sha256:d9d1018b87439cdbe4df2244927c7a02cc420f123f52ccba2baa4f95749a793d
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
      imageID: docker-pullable://docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone@sha256:d9d1018b87439cdbe4df2244927c7a02cc420f123f52ccba2baa4f95749a793d
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
              image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
          image: docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
gerritbot added a comment.Nov 30 2022, 10:14 AM

Change 861388 merged by Arturo Borrero Gonzalez:

[cloud/toolforge/jobs-framework-api@main] deployment: refresh generic image, try to avoid the standalone image

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

Maintenance_bot removed a project: Patch-For-Review.Nov 30 2022, 10:30 AM
aborrero closed this task as Resolved.Nov 30 2022, 10:46 AM
aborrero claimed this task.
tools.arturo-test-tool@tools-sgebastion-11:~$ toolforge-jobs images | grep bullseye
tf-bullseye-std             docker-registry.tools.wmflabs.org/toolforge-bullseye-sssd:latest
tf-bullseye-std-DEPRECATED  docker-registry.tools.wmflabs.org/toolforge-bullseye-standalone:latest
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits