oxidecomputer / oxidecomputer/omicron
Host OS composite artifact will soon have multiple ROM images
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Right now the host OS artifact contains both the phase 1 and phase 2 images for Gimlet. In Cosmo, we will have a new phase 1 image. Currently oxidecomputer/helios#196 tracks how this will change (still tbd). However, whatever logic we have for picking out and assuming image/rom is appropriate for Gimlet is not going to work in the face of Cosmo. This will likely have impacts in everything from wicket through to nexus itself.
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 with oxidecomputer/helios#196, which tracks the pending Cosmo image changes, then trace where the host OS artifact assumes image/rom from wicket through nexus. Done means the artifact and downstream logic can handle Gimlet and Cosmo having multiple ROM images without relying on the current single-image assumption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100