oxidecomputer / oxidecomputer/propolis
Add OPTE backend
Open
Nobody has claimed this yet.
migration
networking
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
In order to live migrate instances that use OPTE for networking, we need to be able to tell the OPTE port device to do Entity things like pause, resume, save, and restore. This requires us to
- define an
OptePortentity type, or similar - add an
Optevariant toNetworkBackendKindthat includes whatever context is needed to find the relevant OPTE port - update the server initializer to build & register OPTE backends
impl Entity for OptePortin a way that allows migration; this depends on the presence of pause/resume/save/restore IOCTLs, which are a WIP
Contributor guide
No contributing guide indexed for this repository
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 by tracing NetworkBackendKind and the server initializer to understand how existing backends are represented, built, and registered. Then inspect the Entity implementation requirements for OptePort and the stated pause/resume/save/restore IOCTL work. Done means OPTE backends can be registered and their port devices support the migration lifecycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100