Speaker
Description
Large scientific facilities such as accelerators rely on multiple EPICS IOCs to coordinate experimental devices. However, distributed deployment and heterogeneous runtime environments make software updates, status monitoring, and fault handling difficult to manage consistently. To address the isolated network environment, complex software dependencies, and hardware-specific placement requirements at CLAPA-II, this work develops an automated operations platform for the control system based on Docker and Kubernetes. An offline Kubernetes cluster was deployed across 14 servers. A common EPICS base image and IOC-specific images are used to encapsulate the required runtime environments, while host networking and node affinity support EPICS communication and device connectivity. A web interface provides status monitoring, IOC start/stop control, and log access. For log management, caPutLog is integrated into the IOC images to record process variable (PV) write operations and the associated value changes. IOC runtime output is redirected via YAML deployment manifests and then collected by Filebeat for centralized storage; this supports fault diagnosis and the automatic generation and distribution of daily experiment records. A manual on-site restart typically takes more than five minutes; in node shutdown tests using an RCF motor IOC, PV access was automatically restored in approximately 53 s on average. The platform now supports all CLAPA-II IOCs and has been operating stably on site for six months. This work provides a practical approach to IOC containerization, automatic recovery, and centralized operations.
