oxidecomputer / oxidecomputer/hubris
Tracking Issue: Improve visibility and handling of Fan Failures
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
A focus for hubris devices in the near future is to improve our detection, reporting, and remediation of failure of cooling fans, as well as ensuring that our handling of replacement of field-serviceable fans is behaving correctly.
There are some low hanging fruit here, including adding new ereports for various unusual conditions. There is also likely some design required to better capture data observed in the lead-up to a fan failure.
This issue aims to serve as a "table of contents" of work planned under this umbrella.
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
This is a tracking issue rather than a scoped implementation task, and it names no files, tests, or entry points. Start by breaking the umbrella into concrete work for fan-failure detection, reporting, remediation, and field-serviceable replacement handling; each resulting task should define its code location, validation, and done criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100