oxidecomputer / oxidecomputer/omicron
[sled-agent] Re-construct Zone management state within sled agent after reboot
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Note: This issue tracks a follow-up from https://github.com/oxidecomputer/omicron/pull/686
Problem
Sled Agent should re-initialize in-memory state for managing Zones on boot, including:
- Identifying Omicron-owned zones
- Identifying their VNICs and other attached devices
- Creating in-memory structures to accurately represent their state (e.g. "RunningZone") such that they can be handled within the context of other Zones, and cleaned up accordingly.
Current workaround
As the Sled Agent "deletes all zones on initialization", we can punt on this issue slightly.
When this'll be a bigger problem
If we want to cope with Sled Agent itself crashing (without taking out all other software on the sled), this issue will become blocking.
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 reading PR #686 and the sled-agent initialization flow. Trace how initialization currently handles zones, then determine how Omicron-owned zones, their VNICs, and attached devices should be represented after reboot. Done means the in-memory state accurately reflects those zones so they can be managed and cleaned up without deleting them first.
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
- Mostly clear
- Newbie friendliness
- 35/100