What Do Virtualization and SEAPATH Really Change for RTE ?
summary
RTE deploys real-time PACS R#SPACE on SEAPATH using Debian + KVM to run protection, automation and HMI functions as virtual machines, moving from dedicated IEDs to a three-server cluster so VMs migrate on failure with failover ≈1 minute. Three substations are already running the stack; breaker‑failure automation and IEC 61850 gateways run as VMs; protection VMs from two vendors are under test. Main tradeoffs are reduced hardware, added integration work and shorter server lifecycles requiring new maintenance processes.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:23PAX strategy evolution
- 3:35Virtualization approach choice
- 6:23Cass open source solution
- 8:11RSpace program overview
- 9:57Cluster redundancy benefits
- 13:09Protection function testing
- 14:14Integration and vendor challenges
- 16:22Maintainability concerns
- 17:24Cass flexibility and future
- 18:52Q&A session
related talks
12mProtecting a 63 KV Substation on SEAPATH With Multi Vendor Solution...
22mEnsuring Requirements on the SEAPATH Project: Testing Process and Continuous Integration
10mEnabling VIED Compatibility on SEAPATH: The SSC600SW Integration Jou...
32mTesting the Resilience of a SEAPATH Cluster: In Search of Single Points of Failure
32mBuilding a Multi-Vendor, Software-Defined Substation: Lessons From Red Hat’s VPAC...
35mHow SRE Makes Electric Vehicles
27mPre-Packaging CRA and NIS2 Compliance: The SEAPATH Approach
15mHow Our SREs Safeguard Nanosecond Performance—at Scale—in an Environment Built to Fail