Skip to content

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

Closed
stephenstack wants to merge 1 commit into
mainfrom
DEV-RCO-1449
Closed

stephenstack wants to merge 1 commit into
mainfrom
DEV-RCO-1449

Conversation

@stephenstack

Copy link
Copy Markdown
Collaborator

Supports the per-gateway connection limit landing in rConfig (RCO-1449, rConfigHub/rconfig8#645).

Why

Every RNE behind a Ciena GNE opens its own TL1 session to that gateway. A nightly run over a gateway fronting a hundred RNEs attempts a hundred logins as fast as the queue can issue them, and 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, default 20.

Changes

Both Ciena templates gain the key.

docs/TEMPLATES.md gains the legend row, including the 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.

scripts/validate_templates.py gains the key in its allowlist. Without this the two templates in this PR would fail the repo's own validation, which is a CI gate. Validator run: 78 templates checked, 0 errors, 2 pre-existing warnings.

Key counts move 46 → 47 in README.md, docs/CONTRIBUTING.md, docs/EDITIONS.md and the legend, and Pro-only 13 → 14 in EDITIONS.md along with its per-key list. The CHANGELOG.md count is deliberately left alone, being a record of a past release.

ciena/README.md is new. Ciena had no vendor README while most other vendors do, so this fills a real gap rather than just documenting the new key: what makes TL1 different from a CLI (no enable mode, no pager, in-band ACT-USER login, quoted passwords), the GNE/RNE and dual-homing model, and how to choose a connection limit.

Note

The root README states it "carries no key documentation" and defers to the legend, so no key documentation was added there. Only its key count changed.

🤖 Generated with Claude Code

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>
@stephenstack
stephenstack deleted the DEV-RCO-1449 branch September 12, 2026 17:51
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