docs(index): HistorianGateway fa9cf31 deployed to QA vq03/vq04 (historiangw#78 closed)

QA had no historian account and now reuses DEV's personal NAM account
(follow-up historiangw#134). Env migration: RuntimeDb removed,
LiveWritesEnabled on, gRPC 0.0.0.0:5221 kept.

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 20:07:32 -05:00
parent f83c75678c
commit 6c4595e87f
2 changed files with 10 additions and 2 deletions
@@ -85,3 +85,11 @@ for persistence evidence.
- **2026-11-11 deployed `ea9f21c` to wonder-app-vd03 (DEV)** (was `d8d890c`, the SQL-era build). Owner-approved WinRM deploy: SMB-staged self-contained win-x64, preflight test boot on 15220/15221 against store copies, swap 6.5 s downtime, verify 0 FAIL (gRPC probe/browse/read-raw as OtOpcUa, bogus key refused). Config unchanged (already `Transport=RemoteGrpc` → wonder-sql-vd03:32565); inert `RuntimeDb` line removed from appsettings.Production.json. Backups `Server.bak.20261111T164035`, `_databak-pre-ea9f21c-…`, `_regbak-…`. Carried-over risks: `AllowUntrustedServerCertificate=true` (#91), personal historian account.
- **2026-11-12 vd03 gRPC opened off-box:** Grpc endpoint `127.0.0.1:5221` → `0.0.0.0:5221` (h2c) + firewall rule `HistorianGateway gRPC 5221` (Domain), via SMB config push + one WinRM script; off-box `HistorianStatus/Probe` without a key → `Unauthenticated` (auth enforced). Backup `appsettings.Production.json.bak-20261112T070347`.
- **2026-11-12 deployed `fa9cf31` to QA vq04 + vq03 (historiangw#78 closed).** `fa9cf31` = `ea9f21c` + #133 (CLI only). Rolled one node at a time: vq04 20:02, then vq03 20:04, with downtime of 8.2 s and 6.5 s. Each node got an isolated test boot first (15220/15221, store copies, migrated env).
- **Finding: QA had no historian account.** The NSSM env had no `Historian__UserName`/`__Password`. `d8d890c`'s health check never signed in, so it said Healthy while browse and read-raw failed with `ArgumentException`. The new health check signs in and returned 503 (`HistorianAuthException`).
- **Owner decision:** reuse DEV's personal account `NAM\dohertj2` on QA. The password was carried vd03 → target only over WinRM stdin, never printed, and verified by SHA-256 prefix across vd03, vq03 and vq04. One password change or lockout now breaks DEV and QA together. Follow-up historiangw#134 (dedicated service account, p2).
- **Env migration (31 → 32 vars):** removed `RuntimeDb__Enabled` and `RuntimeDb__ConnectionString`; added `Historian__LiveWritesEnabled=true` (`RuntimeDb__Enabled=true` had enabled SQL live writes, and OtOpcUa's recorder uses `WriteLiveValues`); added the credentials; kept `Kestrel__Endpoints__Grpc__Url=http://0.0.0.0:5221`. `AllowUntrustedServerCertificate` stays false on QA because its historian certificate verifies (vd03 still needs true).
- **Verify, 0 FAIL on both nodes:** ready 200; dashboard 302 → /login as before; probe, browse and read-raw `SysTimeSec` with OtOpcUa's key on both 127.0.0.1 and the node IP; bogus key refused, including from the Mac; Overview 12/12 Up with HistorianGateway at 4/4.
- **OtOpcUa QA (`fea7de0a`):** points at `http://10.220.158.2:5221` with `UseTls=false`, so no change was needed.
- **Backups:** in protected folders (SYSTEM + Administrators) at `E:\psrem-stage\hg-fa9cf31\backup-<COMPUTER>-<ts>\`, plus `app.bak.20261112T200251` (vq04) and `app.bak.20261112T200425` (vq03).
- **Record:** historiangw `docs/deploy/2026-11-12-qa-vq03-vq04-fa9cf31.md` (`b95bae3`).
+2 -2
View File
File diff suppressed because one or more lines are too long