1 / 14

Jefferson Lab Report

This report outlines the current performance of the EPICS system, highlighting reliable operation while addressing occasional CA Security configuration issues. It discusses the segmentation of the system into 13 independent segments to enhance availability and resource management, and emphasizes the importance of upgrades for growth, increasing IOC speed, and network bandwidth. The use of a nameserver to reduce load and improve connections, as well as the standardization of common elements for productivity, is explored. Effective change management, including version control and rollout processes, is crucial for maintaining system integrity.

johnna
Télécharger la présentation

Jefferson Lab Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jefferson Lab Report Karen S. White

  2. Status • EPICS is performing well. • We continue to occasionally have a problem when switching between CA Security configurations

  3. System Growth

  4. Managing a Large EPICS System • Segmentation • Growth • Managing access and traffic • Diagnostics • Standardization • Change Management

  5. Segmentation • System divided into 13 independent segments to facilitate: • Availability • Resource Management • Maintenance • Each segment has its own server, network, IOCs, etc • Except – a single Oracle database server is shared between all segments

  6. Growth • Upgrades to accommodate growth • Faster IOCs • More IOCs • More Memory on IOCs • More Unix Consoles • More Memory on Unix Consoles • More Network Bandwidth

  7. Nameserver • Nameserver • Reduces IOC load and network traffic due to broadcast for name resolution • Provides PV location info to tools that do not need to connect • Improves client connection time (2x) • Used by all operations client for ~1.5 years – very reliable – no failures • Handles over 6 million requests per day

  8. Gateway • From APS/BESSY • Used to group multiple requests for the same signal • Concentrates communication from many clients to a single client • Reduces IOC load and network traffic due to broadcasts for name resolution • Reduces the number of connections to IOCs • Facilitates easy management of access from different CS segments

  9. Standardization • Standardization of common elements can improve developer productivity and software maintainability. Examples: • PIOC • General purpose tool built on PCAS • Developer does not need to know details • Ensures consistent usage • Standardized Serial, GPIB & PLC drivers

  10. Diagnostics • Alarms – warns of oncoming IOC problems (be careful what you put on IOCs) • Monitoring of Unix and network resources • Diagnostic program to check for hardware communication errors • Status pages with IOC information • Control System startup and checkout procedures

  11. Controlled Change • With a large number of developers and applications, changes must be well planned and documented • Versioning • Roll back procedures • Testplans with auto e-logs

  12. General Comments • Keeping a large EPICS system up and running requires careful planning, diagnostics, monitoring • The development and maintenance processes are made more efficient by using standards, versioning and release control

More Related