SDK2 live gate: AVEVA history, consumer compatibility and paired-cluster rollout #801

New Issue

2026-11-10T13:11:08-05:00

dohertj2 commented

2026-11-10 13:11:08 -05:00

Required live environment checks from #782 Tasks11–13; no deployment is recorded. Local software evidence includes 62 strict application cross-version cases in separate processes, real SQLServer195/195 and QuestDB233/233 conformance passes per original/candidate version, and actual ScadaBridge None/API-key consumed-subset checks. These do not certify the real AVEVA historian or a mixed-version Akka pair.

Owner: repository owner / approved DEV/QA operators, coordinated with HistorianGateway and ScadaBridge owners. In an approved isolated DEV environment, verify actual AVEVA Gateway raw/modified/processed/event/update capabilities and existing unsupported metadata; preserve historian output/quality/timestamps and application aggregate semantics (no new string-backfill/native-aggregate enablement). Coordinate deployed gateway version with historiangw#78; consumer Client/Contracts0.4 bump historiangw#119 is already complete on master16111a5e. Do not call the local deterministic historian fixture real AVEVA evidence.

Exercise current ScadaBridge consumed operations against candidate endpoints, URI-based namespace rebinding, writes/quality/timestamps/alarms and reconnect. ScadaBridge#121 tracks a preexisting missing application-certificate path that rejects SignAndEncrypt on both original/candidate servers; its None subset is not a secure-channel pass. #797 separately tracks preexisting opaque scripted-alarm equipment-scope denial; preserve baseline results until reviewed remediation.

Prove active/standby ServiceLevel250/240, actual failover/reconnect, current key/grant revocation and expiry, and mixed-version Akka serialization/deployment compatibility before choosing a rolling pair restart. Otherwise use a documented coordinated maintenance restart. Follow the checked-in rollout/rollback runbook, retain exact source/artifact/config/PKI hashes and operator results. #800 covers Windows package/install smoke; #799 covers the active native-memory soak finding; #796/#798 are baseline test debt. These are distinct gates, not permission to bypass a failure.

Wonder-box remote-execution hold stays binding: no WinRM/psbridge/replacement channel on vd03/vq03/vq04 without user clearance. UNC/SMB copies and permitted SQL reads do not authorize service commands. No live environment is called passed and #782 must remain open until its required gates are satisfied or accurately separated by the owner.

Required live environment checks from #782 Tasks11–13; no deployment is recorded. Local software evidence includes 62 strict application cross-version cases in separate processes, real SQLServer195/195 and QuestDB233/233 conformance passes per original/candidate version, and actual ScadaBridge None/API-key consumed-subset checks. These do not certify the real AVEVA historian or a mixed-version Akka pair. Owner: repository owner / approved DEV/QA operators, coordinated with HistorianGateway and ScadaBridge owners. In an approved isolated DEV environment, verify actual AVEVA Gateway raw/modified/processed/event/update capabilities and existing unsupported metadata; preserve historian output/quality/timestamps and application aggregate semantics (no new string-backfill/native-aggregate enablement). Coordinate deployed gateway version with historiangw#78; consumer Client/Contracts0.4 bump historiangw#119 is already complete on master16111a5e. Do not call the local deterministic historian fixture real AVEVA evidence. Exercise current ScadaBridge consumed operations against candidate endpoints, URI-based namespace rebinding, writes/quality/timestamps/alarms and reconnect. ScadaBridge#121 tracks a preexisting missing application-certificate path that rejects SignAndEncrypt on both original/candidate servers; its None subset is not a secure-channel pass. #797 separately tracks preexisting opaque scripted-alarm equipment-scope denial; preserve baseline results until reviewed remediation. Prove active/standby ServiceLevel250/240, actual failover/reconnect, current key/grant revocation and expiry, and mixed-version Akka serialization/deployment compatibility before choosing a rolling pair restart. Otherwise use a documented coordinated maintenance restart. Follow the checked-in rollout/rollback runbook, retain exact source/artifact/config/PKI hashes and operator results. #800 covers Windows package/install smoke; #799 covers the active native-memory soak finding; #796/#798 are baseline test debt. These are distinct gates, not permission to bypass a failure. Wonder-box remote-execution hold stays binding: no WinRM/psbridge/replacement channel on vd03/vq03/vq04 without user clearance. UNC/SMB copies and permitted SQL reads do not authorize service commands. No live environment is called passed and #782 must remain open until its required gates are satisfied or accurately separated by the owner.