oxidecomputer / oxidecomputer/omicron
User API IP Reservations and Selection
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
IP address assignments within a VPC subnet are automatic. It would be useful to be able to reserve addresses within a VPC subnet for a few reasons.
- Precluding from automatic use.
- Assignment to specific instances.
- Integration with tooling that want's to assume particular address ranges.
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 User API entry points for VPC subnets and the code that performs automatic IP address assignment. Trace how addresses are selected and exposed through the API, then clarify the reservation and instance-assignment semantics before implementation. Done should include an agreed API and behavior for reserving addresses, preventing automatic use, and selecting them for instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100