oxidecomputer / oxidecomputer/maghemite
Extend RIB for multicast path: MRIB
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
As per RFD 488:
For the API-driven strategy, the control plane, Omicron, would be entirely responsible for managing the switch MRIB and the OPTE MRIB. Particularly, the Nexus component, responsible for much of the control plane’s orchestration, would be extended to support the tracking of multicast groups and the assignment of multicast group addresses to specific sender instances. Much of the multicast machinery in the control plane will be implemented in the Nexus component carried out as an RPW (Reliable Persistent Workflow), a pattern similar to other networking mechanisms we currently have implemented in the rack.
Similar to lldp (updated through Omicron), the mcastd daemon client can update the MRIB via API calls directly.
Contributor guide
No contributing guide indexed for this repository
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 with RFD 488's MRIB population section, then inspect the Nexus control-plane component and the mcastd API path; the issue also points to lldp as a related client. No file or test is named, and completion criteria are not specified beyond extending RIB support for multicast/MRIB management, so clarify scope and validation before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100