Repository navigation
Rename ateom #2065
Description
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, AteomSupport and AteomHerder.
Activity
BenTheElder commentedon Oct 1, 2026
My take:
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".
annapendleton commentedon Oct 1, 2026
ateom is such a cute name 🥲
pitching some ideas that I think are still subjectively cute and expand to more than a single unit:
juli4n commentedon Oct 1, 2026
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:
HavenXia commentedon Oct 1, 2026
+1 to the renaming.
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.BenTheElder commentedon Oct 1, 2026
We might need to iterate a little on the RPC services in atelet. Will look at that more closely tomorrow.
rename ateom -> ateworker (agent-substrate#2254)