oxidecomputer / oxidecomputer/omicron
wicket should detect some kinds of miscabling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We had an issue with a rack where the backplane connections for a PSC and a sidecar had gotten swapped. Wicket happily displayed this: when looking at the details for PSC 0, it showed the details of a sidecar, and vice versa.
Wicket may not be able to detect all kinds of miscabling (e.g., if two gimlets are swapped; I think this would require querying both switches to detect, and even then isn't guaranteed to find it?), but it certainly check for "this thing I think is a {sled,switch,psc} is claiming to be something else", and:
- Color the slot(s) red in the overview
- Refuse to perform updates of the miscabled slots
- Refuse to kick off RSS
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 entry points for the overview, PSC/sidecar details, update operations, and RSS behavior. Identify where reported device identity can be compared with the expected sled, switch, or PSC type, then verify that miscabled slots are marked red and excluded from updates and RSS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100