oxidecomputer / oxidecomputer/omicron
Sled slot/cubby number should be recorded in the database.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The current slot number for a sled should be recorded.
Maybe in the database with the rest of the info for a sled.
Originally: #2231
was to cover this case, but it look like it slipped through the cracks.
Having the slot in Nexus will allow the UI to display it, and customer(s!) want to see it.
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 how sled information is represented and persisted in Nexus, then identify the database and API paths that would need to carry the current slot or cubby number. Check the existing work referenced by pull request #2231. Done means the slot is recorded in Nexus and available for the UI to display, with relevant tests updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100