oxidecomputer / oxidecomputer/omicron

softnpu could be packaged as a zone, like other omicron components

Open
#4,131 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

development
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

Deploying omicron on systems without real Oxide switch(es) requires softnpu, which simulates the switch. Today, softnpu is installed separate of other omicron services, by the "virtual hardware" scripts.

As long as engineers will want to deploy omicron on systems without a real oxide switch (which will probably be a very long time, at least), we will need softnpu; as such, it should be treated as a first class component the way other zones are.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the virtual hardware scripts and the packaging for other zones, then compare how softnpu is installed separately today. Done means softnpu is treated as a first-class zone and can be deployed with omicron on systems without real Oxide switches.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.