oxidecomputer / oxidecomputer/omicron
Operator View: Updates - what's the impact of the update?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Provide a mechanism for Nexus to identify the scope of an update.
Updates may be disruptive, requiring instance to migrate, and changing workloads. Ideally, we'd be able to communicate this in a reasonable way to users (either as an ETA, part of asynchronously communicating the update plan, or something similar).
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 examining Nexus's update flow and the Operator View requirements described in this issue; no files, tests, or entry points are named. Clarify how update scope, disruption, migration, workload impact, and user communication should be represented, then document acceptance criteria for a complete mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100