vms-67f: TCP/IP Services as first-class layered product — build plan + roadmap - #851
Merged
Merged
Conversation
Reflect the operator ruling (2026-08-28): TCP/IP Services is a first-class layered-product deliverable (own kit, own release line, OpenSSH bundled in), distinct from the base OVMX OS but living in src/vmstcpip/. - design-tcpip-services-ovmx.md: new §0 (operator ruling + base-OS/layered split), §6 Packaging rewritten and grounded in the actual kit mechanism (tools/ovmx_kit_pack.c OVMXKIT1 container, src/product PRODUCT.EXE + product DB, distinct 'OVMX <arch> TCPIP' product identity, ovmx-tcpip.kit artifact), §9 operator calls marked resolved. - building.md: new 'Base OS vs. Layered Products (kits)' section grounding the layered-product build/install flow; DECnet noted as the same pattern.
…deliverable Regenerate the rd-derived roadmap GENERATED block (INV-LEDGER — not hand-edited) so the promoted TCP/IP networking epic (vms-67f, now p1) surfaces with its full rung tree: the 1.0-gate workstream row moves 7/12 -> 12/26 (5 blocked), matching the expanded config/management + kit + OpenSSH-bundle decomposition. Also refine the editorial workstream summary in reconcile.py (GATE_EPICS config, not the generated block) to describe the layered product: its own installable kit on the base OS, config/management, and a bundled SSH. This flows to the canonical export + public site view only; the site publish is DEFERRED to the conductor (INV-0). Ledger drift gate (check_roadmap_block.py), reconcile --check idempotency, and the collapse-guard test all pass.
baron-3dl
added a commit
that referenced
this pull request
Aug 28, 2026
…ce parity, SHOW USERS de-fab (#858) Bumps OVMX_PRODUCT_VERSION and os-release V0.5-7 -> V0.5-8. 14 commits since V0.5-7. Distributed Lock Manager — the cross-node ladder tops out at a real GRANT: - #849 vms-e8f1/vms-17c DLM rung-2 (H4): the first REAL cross-node $ENQ GRANT — node B holds a lock on A's behalf for A's CSID, $ENQ returns SS$_NORMAL over live SCS (no longer INV-6 "grants nothing"). The distributed lock manager now actually locks across nodes. - #845 vms-209 DLM harness H3 — a cross-node $ENQ reaches node B's real executive - #843 vms-4bd0 DLM harness H2 — two real-executive QEMU nodes complete the full VMS$VAXcluster join - #842 vms-534 DLM harness H1 — two real-executive nodes exchange the 0x6007 HELLO over a socket netdev - #840 vms-4b6 DLM harness rung H0 — SCSD.EXE composes with a real executive - #841 docs Alpha cross-node DLM wire oracle — observed SCS transport + documented GRANT semantics (Rule 8) Alpha co-release parity — authenticated login + the shared SHOW battery: - #852 vms-f2c Alpha DCL/SHOW acceptance parity — the same shared 11-command battery x86_64 runs, now on qemu-system-alpha - #847 vms.ko guards BG fork-inherit tracepoints behind CONFIG_TRACEPOINTS (Alpha P0 modpost fix) Authenticity (INV-6 de-fabrication): - #839 vms-6a1 SHOW USERS fails honestly when the executive is absent — no more per-process fabricated user list Boot console fidelity: - #850 vms-dec kill boot-console newline spam (the operator's echoed RETURNs) + a type-during-boot regression gate Networking (layered-product promotion): - #851 vms-67f TCP/IP Services promoted to a first-class layered product — build plan + roadmap (1.0 blocker) Docs / ledger: - #745 Alpha C-RTL archive DECIDED — Option A (operator ruling 2026-08-23) - #709 vms-da0 OpenVMS GCC port × OVMX faithful-surface gap analysis - #838 reconcile the release block for the V0.5-7 tag (INV-LEDGER) QA'd under KVM boot-to-login on the workshop host with the full SHOW acceptance battery VMS-faithful; boot console clean (no newline flood) and SHOW USERS honest. Release notes are generated at tag time by tools/gen_release_notes.py (INV-LEDGER single-ledger); the roadmap narrative block + public site are the conductor's reconcile (INV-0/INV-LEDGER). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Works the operator ruling (2026-08-28) promoting TCP/IP Services for OVMX (rd epic
vms-67f, now p1) to a first-class layered-product deliverable into the build plan and the roadmap.Deliverable 1 — build plan
docs/design-tcpip-services-ovmx.md:vms-843/vms-4bfsshd-over-BGn:work re-framed as a valid OpenVMS source-support oracle, not a standalone feature), config/management as the gap, and the base-OS-vs-layered-product split (IP engine = substrateAF_INET; faithfulness lives in the userspace product surface).tools/ovmx_kit_pack.c(OVMXKIT1container,src/libvms/include/ovmx_kit_format.h),src/product/product.c(PRODUCT.EXE) + the PCSI-equivalent product DB (src/product/ovmx_product_db.h). TCP/IP ships as a distinct productOVMX <arch> TCPIP(parallel to the baseOVMX X86VMS VMS/OVMX VAXVMS VMS), packed asovmx-tcpip.kit, registering a second row inVMS$PRODUCT_DATABASE.DATsoPRODUCT SHOW PRODUCTlists OS + TCPIP separately. DECnet (vms-30e) noted as the same pattern.docs/building.md: new "Base OS vs. Layered Products (kits)" section grounding the layered-product build/install flow in the same tools.Deliverable 2 — roadmap
Regenerated the rd-derived GENERATED block in
docs/release-roadmap-to-1.0.mdviatools/roadmap/reconcile.py(INV-LEDGER — not hand-edited). The TCP/IP networking 1.0-gate workstream row now reflects the promoted/expanded rung tree: 7/12 → 12/26 (5 blocked), andvms-67fcontinues to list under the 0.5 milestone. Norel-*labelling gaps (all gate epics labelled).Also refined the editorial workstream summary in
reconcile.py(GATE_EPICSconfig, not the generated block) to describe the layered product. That text flows to the canonical export + public site view only.Gates (all green locally)
tools/ledger/check_roadmap_block.py— clean (block well-formed; 12 shipped releases matchgit tag)tools/ledger/no_new_hand_copies.py— clean (154 docs scanned)tests/tools/test_roadmap_collapse_guard.py— 4 passedreconcile.py --check(pinned snapshot +--as-of) — clean / idempotentDeferred (per instructions)
--site-dirrun;data/roadmap.json/atom.xmluntouched. The refined workstream summary will surface on the site when the conductor next regenerates + reviews it.🤖 Generated with Claude Code