plan: a card chassis is a build, and the queue calls ten unbuildable requests ready #1798
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1798
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1117-0610"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forward plan only - no engine, test or workflow changes.
docs/plans/stated-configurations.mdrecords the contract that a card chassis enters the catalogue as a stated build, and what is actually blocking the ten open device requests:PIC 1-8) and a 60-card census with port counts per part name are inresearch/huawei-netengine-8000-m-series-slots.md.engine/media.js:831-860has no OTN/WDM family, so a line port would be cabled as ordinary optical Ethernet. Marked as needing Jay's approval.The measured defect:
node scripts/request-queue.jsprintsopen: 10 ready: 10- readiness is four form fields (scripts/request-queue.js:103-107) - and--skeleton 799emits a 19-slot chassis as a singleeth01G port.docs/DEVICE_SCHEMA.md:30never mentions a build, and the card complement lives inlabelfor 42 entries but inmodelfor 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.
c8b9da7ca66d2b75ee4d