oxidecomputer / oxidecomputer/omicron
Clarify the usage and philosphy behind using `rack_id` and `switch_location` for association of switch port configurations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently we are using rack_id and switch_location fields for determining where a port lives. There seems to still be a bit of uncertainty with this approach, so maybe we should clarify our intentions with using these with clear documentation, or reconsider their usage (if warranted). Maybe this Issue can be used for a more focused discussion.
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
The issue names the rack_id and switch_location fields but no files or tests. Start by locating their current uses and document the intended association of switch port configurations, or record a decided change in usage. Done means the project has an agreed, clearly documented approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100