You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7d9ced4
Browse filesBrowse the repository at this point in the historyBrowse files
CreateWorker was fabricating a capacity of one actor for every Worker it
stored. That contradicts the rule the API just adopted -- a Worker reports
every dimension it has, so an absent one is none of it -- because the
control plane was answering on the Worker's behalf before the worker had
said anything.
Nothing was calling SetWorkerCapacity, so add the reporter that makes it
real: ateom answers a new GetCapacity, atelet sweeps the node's ateoms and
forwards what they say, and a Worker holds no capacity until that lands.
ateom learns its compute limits from the downward API, since it has no
reader for its own cgroup and inventing one is a larger change. Left as a
TODO: the environment is fixed at pod creation, so it goes stale under
in-place pod resize.
0 commit comments