Skip to content

feat(ciena): add tl1MaxConnections and a Ciena vendor README - #78

Merged
stephenstack merged 2 commits into
mainfrom
dev
Sep 12, 2026
Merged

stephenstack merged 2 commits into
mainfrom
dev

Conversation

@stephenstack

Copy link
Copy Markdown
Collaborator

No description provided.

rconfig and others added 2 commits September 12, 2026 18:33
Every RNE behind a Ciena GNE opens its own TL1 session to that gateway, so
a nightly run over a gateway fronting a hundred RNEs attempts a hundred
logins as fast as the queue can issue them. A node that refuses connections
past its own cap fails whichever collections lose that race.

rConfig now caps concurrent sessions per gateway, configured with
connect.tl1MaxConnections on the GNE's template and defaulting to 20. Both
Ciena templates carry it, and the key is documented in the legend with its
clamping behaviour: values outside 1 to 500 are clamped and anything
non-numeric falls back to the default, so a typo cannot stop a gateway
collecting.

The validator's allowlist gains the key too, otherwise these templates
would fail their own CI. Key counts in README, CONTRIBUTING, EDITIONS and
the legend move from 46 to 47, and the Pro-only count from 13 to 14. The
CHANGELOG's count is left alone, being a record of a past release.

Ciena had no vendor README while most other vendors do. Added one covering
what makes TL1 different from a CLI, the GNE/RNE and dual-homing model, and
how to choose a connection limit.

Refs RCO-1449

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
feat(ciena): add tl1MaxConnections and a Ciena vendor README
@stephenstack
stephenstack merged commit 13d5491 into main Sep 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants