oxidecomputer / oxidecomputer/propolis
Lift DRAM transfer out of websocket
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
During a migration, the contents of guest DRAM must be transferred from source to destination. It is, by orders of magnitude, the largest thing which must be transferred during said process. Today it is transmitted over the same websocket used for other migration data. To avoid incurring the overhead (copying, encoding, etc) for that large data collection, propolis-server should transfer DRAM contents over a dedicated (TLS, for security) socket.
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 propolis-server's migration path and the existing websocket transport for guest DRAM and other migration data. The work is done when DRAM contents use a dedicated TLS-secured socket rather than the websocket, with the migration flow still transferring the remaining data correctly; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100