oxidecomputer / oxidecomputer/omicron
Single address lot block for infra IPs is insufficient
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In wicket/RSS config we only provide the ability to specify a single address lot block for infrastructure IPs. This means for non-contiguous address sets, the resulting block is misleading. We should make it so that multiple disjoint blocks can be specified.
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 locating the Wicket/RSS configuration code that defines the infrastructure IP address lot block. Trace how that block is represented and consumed, then determine the existing configuration validation and tests. Done means non-contiguous infrastructure address sets can be specified as multiple disjoint blocks without producing a misleading combined block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100