Release NetOpsBench 0.2 scalable benchmark runtime - #6
Merged
Conversation
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
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.
Summary
This PR delivers the NetOpsBench 0.2 benchmark/runtime refactor and validated large-topology support:
This is an intentional 0.2 alpha API/runtime boundary cleanup. NetOpsBench-RL remains outside this repository and consumes the public SDK.
Validation
Real infrastructure validation completed for xlarge, fat-tree K8/K12, and the corrected large profile. The final large gate verified 64 clients, 256 background flows, complete 4,032-path and 16,128 pair-port Pingmesh coverage, clean healthy observations, leaf/spine device-down behavior, recovery, and residue-free teardown.
The completed xlarge DeepSeek campaign produced 70/70 case-valid, cleanup-successful, coverage-complete cases. Agent accuracy remains a model baseline result rather than a release gate.
Known follow-up
A deliberately broader, non-CI mypy scan reports nine annotation-only issues in topology builders. They do not affect runtime behavior or the configured release gate and can be handled in a separate type-only cleanup.