oxidecomputer / oxidecomputer/omicron
log shell commands related to zone config and management
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Problems related to zone management can be really hard to debug when you don't know exactly what happened. e.g., a tool like ipadm might report some unexpected error, but it's hard to know why if you don't know what the previous state was. It'd be really handy if sled agent logged all of the shell commands it runs related to zone configuration and management (zoneadm, but also zfs, zonecfg, svcs/svcfg, networking, etc.) It'd be great to include the exit code or termination signal, stdout, and stderr. A complete log of these commands should make it easier to try to reproduce failures during zone management (e.g., #1880). I assume this wouldn't be prohibitive in terms of performance or disk space because I don't think we'd be doing these at high frequency in production.
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 zone configuration and management command execution, including zoneadm, zfs, zonecfg, svcs/svcfg, and networking commands. Read issue #1880 for the failure context. Done means these commands have complete logs containing the command, exit code or termination signal, stdout, and stderr.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100