oxidecomputer / oxidecomputer/omicron
Instance start API in the face of long creation times.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
With potentially long (5-10 minutes) of creation/initialization time now possible with local storage volumes, we want to discuss the possibility of making and instance start request be asynchronous.
The current behavior of having instance start (or instance create with start option) wait for the instance to report started will almost always timeout before the local storage volume has finished initialization, resulting in a sharp edge that might confuse users as to the status of their instance.
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 examining the instance start API and the instance create flow when the start option is used, focusing on how long local storage volume initialization affects the current wait and timeout behavior. Define the asynchronous behavior and the observable instance status needed to avoid confusing users; the issue is complete when the proposed API behavior addresses these long creation times without premature timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100