oxidecomputer / oxidecomputer/oxide.rs
oxide instance from-image --help could describe what is happening with networking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 75
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
I was using oxide instance from-image to create an instance and was surprised that there were no controls over networking. It'd be nice if we said in the --help output what would actually happen. I got this invocation from some of the quickstart docs and adopted it and if not for that context I would have been surprised that it was requesting an ephemeral IP address and I'm not sure whether or not that should be the default longer term, but understand why it is.
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 oxide instance from-image --help entry point and the quickstart documentation that provides the invocation. Confirm what networking setup occurs, including the ephemeral IP request and its default behavior. Done means the help output clearly explains those networking effects and any relevant controls or defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100