oxidecomputer / oxidecomputer/opte

Verify that Oxide-VPC ports can be configured/reconfigured to run without external IPs bound

Open
#897 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
77
Forks
11
Avg merge
9d 20h
Merged PRs (30d)
8

Description

At some point we will want to be able to meet the constraint that a single/dual-stack port without, e.g., an Internet Gateway will consume no IP pool resources whatsoever. We should ensure that a port can begin in, and be safely reconfigured into, such a state and that xde will consider it valid.

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

The issue names Oxide-VPC ports and xde but no files or tests. Start by tracing port configuration and xde validation, then exercise a single- or dual-stack port with no external IP at creation and after reconfiguration. Done means both states are accepted and consume no IP pool resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
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.