Skip to content

temporarily drop device support - #1389

Merged
Tim Hockin (thockin) merged 2 commits into
agent-substrate:mainfrom
BenTheElder:drop-device-support
Sep 2, 2026
Merged

temporarily drop device support#1389
Tim Hockin (thockin) merged 2 commits into
agent-substrate:mainfrom
BenTheElder:drop-device-support

Conversation

@BenTheElder

Copy link
Copy Markdown
Collaborator

See: #752 (comment)

TLDR: I think we need to rethink how we express devices.

This PR drops the user facing support, while retaining some other bits around CDI for-reuse when we're ready.

containerd applies CDI to a pod's containers, and actor containers sit underneath
one, so whatever gives an actor a device reads the spec itself. Split by how far
it travels: internal/cdi parses a spec and resolves what a named set of devices
asks for, which any sandbox can use, while cmd/ateom-gvisor/internal/cdiinject
applies the result to a bundle on disk and stats the host for device numbers,
which only suits a sandbox on the host kernel.

The NVIDIA specifics -- which devices, which hooks may run, which library
directories -- are caller options rather than package globals. No behavior change,
and the tests run on any host rather than Linux only.
A GPU worker pool injected its devices into every container of every actor on it,
which only held up while a worker ran one actor.

A resource name and a count cannot replace it: that shape cannot express which
container gets a device, sharing one between containers, or resuming onto hardware
compatible with the snapshot. A nvidia.com/gpu pool limit is now an ordinary
extended resource -- it places the pod on a GPU node and nothing else reads it.

internal/cdi stays, unused: whatever the API becomes, an ateom still has to merge
CDI edits into an actor's bundle itself.
@thockin

Copy link
Copy Markdown
Collaborator

Merging

@thockin
Tim Hockin (thockin) merged commit 7535180 into agent-substrate:main Sep 2, 2026
9 checks passed
@BenTheElder
Benjamin Elder (BenTheElder) deleted the drop-device-support branch September 2, 2026 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants