1 / 8

CA Gateway Update

The CA Gateway 2.0, built on EPICS base 3.14.2, offers significant enhancements but faces challenges. It functions as a CA proxy, connecting and managing multiple networks while caching data and maintaining connections. Despite recent bug fixes and performance upgrades, issues such as scalability bottlenecks and high resource consumption remain. Upcoming steps include addressing hang problems and potentially releasing a beta version. Future ideas for improvement focus on new configuration formats and enhanced documentation to optimize performance and usability.

tacey
Download Presentation

CA Gateway Update

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. CA Gateway Update Ralph Lange, BESSYKen Evans Jr., APSJeff Hill, LANL

  2. Overview • As well CA server as CA client • Usually runs on workstation with multiple network interfaces • Connects and separates networks in terms of CA connections • May use channel aliases (e.g. prefixes) • Caches data • Keeps connections alive • Watchdog mode restarts on core dump

  3. CA Proxy Gateway Allows CA between networks – configurablethrough regular expression filters and CA access security. CA Clients CA Gateway CA Servers

  4. CA Proxy Gateway Clients point to one proxy that distributes the data with minimal impact on the private parts. CA Clients CA Gateway CA Servers

  5. Caveats • The Gateway always introduces a non-scalable bottleneck. • A heavily loaded Gateway is a CPU and memory consuming application that usually will add overhead to the system. • Bad configuration (too loose) may put more load on the precious side instead of shielding the IOCs.

  6. Recent Developments • Gateway 2.0 (built against EPICS base 3.14.2) is complete and working. • More bugfixes in the Gateway, GDD, CAS / CAC, important performance improvements. • CAput logging feature (same as on IOC). • Work on documentation (user manual) started. BUT... • Still some crashes (bad) and brain-dead hang situations (much much worse). • Not yet officially released.

  7. Next Steps Mid-July: Jeff and Ken will try to fix the hang problems. After that: Independent of their results a release of the Gateway will be published. • Either a beta release:bad but still better than the old 3.13.2 based Gateway. • Or a stable 2.0:quite good, but still bad, with lots of room for improvements…

  8. Ideas All the nice ideas for improvements: will be postponed until stable operation of the Gateway is achieved. • New hierarchical configuration file format to improve performance (XML format?) • New configurable watchdog (steal from Channel Archiver) • Better code documentation (using Doxygen?) • CMLOG interface • Provide some tabular usage and statistics info as web page • Use Data Access (new data object) instead of GDD

More Related