Deploy Alarm Handler and Viewer in ITF

Alarm handler deployment: The Elettra Alarm Handler was selected as the Alarm Handling technology as per ADR-68. It was deployed and tested in PI17, in a proof of concept manner. The need for Alarm handling is growing within the system. This feature aims to deploy the Alarm Handler at <TBD> ITF alongside the Alarm Viewer for use by AIV engineers.

To allow testing and familiarisation by the AIV teams, this feature also covers the provision of some Tango level Alarms from the TMC subsystem and potentially a second subsystem. This will allow the generation of complex rules using the Alarm handler.  

Viewer: (Originally part of SP-3685)The Alarm-ng, Elettra's GUI alarm viewer, is selected as the tool for viewing the alarms. Currently, the alarm handler solution implemented in PI 17 does not include Alarm-ng component. So, the tool needs to be packaged with the existing alarm handler and delivered via the alarm handler helm chart.

The Alarm-ng is a desktop-based GUI tool and its deployment in a cloud environment needs special arrangement of access.

Dec-7 Update (PI-21):

As VNC access is not permitted in the ITF, an alternative mechanism for remotely accessing the Alarm Viewer is agreed between TMC, AIV and Services. Slack reference here:

• Run the Elettra GUI as a Linux executable on an existing Windows terminal server (If it turns out that running the program as a native Linux application is not possible go for option 2):
• Recompile it as a Windows program from source code, deploy on an existing Windows terminal server in MID-ITF. This will be worked out by Thomas.Juerges and T.Ives 

Documentation: To provide a complete workable Alarm handler a set of User Documentation covering Tango Alarm configuration, Deployment of the Alarm Handler and Viewer and generating 'complex' rules within the Alarm Handler is to be provided.

*NOTE: The use of the word 'complex' is intended to mean an Alarm rule created within the Alarm Handler which uses >1 condition to trigger the alarm. 'Complex' may be misleading, as a rule like "if condition-x and condition-y are met raise alarm"

 -------------------------------------------------------------------------------------------------

Older Discussion (for reference):

As per ADR-68, the preferred way of accessing the tool is using VNC technology. Thus it is necessary to set up the deployment configuration that allows remote access via VNC client, preferably from a web browser.

Update on Sep 7

Based on the slack conversation here VNC cannot be supported in STFC. Thus after discussion between the development team, feature owner and architect it is decided that for the GUI work, deployment of Elettra GUI in STFC cluster is not needed. The demo can be dome from developer's machine. Since VNC access is enabled from mid ITF, it is desired that alarm handler deployment is done and demonstrated from itf. It can be an uncommitted work. This needs to be informed to Atlas/Viola team.