Repository navigation
test: Record a reproducible baseline for dedicated placement - #1451
Conversation
Add ns80, two VPCs (80 and 81) whose guests take identical fixed addresses on dfw's and sjc's compute workers, with gateway and NAT left on the dedicated edge nodes. deploy:scenarios deploys it and verify:scenarios checks placement, the overlap and cross-site ping. Add task baseline:observe, baseline:twice and baseline:versions. The observations cover cross-node delivery in both VPCs, NAT66 and NAT64 egress from both overlapping guests at once, gateway ingress over IPv6 and IPv4, and a negative isolation control. Each scenario captures at the public side, the guests' veth pairs and the remote underlay. results.json keeps only stable fields, so two runs compare equal; ports, nonces and translated tuples go to volatile.tsv. baseline/pins.yaml pins the host tools, the Kind node, FRR, the remote-host base and the guest image digest, and the run fails on any mismatch. baseline/reference-results.json is the result of two identical passing runs. Recorded limits: inbound packets bypass the host veth through bpf_redirect_peer, the edge nodes forward in XDP out of tcpdump's view, and the lab's gateway checks intermittently lose a TCP flow at the ns60 responder, so those are observations or per-run values. The TAP capture point moved to #1444. Fixes #1432
Acceptance evidenceAll lab runs used the shared Containerlab reservation procedure (
Local checks on this commit: Limits the baseline recordsThese are recorded as observations without an expectation, or as per-run values, and
Why the TAP stand-in was dropped (for #1444)The fixture first included a TAP-backed guest. A pod's sandbox ran
The bridge itself works. In a throwaway privileged container, socat 1.8.1.3 ( |
The TAP stand-in moved to #1444, so baseline-versions.sh no longer has a dfw/tap-guest.yaml to read and logged a sed error on every run.
Summary
Later Galactic Worker tasks need a fixed starting point to measure against: today's remote paths on dedicated edge and compute nodes, captured the same way every time.
This adds a lab fixture with two VPCs whose guests share addresses across two compute workers, plus scripted observations of cross-node delivery, NAT66 and NAT64 egress, and gateway ingress over IPv4 and IPv6, each in both directions. A negative control proves a guest never receives traffic sent to its twin in the other VPC, and the run pins and records tool, kernel and image versions and stores a reference result for later runs to compare against.
The TAP capture point moved to #1444, which records why the TAP stand-in failed in Kind.
Evidence scope
The lab evidence is one managed run of two observation passes at this branch's tree, plus an earlier full lab verification with the fixture deployed. Changes after that verification touched only the baseline scripts, not the fixture.
Gateway ingress counts as delivered when each protocol has answered flows, because the lab's own ingress checks lose a TCP flow now and then. With no captures running, one of three IPv4 ingress checks answered 6 of 8 TCP flows. The captures show the request reaching the backend, then the backend's socat responder closing without a reply. That fault predates this change, is tracked in #1452, and is not fixed here.
Test plan
Fixes #1432