nestybox / nestybox/sysbox-ipc
SetupDevices RPC and Device messages for DRA/CDI GPU passthrough
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 19
- Avg merge
- 2h 10m
- Merged PRs (30d)
- 1
Description
Need
sysbox-runc and sysbox-mgr must coordinate which host device nodes belong to a container as part of the DRA/CDI GPU passthrough feature.
Today the IPC interface has no message to carry that device set, so the feature cannot be plumbed end-to-end.
Proposal
Add a SetupDevices gRPC RPC to the sysbox-mgr IPC proto, plus supporting Device / request / response messages, wired through grpcServer.go (the ServerCallbacks field + handler) and grpcClient.go (client wrapper).
The regenerated sysboxMgrProtobuf.pb.go is gitignored and rebuilt by make.
Benefits
Gives sysbox-mgr a clean, typed channel to tell sysbox-runc which device nodes (e.g. NVIDIA MIG capability nodes) to set up for a container, enabling GPU/MIG passthrough for system containers driven by DRA/CDI.
Part of a 3-repo feature (see sysbox-mgr and sysbox-runc PRs).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IPC proto and inspect existing RPC patterns in grpcServer.go and grpcClient.go. Add the SetupDevices RPC with its Device, request, and response messages, wire the ServerCallbacks handler and client wrapper, then run make to regenerate sysboxMgrProtobuf.pb.go and verify the interface builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100