oxidecomputer / oxidecomputer/omicron
want regular automated testing of upgrade from last release to "main"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We've long considered this is blocked on either:
- a racklette we can use for this
- #7424 or something like it to use a4x2 in CI
It's possible we could instead build automation that uses inventron to attempt to reserve a racklette for doing this.
It's probably a fair bit of work to build reliable automation for this process. My experience from past systems like this is that it's very easy for the automation to get stuck when it finds test hardware in an unexpected state (which happens all the time when people -- or tests like this -- are deploying dev bits to this hardware).
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 reviewing the racklette, #7424/a4x2, and inventron options mentioned in the issue. Establish the automation's scope for testing an upgrade from the last release to main, including how it handles hardware in an unexpected state; done means a reliable regular CI process.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100