plan: a card chassis is a build, and the queue calls ten unbuildable requests ready #1798

Merged
jaylouisw merged 1 commit from plan/1117-0610 into main 2026-11-17 06:22:55 +00:00
Owner

Forward plan only - no engine, test or workflow changes.

docs/plans/stated-configurations.md records the contract that a card chassis enters the catalogue as a stated build, and what is actually blocking the ten open device requests:

  • #797 / #799 (M8, M14) are writable today - the slot table (PIC 1-8) and a 60-card census with port counts per part name are in research/huawei-netengine-8000-m-series-slots.md.
  • #807 / #808 / #810 (OptiXtrans E9605/E9612/E9624) are blocked on a port type, not a source: every port is an OTU line port, and engine/media.js:831-860 has no OTN/WDM family, so a line port would be cabled as ordinary optical Ethernet. Marked as needing Jay's approval.
  • #803 / #804 / #742 / #743 are blocked on material the vendor does not publish.

The measured defect: node scripts/request-queue.js prints open: 10 ready: 10 - readiness is four form fields (scripts/request-queue.js:103-107) - and --skeleton 799 emits a 19-slot chassis as a single eth0 1G port. docs/DEVICE_SCHEMA.md:30 never mentions a build, and the card complement lives in label for 42 entries but in model for 2.

Eight ordered steps, each one PR, sizes S/M: steps 1-3 are schema and queue work, 4-5 land the two NetEngine chassis, 6 is the port-type decision.

Forward plan only - no engine, test or workflow changes. `docs/plans/stated-configurations.md` records the contract that a card chassis enters the catalogue as a *stated build*, and what is actually blocking the ten open device requests: - **#797 / #799 (M8, M14)** are writable today - the slot table (`PIC 1-8`) and a 60-card census with port counts per part name are in `research/huawei-netengine-8000-m-series-slots.md`. - **#807 / #808 / #810 (OptiXtrans E9605/E9612/E9624)** are blocked on a *port type*, not a source: every port is an OTU line port, and `engine/media.js:831-860` has no OTN/WDM family, so a line port would be cabled as ordinary optical Ethernet. Marked as needing Jay's approval. - **#803 / #804 / #742 / #743** are blocked on material the vendor does not publish. The measured defect: `node scripts/request-queue.js` prints `open: 10 ready: 10` - readiness is four form fields (`scripts/request-queue.js:103-107`) - and `--skeleton 799` emits a 19-slot chassis as a single `eth0` 1G port. `docs/DEVICE_SCHEMA.md:30` never mentions a build, and the card complement lives in `label` for 42 entries but in `model` for 2. Eight ordered steps, each one PR, sizes S/M: steps 1-3 are schema and queue work, 4-5 land the two NetEngine chassis, 6 is the port-type decision.
plan: a card chassis is a build, and the queue calls ten unbuildable requests ready
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m7s
CI / Server smoke test (pull_request) Failing after 11m16s
CI / Test (Node 20) (pull_request) Failing after 11m23s
c8b9da7ca6
jaylouisw force-pushed plan/1117-0610 from c8b9da7ca6
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m7s
CI / Server smoke test (pull_request) Failing after 11m16s
CI / Test (Node 20) (pull_request) Failing after 11m23s
to 6d2b75ee4d
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 14s
2026-11-17 06:20:00 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1798
No description provided.