oxidecomputer / oxidecomputer/omicron
Sled Agent service launching should cope with U.2s that might not be ready yet
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
- RSS / Nexus both tell sled agent to launch services
- If we succeed when starting a service, the sled agent stores "here are the services I should launch on cold boot" in the M.2 configuration dataset
- On reboot, we read this list of services from the M.2 and try to start 'em.
RIGHT NOW if we fail to start those services, we don't try again.
This is a bummer! Especially with the dependencies on U.2s - which might take a sec to load - we should add a retry-with-backoff to service launching, kinda like we already do for the NTP and Switch zones.
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 tracing Sled Agent's cold-boot service-launch path and compare it with the existing retry-with-backoff behavior for the NTP and Switch zones. Confirm where failures currently stop the launch sequence and identify the relevant tests. Done means services dependent on U.2s are retried with backoff after reboot rather than abandoned after the first failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100