oxidecomputer / oxidecomputer/opte
`InnerFlowId` should be a per-`NetworkImpl` concept
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
We don't yet have any other NetworkImpl, much less one that would require a different FlowId type. Plumbing this through would be quite an involved task. When we do so, we want it to use the trait FlowId introduced in #990 -- at that time we should also move the trait into opte_api.
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 with the linked lib/opte/README.adoc lines 109-113 and review the FlowId trait introduced in #990. Trace how InnerFlowId is currently tied to NetworkImpl, then assess the plumbing needed to make it per-NetworkImpl and move the trait into opte_api. Done means the concept is correctly separated without requiring a different FlowId type for the current implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100