Repository navigation
Rename ateom #2065
Description
Activity
My take:
- We need a daemonset per node, durably, at minimum for the device plugin / DRA to access KVM. Call that "atelet" still. We document that it handles singleton substrate dataplane things.
- We need a concept of a "worker" which may or may not be deduped with the atelet in the future. Call it "ate-worker" (currently ateom). Taahir Ahmed (@ahmedtd) called it "ateom" back when it atomicly hosted one actor. Since [EPIC] Multi-Actor Worker Support #1266 it becamse
I'm not super attached to these names, but we should rename ASAP, because it's a breaking change for the images / binary / package paths / RPC services.
I think "worker" is generic and obvious for the RPC services, and the binary / container image can be "ate-worker".
Reacted by eliranwateom is such a cute name 🥲
pitching some ideas that I think are still subjectively cute and expand to more than a single unit:
- moleculate (molecule + ate)
- polymate (polymer + ate)
- ensemblate (ensemble + ate)
- aggregate
The concept of
Workerexists today, and it's an API resource. We need names for the agents. So this could be:ateapi: the control plane. Stays the same.atelet: the per-node agent. Stays the same.ate-worker-{gvisor, microvm}: the agent that runs within the worker pod.
For the gRPC APIs:
- Ateom -> Worker
- AteomSupport -> WorkerSupport
- AteomHerder -> Atelet
Reacted by Benjamin Elder, Jan Willies, Steven Shriver, Haven Xia and Tommy McCormick+1 to the renaming.
For the gRPC APIs:
- Ateom -> Worker
- AteomSupport -> WorkerSupport
- AteomHerder -> Atelet
I’m not entirely sure on the gRPC renaming. We already have a
WorkerServicedefined inatelet, and renamingAteomSupporttoWorkerSupportcreates potential confusion, especially that they represent two distinct hops in our call chain. That goes back to a distinct name for the in-pod agent, though.We might need to iterate a little on the RPC services in atelet. Will look at that more closely tomorrow.
- added a parent issue
on Oct 6, 2026
Evaluate whether we want to rename ateom (and maybe atelet too?) to something more descriptive.
We should also rename the gRPC services they expose as well:
Ateom,AteomSupportandAteomHerder.Benjamin Elder (@BenTheElder)