oxidecomputer / oxidecomputer/omicron
Archive switch zone logs before rebooting scrimlets during mupdate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Rebooting scrimlets is part of mupdate. However, if we don't archive log files in the switch zone first, we may lose them, as the switch zone file system is transient. This happened on a recent Rack 2 update where a ddmd crash happened that produced a core file, but the corresponding log file was lost with the switch zone on reboot. We should consider archiving switch zone log files after the zone is shutdown, but before the host scrimlet is rebooted.
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 by tracing the mupdate flow that shuts down switch zones and reboots host scrimlets. Identify where switch-zone log files can be archived before reboot, then verify that logs survive the reboot, including the ddmd-crash case described for Rack 2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100