oxidecomputer / oxidecomputer/omicron
Tracking issue for saga idempotency safety
Open
Nobody has claimed this yet.
nexus
Testing & Analysis
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This issue tracks testing that invoking all actions / undo actions within a saga "twice" is safe, and results in the same output as being called once.
- Instance create: https://github.com/oxidecomputer/omicron/pull/2095
- Instance delete: https://github.com/oxidecomputer/omicron/pull/2096
- Disk create: https://github.com/oxidecomputer/omicron/pull/2097
- Disk Delete: https://github.com/oxidecomputer/omicron/pull/2098
- Snapshot Create
- Snapshot Delete
- Volume Delete
- Volume Remove ROP
- Project Creation
- Project Deletion
- VPC Creation
- VPC Deletion
- Instance Migration
Related to https://github.com/oxidecomputer/omicron/issues/2052, https://github.com/oxidecomputer/omicron/issues/1799
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
No files or tests are named. Start by reviewing the unchecked saga actions in the checklist and the related issues 2052 and 1799, using the completed pull requests 2095–2098 as examples. Done means each remaining action and undo action can be invoked twice and produces the same result as one invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100