oxidecomputer / oxidecomputer/omicron
Expose routing fanout/max_paths as a RIB concept and not a BGP-specific concept
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently the only way to set routing information base (RIB) fanout in maghemite from omicron is through the BgpConfig member max_paths. Maghemite has generalized this concept to cover static routing and BGP. The omicron API should be updated to reflect that max_paths is a general routing property of a switch RIB and not something that is BGP specific.
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
Trace how BgpConfig.max_paths is represented in the omicron API, then inspect the routing and RIB concepts used by maghemite. Confirm how static routing and BGP share this property; done means max_paths is exposed as a general switch RIB setting rather than only through BgpConfig.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100