Skip to content

docs(networking): record OVN ownership and address consumption #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jmgilman wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs(networking): record OVN ownership and address consumption #31

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74bec86
docs(networking): record OVN sandbox address consumption
jmgilman Sep 12, 2026
0856555
docs(networking): require exclusive OVN uplink parent ownership
jmgilman Sep 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 22 additions & 7 deletions docs/docs/reference/networking/address-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,10 +102,25 @@ external router and network-forward addresses on VLAN 40, not a separate
routed subnet or an extension of the `.200`–`.250` DHCP pool. Do not assign
them to other endpoints.

Each tested sandbox consumes two addresses: one NAT router address and one
network-forward address. The 16-address pool therefore has address capacity
for eight such sandboxes. A temporary empty `keeper` network added one shared
address (`10.10.40.64`), reducing that ceiling to seven sandboxes and one spare.
The failed keeper mitigation was removed; it no longer reserves an address.
These figures describe address capacity, not lifecycle qualification.

`fast40-uplink` is the exclusive consumer of `fast40` on every member. Do not
attach raw macvlan or physical NIC devices to that parent: macvlan and OVS
compete for its RX handler. Sandbox projects require
`restricted.devices.nic=managed`; fleet checks default-project instances,
profiles, and member-specific network parents before OVN convergence.
OVN control-plane operations require central up. After central recovery,
the reaper can delete an `Errored` network left by a failed create.

Temporary OVN central runs on `sandbox01` at `10.10.40.10`, with northbound
TCP port `6641` and southbound TCP port `6642`; it remains running until
Phase 5 replaces it. Chassis encapsulation uses the members' VLAN 30
addresses. See the [spike report](https://github.com/GilmanLab/agentcompute/blob/spike/ovn-mechanism/spikes/ovn/README.md)
addresses. See the [spike report](https://github.com/GilmanLab/agentcompute/blob/master/spikes/ovn/README.md)
for measurements and the northbound/chassis sequencing constraint.

## Gateway interface mapping
Expand Down Expand Up @@ -152,12 +167,12 @@ workloads stay off the management plane. These links are not required for
IncusOS management boot. The host-side counterpart, converged by the
`GilmanLab/fleet` `cluster/` project, is the `vlan_tags` allow-list plus an
IncusOS-declared VLAN interface per carried VLAN (`fast30`, `fast40`).
Instances must attach to the IncusOS-owned interface (for example macvlan
with `parent=fast40`), never with an Incus-created `vlan=` sub-interface on
`fast`: the visible `fast` device is an IncusOS-internal VLAN-filtering
bridge, and only IncusOS-declared VLANs receive bridge self-port membership,
so other tagged sub-interfaces pass no traffic. Additional instance VLANs
join these links when their first consumer arrives.
OVN instances attach to managed OVN networks, whose physical uplink alone
claims `fast40`. Do not attach instance NICs directly to `fast40` or create
Incus `vlan=` sub-interfaces on `fast`: the visible `fast` device is an
IncusOS-internal VLAN-filtering bridge, and only IncusOS-declared VLANs
receive bridge self-port membership, so other tagged sub-interfaces pass no
traffic. Additional instance VLANs join these links when their first consumer arrives.

## DHCP and DNS ownership

Expand Down