Conveners
Build and Deployment
- Ralph Lange (ITER Organization)
Build and Deployment
- Ralph Lange (ITER Organization)
Build and Deployment
- Ralph Lange (ITER Organization)
Description
Support modules and applications
Some background on this session, and a few questions that the talks might help answering.
The EPICS build system at PSI differs from the standard EPICS way of building IOCs. We build all software modules (e.g. drivers) as loadable modules and load them into softIoc at run-time. This requires a system for dealing with versions and dependencies during build, deployment, and IOC startup.
The EPICS development and deployment at ESS is based on the concept developed at PSI, and adapted to our specific challenges. These include dealing with many external developers in geographically separated locations, having different environments and levels of expertise. The environment E3 addresses a number of issues that we had in our first attempt but keeps the same main core concepts and...
Manually maintaining configure/RELEASE files and building EPICS support modules in the correct order is an error-prone and tedious task, especially if different versions of different sets of modules are to be kept around in order for old applications to remain buildable.
SUMO was developed as a tool to automate all of this work. A single JSON file with a simple schema is used to specify...
The NSLS-II Debian Repository was updated to include recent contributions to the epicsdeb project on GitHub. The repository is now available at the public mirror https://epicsdeb.bnl.gov/debian/. Notable news:
- Debian 9 (stretch) packaging is now available.
- For stretch and further, 32-bit builds were dropped and packages are no longer provided.
- For stretch and further, the RTEMS build...
SNACK stands for SiNgular Application Configuration Kit and is an Ansible-based software configuration and deployment tool used at NSLS-II, primarily on accelerator side, to provide means of retaining and deploying EPICS IOCs. Despite the solution versatility, rich feature set, and reliable operation as applied to deploy close to two hundred application instances, there is no sufficient...
The Facility for Rare Isotope Beams (FRIB) project follows a standardized and automated process to continuously deploy and deliver EPICS IOCs from development to test and production environments. Unfortunately, building, testing, packaging, and deploying software can be a time consuming and error prone process, so at FRIB we use a set of different tools to make this process easy, safe,...
ITER Instrumentation and Control System comprise all hardware and software required to operate ITER. CODAC (Control, Data Acquisition and Communication) provides centralized services to Plant Systems during installation, testing, integration and operation. Such CODAC Services include the Operator Interface BOY, Alarm System BEAST, Archiving System BEAUTY and Electronic Logbook OLOG.
For...
We present rsync-dist, a tool to deploy build artefacts from an EPICS
application to remote servers. It uses ssh for authentication and
authorization, log files for auditing, and supports unlimited rollback. In
contrast to standard CI tools, its use is decoupled from source version
control to allow developers to easily install test and debug versions of
their software.
