oxidecomputer / oxidecomputer/omicron
Make instance start saga trigger NAT RPW when available
Open
Nobody has claimed this yet.
nexus
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Once #3593 is fixed, the step in the instance start saga that updates switches' instance NAT state should be replaced with a step that triggers the NAT RPW.
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 reviewing issue #3593, then locate the instance start saga and its step that updates switches' instance NAT state. Trace how the NAT RPW is triggered when available and determine the expected saga behavior. Done means that step has been replaced without breaking the instance-start flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100