oxidecomputer / oxidecomputer/propolis
Instance (re)creation from migration payload
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Up until now, when a a Propolis instance is migrated, the rough "shape" of that instance (devices, etc) is created on the target VMM using the instance specification, after which it is "re-hydrated" using the resulting migration payload. Some of the details of that target instance depend on recreating identical data during initialization, such as fw_cfg contents (see #667) or the VPD info exposed via PCI devices.
It would be nice if the migration payloads were suitably enhanced to make it possible to reliably recreate an instance from only said migration payload (perhaps excluding basic details like vCPU count, etc).
Items which still require attention:
-
fw_cfgdata - #667 - PCI VPD bits (vendor, model, etc)
- PCI capability layout
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
Review the migration-payload handling and the related work in #667. The issue identifies fw_cfg data, PCI VPD bits, and PCI capability layout as remaining areas. Done means an instance can be reliably recreated from only the migration payload, apart from explicitly excluded basics such as vCPU count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100