jeonghanlee / phoebus-env

Phoebus and Alarm Trio Configuration Environment

Phoebus and Alarm Trio Configuration Environment

Configuration Environment for Phoebus [1] and Alarm Trio [2].

Roles

To download, install, setup all relevant components, one should do many steps manually. This repository was designed for the easy-to-reproducible environment for ControlSystemStudio/phoebus and its alarm services (alarm-server, alarm-logger, and alarm-config-logger), because most of their configuration are common, shareable, and consistent.

Notice

• This environment can change a system configuration as small as possible. Thus, all things we can do is to remove installation directory and clean up systemd services properly. It uses an ugly makefile, Linux command line tools, and bash shell scripts.

• There are a plenty of tools around us to do similar jobs. This repository is designed for my working environment and conditions. I do not have available time to learn others automation tools, such as ansible, and so on. And I am enough to be tired by thier own incompatibilities within their release versions.

Phoebus Building and Installation

See docs/Phoebus.md

If one would like to see the current status of the native support of Phoebus on Apple M1 aarch64, please docs/PhoebusOnAppleM1.md

Alarm Trios Building and Installation

See docs/AlarmTrio.md

Reporting issues

If you encounter any bugs you can report them here on Github.

Known issues

See docs/KnownIssues.md

References

[1] https://github.com/ControlSystemStudio/phoebus

[2] https://github.com/ControlSystemStudio/phoebus/tree/master/services

phoebus-env's Issues

alarm-server settings

-settings option has the inconsistent way to handle the kafka server (host:port). The valid options can be transferred into -server option only. It should be checked later carefully.

user and group permission

MacOS aarch64 on M1

Branch is prepared for this, with Azul Java 15, I successfully compile the phoebus, however, I cannot run it because openjfx doesn't support this architecture yet. It looks like this will be available with JDK 16 according to their development repositories.

alarm-logger help arg doesn't work

The input arg -h* doesn't work. Should be checked later.

implement logrotate

If we move all log files into /var/log/procserv/, it will be implemented into procServ configuration. I think, this will be better solution than the current configuration. However, the modification of the systemd unit file is needed, so I keep this issue as a place holder.