docs(index): OtOpcUa fea7de0a deployed on DEV vd03 and the QA pair vq03/vq04 (SDK 2.0.1, runner OutOfProcess on QA)

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 17:05:06 -05:00
parent e6beb9b4bf
commit cde1297c4a
2 changed files with 38 additions and 2 deletions
@@ -520,3 +520,39 @@ its Galaxy acks fail against mxaccessgw `2b13564e` did not apply to this box's d
- **What changes on a deployed box:** only a box that already lists `EnabledSecurityProfiles` in its appsettings or env. Before, it still advertised `None` and so everything kept working; after, `None` really goes. No checked-in config, deploy record or the vd03 upgrade record (`docs/deploy/vd03-upgrade-b8b4c18f-to-master.md`, deployed-appsettings diff) sets it, and no QA record does either, so none of DEV vd03 or QA vq03/vq04 is known to rely on the append behaviour. The service environment on the boxes was not inspected (no ad-hoc WinRM); check `OpcUa__EnabledSecurityProfiles__*` on a box before its redeploy. - **What changes on a deployed box:** only a box that already lists `EnabledSecurityProfiles` in its appsettings or env. Before, it still advertised `None` and so everything kept working; after, `None` really goes. No checked-in config, deploy record or the vd03 upgrade record (`docs/deploy/vd03-upgrade-b8b4c18f-to-master.md`, deployed-appsettings diff) sets it, and no QA record does either, so none of DEV vd03 or QA vq03/vq04 is known to rely on the append behaviour. The service environment on the boxes was not inspected (no ad-hoc WinRM); check `OpcUa__EnabledSecurityProfiles__*` on a box before its redeploy.
- **ScadaBridge consumer impact: none today, a hard constraint if `None` is ever dropped.** ScadaBridge's OPC UA adapter connects with `None` + API key (18 cases pass against SDK 1.5 and SDK 2 servers) and has no client certificate, so its encrypted attempts fail before activation (ScadaBridge#121). On a node whose profile list omits `None`, that link would be refused with `BadSecurityPolicyRejected`. Do not drop `None` on any node ScadaBridge connects to until #121 is done. vd03 ScadaBridge has no OPC UA link to OtOpcUa, so vd03 could drop `None` safely; QA is not checked. - **ScadaBridge consumer impact: none today, a hard constraint if `None` is ever dropped.** ScadaBridge's OPC UA adapter connects with `None` + API key (18 cases pass against SDK 1.5 and SDK 2 servers) and has no client certificate, so its encrypted attempts fail before activation (ScadaBridge#121). On a node whose profile list omits `None`, that link would be refused with `BadSecurityPolicyRejected`. Do not drop `None` on any node ScadaBridge connects to until #121 is done. vd03 ScadaBridge has no OPC UA link to OtOpcUa, so vd03 could drop `None` safely; QA is not checked.
- **Evidence:** options binding (indexed, JSON array and env forms, default, empty, unknown name) 8 tests; booted-server wire test (secure-only config advertises no `None`, a `None` session is refused with `BadSecurityPolicyRejected`, a SignAndEncrypt session works; the default-config case is the control and does connect on `None`). Mutation (re-adding the pre-filled default) fails the wire test and 5 of the 8 binding tests. - **Evidence:** options binding (indexed, JSON array and env forms, default, empty, unknown name) 8 tests; booted-server wire test (secure-only config advertises no `None`, a `None` session is refused with `BadSecurityPolicyRejected`, a SignAndEncrypt session works; the default-config case is the control and does connect on `None`). Mutation (re-adding the pre-filled default) fails the wire test and 5 of the 8 binding tests.
### 2026-11-12 — DEV vd03 and the QA pair vq03/vq04 upgraded to master `fea7de0a` (#801, #793, #794, #780)
WinRM was used only for the on-box steps of this owner-requested deploy. The build was a self-contained win-x64 publish
from an isolated worktree: 1396 files, zip SHA-256 `170E7392…8F8024`, LocalDb 0.3.7, HG Client 1.0.0, mxgw Client 0.4.0.
Record: OtOpcUa `docs/deploy/qa-upgrade-b8b4c18f-to-fea7de0a.md` (`c80d187c`). **Every "not deployed" master entry
above (#879–#887, #880, #884/#885, #876) is now deployed on vd03 and on QA.**
- **DEV vd03 `5fb4b4db` → `fea7de0a`.** About 10 s downtime; no migration or config change.
- ServiceLevel **255 → 250** (#884/#885).
- Browse and values the same as before: 23/24 Good, `Program/BlockCount` BadNoData as before.
- ScadaBridge vd03 `/health/ready` 200 (it has no OPC UA link to OtOpcUa).
- **QA `b8b4c18f` → `fea7de0a`, stop-both/start-both** (owner decision; no mixed-SDK rolling restart). Pair outage about 2 min, including the isolation drill.
- #793: preflight all 15 checks ok. **The QA ConfigDb is empty** (0 deployments, drivers, tags, VTs, scripts, API keys).
- The `EnableSnapshotIsolation` migration was applied.
- Pepper and LocalDb sync `ApiKey` were already in both nodes' service env, and identical.
- Isolated preflight boot on vq04 against a clone DB: healthy. A short-pepper negative control was refused.
- #794 worker isolation installed on both nodes: idempotent, rollback drill done. Follow-up #890: the deny does not
cover the sibling `pki\`/`data\`, which are Users-readable.
- #780 P3: `Scripting:Runner=OutOfProcess`, seams Calculation + VirtualTag (ScriptedAlarm not yet). No script exists
on QA, so no worker has run and the runaway drill was skipped.
- **QA verified:**
- Real pair **250/240**.
- Failover: stopping the Primary hands 250 to the Secondary. The old Primary rejoins 100 → 240, never 255, with no failback.
- LocalDb sync connected on both nodes, and refused with no or a bogus bearer (grpc-status 7).
- Overview 5/5 checks healthy.
- AdminUI login posture unchanged.
- **Left as they are on QA:** HistorianGateway `d8d890c` (master's RPC set is served; the probe is reachable over h2c;
historiangw#78 stays separate) and mxgw `4f931e4` (#877 is capability-negotiated; QA has no Galaxy driver).
- **Operator caution, found in preflight:** under SDK 2.0.1, an `OpcUa:PublicHostname` that is not in the application
certificate's SAN stops the OPC UA endpoint (`certificate … is invalid`). `/health/ready` goes 503, but
**`/health/active` stays 200**.
- **ScadaBridge consumer impact: none on QA today.** ScadaBridge QA's only data connection is `MxGateway`, and QA
OtOpcUa serves no application tags. When ScadaBridge does bind QA OtOpcUa:
- the ServiceLevel order is correct again (250 Primary);
- the #887 Severity order flip applies to Galaxy alarms;
- script-backed values return `BadResourceUnavailable` while the runner is unavailable (ScadaBridge#112 handles it).
+2 -2
View File
File diff suppressed because one or more lines are too long