oxidecomputer / oxidecomputer/omicron
Ephemeral IP should ideally be released once an instance stops running
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently ephemeral IP address seems to be released only after an instance has been destroyed (probably the expected behavior per #1333). Customer will likely want to optimize external IP resources and expect the public cloud experience, i.e. free up the IP address for the next guest if the instance with it has stopped running after certain time threshold.
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
The issue names no files, tests, or entry points; start by tracing how an instance stop is handled and how ephemeral IPs are released after destruction. Before implementation, clarify the time threshold and expected reassignment behavior, then add coverage for the agreed stop-and-release lifecycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100