oxidecomputer / oxidecomputer/propolis
cannot ssh to helios VM in omicron deployment
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
On real omicron deployments (such as the dogfood cluster on rack2), currently helios VMs are not fully functional from a networking perspective (due to oxidecomputer/stlouis#326).
This is obviously not a propolis issue per se, but in the fullness of time I imagine we will have a more crisp story for supported guest OSes. We will need helios VMs to run our own infrastructure on Oxide, so for now, I am filing an issue to track this here as well.
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 real omicron deployment context described for the dogfood cluster on rack2, then read oxidecomputer/stlouis#326 to understand the stated networking dependency. The issue does not identify files, tests, or a concrete change; done would require a defined supported-guest and networking outcome for helios VMs.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100