Files
rust-discovery/docs/server-time-gateway-deploy.md
T
2026-11-15 13:16:46 +01:00

70 lines
4.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Fixed time gateway deployment preparation
Source-only, no deployment executed by this author. The operator uses only the
already qualified ARM64 image422c2c28 from stage
`d11a6fb7-cfdd-41b2-87c5-b48a2cfd2e27`, source2af. It performs no rebuild and
does not package, replace or delete existing WebUI files. The original seven
web files, their bytes and inodes, index95d6f905, compose d2044b0e, PKI/key
metadata, closed policycf15, PostgreSQL container/volume and Chrony generation
remain bound. Root independently captures immutable31/31/27 closed core history,
Windows0 and native-role evidence before/after; this controller does not claim
those external witnesses from container checks alone.
`deploy/server.time-broker.compose.yaml` is the199-byte fixed optional overlay,
SHA256 `dbd08faea8f58c032562d822f4191c719f9a6828b00d6c368fc2596155a9a314`.
Only gateway receives the read-only `/run/rmm-time-source` bind, with
`create_host_path: false`. API receives no time mount. No port, environment,
authentication, TLS, policy or capability changes are added.
`cloud_server_upgrade.deploy` automatically includes that exact Root0:0/0644
single-link overlay whenever installed. Wrong bytes, owner, mode, hardlinks or
symlink/unsafe ancestry deny before UI/tag/migration effects, with repeat checks
before each backend effect. Absence retains the original compose invocation.
A stage reserved by the fixed operator cannot later be replayed through generic
deploy. The new reviewed public upgrade tool is installed with a retained old
copy, so future upgrades keep the mount.
`deploy/server_time_gateway_deploy.py` has only `host-preflight`, one
`host-deploy`, and original `host-read`. Root stages `gateway_deploy.py` plus the
two fixed public files under the controller's content hash. It checks source209
files and original build result, actual old6f API/GW containers and runtime tag,
UI CAS, PostgreSQL identity, and actual broker start8fc6/e145 proof. Live broker
checks retain the original process/birth/image/socket independently of the old
6f application IDs; no old InstalledProof freshness check is bypassed or reset.
The separate C31 public key is pinned. A missing actual signature-PASS result
and separate read hash hard-denies before deployment.
The final source pins actual signature controllera8afe8a2 and result
`38ed1a3079f20438fe07a57f1bfa5a37348bdec9fc7780d7822ca3d6967e5ea1`,
with separate read receipt
`4b442a9022f1ee56f8e851e25ad323d630b220cf47aa8169b83b9c4412c50b8d`.
Both host and default-container UID/GID10001 signatures were verified in that
separate fixture. They do not attest mTLS, an enrolled Windows identity, sync
readiness or clock authority. The deploy operator sends no signature request.
New case `fb87aa88-2b67-4cff-9c90-4cd713380889` writes intent before installing
the create-only overlay, persistent upgrade tool or moving the runtime tag.
Each tag, migration and API/GW recreate has its own intent and retained exit/log.
Migration uses the existing compiled image once; actual versions1–14 must become
1–15. Only API/GW are forcibly recreated, without dependencies or rebuilds. All
old role mounts remain equal, plus exactly the gateway-only read-only broker
mount. Broker, Chrony and PostgreSQL are not restarted.
Failure/lost reply permits only the same case's `host-read`, with no retry,
automatic rollback, reset, enrollment, key generation, signature request or
API/DB approval. The existing WebUI approval boundary for every RMM job remains
unchanged. Readback performs no Docker/service/SQL/time action.
## Tatsächlicher lesender Vorabcheck
Controller `e14aeabfd7d3a8ab298985706dc26014e0ad540a1c3ef40cf57e1a65b77b7f3b`
mit unabhängigem QuellenreviewPASS. Auf dem permanenten Server wurde ausschließlich
`host-preflight` ausgeführt: Exit0, Rootreceipt
`9c08cce4f21da8a895eabeea80c4ff1e6068346fb5b46b4fe95b0ee2d30db1e9`.
Geschützte Sources/Buildresultate, bestehende6f-Runtime, alleUI-Dateien, PKI-,
Broker-/Signatur-/Pinbelege, PostgreSQL und Migrationsstand1..14 akzeptiert.
Noch kein Deploymentfall angelegt, Overlay installiert, Image getaggt, Migration
oder Recreate ausgeführt. Die Runtime bleibt6f;422 bleibt gebauter Kandidat.
Vor tatsächlichem `host-deploy` folgen die getrennten vollständigen SQL-
Historienzeugen, nachher deren Originalvergleich sowie Endpoint-/Windowsnachweise.