Repository navigation
hummingbird: run hummbwtester demo inside SCIERA - #79
Merged
Merged
Conversation
juagargi
force-pushed
the
hummingbird-sciera
branch
from
September 18, 2026 13:13
313504e to
706e651
Compare
juagargi
marked this pull request as ready for review
October 21, 2026 10:30
Add explicit SSH inventory, deployment, session lifecycle, and metric tunnels. Support dedicated-link TBF shaping with safe cleanup. Fetch marketplace JWTs through the configured URL without exposing secrets.
We can't use veth with an IPv6 link local interface. Instead use a selective qdisc and TBF.
Use one experiment definition json file. Three actions: setup, run, and teardown.
Under error conditions, ReadBatch returns whatever recvmmsg returned, which happens to be -1.
When in ssh mode, allow the marketplace to be declared on any ssh host. If so, the token is extracted from there, using an ssh tunnel.
The teardown step does NOT remove it. Also, in ssh mode the "host" parameter is required.
Simplify/unify ssh setup. Rewrite ssh setup section in README.
If the marketplace binary is different, copy a new one. Copy a systemd unit file as well. Restart the service if marketplace is not reachable, or newly copied. If service is to be restarted, repopulate DB with the save values that the docker mode uses. Teardown stops the service, does not remove DB or binary.
Grafana connects to Prometheus using an ssh relay too.
Allow just plain text when setting with tc.
Reduce the verbosity of the setup step in ssh mode.
It aggregates now using {AS,BR-name}.
From flake8.
The experiment JSON file now accepts hummingbird.marketplace.interfaces with a AS-based dictionary of interfaces that are declared to be hummingbird assets to be sold. If not present in the JSON file, all interfaces are considered Hummingbird.
Also report if any leftover process is found on both setup and run steps.
Use the same --sequence flag that scion showpaths uses.
Fix cases where the source and destination ASes are part of the same segment. Because the PCB didn't contain 0 as ingress of the src AS, or 0 as the egress of the dst AS, and the flyover was acquired with 0 as ingress of the src, and 0 as egress of the dst, modify the ingress/egress interface used to validate the flyover MAC.
Regardless of the contents of the dataplane hop fields, the first and last flyovers must always contain ingress (and respectively egress) set to zero. The fix is necessary to allow assigning reservations to e.g. a down-segment where src and dst are part of the segment, but non core (segment cut).
When after e.g. docker network prune, it is necessary to recreate the container.
juagargi
force-pushed
the
hummingbird-sciera
branch
from
October 21, 2026 13:12
ad6f607 to
fd29158
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs the hummbwtester Hummingbird vs. best-effort experiment on real SCIERA hosts over SSH,
alongside the existing Docker mode,
and fixes the Hummingbird bugs these new topologies exposed (over RNP, UFES, and UFMS).
The experiment
JSONsetup file configures the whole of the experiment.We provide two examples, one for the local docker setup, another one for SCIERA.
hummbwtester
experiment.py {setup,run,teardown} --config FILE(
deployment.kind:docker|ssh), plus a read-onlysetup --dry-run.setup: deploys the tester binary, a marketplace service (assets limited tohummingbird.marketplace.interfaces), the client JWT, per-flow PRIO/flower/TBF qdiscs, the staticinfo Note entry, Prometheus on a host (fed through SSH relays), and a local Grafana. It never
restarts SCION services; it prints manual steps instead.
run: reports tester exits, stops on Ctrl-C, server exit, or all clients done, cleans up,and kills stray testers.
-sequencepath filter (same syntax asscion showpaths --sequence); retries with arefresh when no path matches.
(as, br). SCIERA config:hummbwtester-sciera.json.Hummingbird fixes/changes
segment) keeps the untraversed interface in its hop field. The flyover now uses 0 on that side.
Unit and braccept cases added.
pkg/snet/path: reservation setup applies the same rule (dataplaneToBaseHops,SetHopAndFlyover).Other
ReadBatchreturns -1.marketplace/tools/get_jwt.py(used by setup); smallend2endcleanup.Testing / braccept
Python unit tests,
go test, andbazel teston the affected packages; router acceptance(braccept) passes.
Setup deployed and verified on SCIERA;
a full Hummingbird test run passes as well.
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com
This change is