oxidecomputer / oxidecomputer/falcon
info command could provide more information about the VMs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 5
- Avg merge
- 11d 13h
- Merged PRs (30d)
- 2
Description
The info subcommand of a falcon binary (e.g. a4x2 or interop) could provide more VM state information, which would be helpful for debugging.
For example, the first thing that would be helpful is to have a "running" or "created" field that lets the user know whether the VM has actually been instantiated and whether there's anything currently running.
It would also be nice if this could be used as a discovery mechanism to figure out if there are other propolis VMs running on the system, even if they were launched from a different falcon directory (or from a different falcon binary).
Another item that could be included would be the filepath to falcon/propolis log files, so the user doesn't have to know ahead of time about the .falcon directory and what the various files are.
Contributor guide
No contributing guide indexed for this repository
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 with the falcon binary's info subcommand, including the a4x2 and interop entry points mentioned in the issue. Define how the command reports VM state, discovers VMs launched elsewhere, and identifies falcon/propolis log paths; done means these details are available through info for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100