The toolforge-jobs containers command should indicate which containers are deprecated. This data is available on https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes#Available_container_types, afaik it's not available anywhere programmatically, webservice hardcodes the list of containers.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| containers: store information in a ConfigMap | cloud/toolforge/jobs-framework-api | main | +76 -45 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • JHedden | T251027 "signatures" tool has failed job pods on Kubernetes cluster | |||
| Resolved | aborrero | T251917 Design the Jobs service in k8s | |||
| Resolved | aborrero | T283238 Toolforge: develop jobs-framework-api | |||
| Resolved | aborrero | T285944 Toolforge: beta phase for the new jobs framework | |||
| Resolved | Feature | aborrero | T287077 toolforge-jobs: Indicate which containers are deprecated |
Event Timeline
Comment Actions
The current approach as of this writing to avoid the harcoded container list is to fetch them from the registry at API startup time.
If we need to store some additional metadata in the source code, then fetching the list is pointless and we could probably just go the webservice route and hardcode them.
We could introduce a deprecated string everywhere near the container name when listing, so users listing their jobs could clearly identify jobs using deprecated images (like we do with glance images @ CloudVPS), for example:
$ toolforge-jobs show myscheduledjob +------------+-----------------------------------------------------------------+ | Job name: | myscheduledjob | +------------+-----------------------------------------------------------------+ | Command: | ./read-dumps.sh myargument | +------------+-----------------------------------------------------------------+ | Job type: | schedule: * * * * * | +------------+-----------------------------------------------------------------+ | Container: | tf-buster-std (deprecated) | <------- +------------+-----------------------------------------------------------------+ | File log: | yes | +------------+-----------------------------------------------------------------+ | Resources: | mem: 10Mi, cpu: 100 | +------------+-----------------------------------------------------------------+ | Status: | Last schedule time: 2021-06-30T10:26:00Z | +------------+-----------------------------------------------------------------+ | Hints: | Last run at 2021-06-30T10:26:08Z. Pod in 'Pending' phase. State | | | 'waiting' for reason 'ContainerCreating'. | +------------+-----------------------------------------------------------------+
Comment Actions
Change 706458 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):
[cloud/toolforge/jobs-framework-api@main] containers: store information in a ConfigMap
Comment Actions
Change 706458 merged by Arturo Borrero Gonzalez:
[cloud/toolforge/jobs-framework-api@main] containers: store information in a ConfigMap
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2021-07-22T15:30:41Z] <arturo> pushed new docker image on the registry for toolforge-jobs-framework-api 4d8235b879adbac9122a968b4335cf2bafee2b61 (T287077)