Fixes the HB of the UdpPlugin

The HB of the UDP plugin was not able to connect to a kafka broker running in a server other then the local host

Fixes plugin filters and kafka producers

This patch fixes an issue when the configuration of plugins did not specify filters for monitor points. In such a case the noneFilteris automatically selected.

There was an exception returned by kafka when teh same tool instantiates more kafka producer with the same client.id. It has been fixed by renaming the producer used by the heartbeat.
A more definitive solution will be delivered in #110

UdpPlugin for python2

v3.0.2 ships a UdPplugin for legacy python 2.7 installations.

There is also a python kafka client to dump IasValue published in the BSDB: iasValueDumper

Bug fixes and the BackupSelector transfer function

Minor release shipping

• bug fixes in the python scripts
• the BackupSelector transfer function to select one monitor point or abackup if the main monitor point is not available or OPERATIONAL

Release 3 with many new features

This release provides many improvements and new features:

• the alarm has 4 priority levels: LOW, MEDIUM, HIGH and CRITICAL being MEDIUM the default; an API allows to increase/decrease the priority of an alarm at run time
• IAS tools provides an heartbeat in a dedicated kafka topic; the time interval is set in the CDB
• the core supports the replication of DASUs to cope with alarms from replicated identical devices
• plugins can be developed in python
• the monitor points passed to the TF hides the internals of the IAS and are consistent in java and scala
• docker images are based on CentOS
• fixes in the python logging
• upgrade of several tools

Log fixes

This is a bug fix release solving 2 issues that we detected after deploying v2.0.0 in operation:

• log rotation not working
• logging too often

Both issues together saturated the disk space in few hours of operations. All the alarms in the display where not valid because without disk space were not possible to update their values.

Logging from plugins has not yet been fixed

First release for the control room

Release description

Release 2.0.0 is the first version to be installed at the OSF. It fixes several important points left over from v1.0.0.

Main fixes and improvements

• The output generated by DASUs is published following the requirements: immediately on change and at regular time intervals if it did not change. Monitor points and alarms produced by plugins, as well as the alarms generated by the DASUs are instrumented with timestamps to follow their trip time from the remote controlled system up to their publication in the BSDB.
• Python has been upgraded to v3.5.
• User friendly commands have been provided to start the IAS core tools so that the final user does not need to know the programming language neither the java/scala class.
• All references to the prototype have been removed by renaming classes and packages.
• Log file names produced by java/scala tools clearly reports the ID of the tool to ease debugging. The log generated by kafka was too verbose and has been reduced (now level INFO by default).
• Each alarm and synthetic parameter produced by DASU is instrumented with the full running ID of the dependent monitor points where the dependent monitor points are the inputs to the DASU digested by the transfer functions of the ASCEs to finally produce the output.
• The TFs can set additional properties to alarms that will be stored in the BSDB. For example if an alarm is produced because a temperature is too high, the TF can set an additional property with the value of the temperature. Such a value can the be displayed in the control room.
• Time stamps are in UTC. The JSON strings published in the BSDB shows the timestamps as human readable strings instead of longs.
• Plugin configuration has been made easier allowing to specify a global filter that can be overridden for specific monitor point values if needed. This reduces the amount of information to be written in the JSON configuration file.

Known problems

Plugins does not send monitor point and alarms following the requirement - #58

Initial production release

Release description

Release 1.0.0 allows to get monitor point and alarms from the plugins, convert them to IAS data structures, forward them to the Supervisors and finally to DASUs and ASCEs to generate alarms. The WebServerSender feeds the web server with the alarms produced by DASUs to be finally displayed in the panels in the control room.

This version is still not yet feature-complete as it lack at least the injector of alarm in the LTDB.

This version has been shown in a demo with ALMA, ESO, NRAO stakeholder on Feb. 5th 2018.
The demo consisted of one plugin collecting monitor points from the ALMA weather stations located at the AOS, 5ooom a.s.l. and showing them in a tabular view.
A dummy plugin allowed to manual set monitor points and check how their states changed in operator panel.

Known problems

• the way the refresh rate is used by DASUs and plugins is not consistent - see #52 and #58
• DASUs send the output even if their values did not change - #63

Initial generation of alarms by DASUs

Release description

This is the first release that closes the loop from the plugins to the generation of alarms by means of DASU and their ASCEs.

Plugins collect monitor point values and alarms from monitored system and send the alarms to the BackStage DataBase (BSDB).
DASUs get such monitor points and alarms and send them to the ASCEs that, in turn, generate alarms or synthetic parameters that finally go in the BSDB.

The release is not yet ready to go in production.

Known problems

The validity test of TestTransferFunction does not pass because it is not possible to propagate the validity though the IASValue (@see Issue #19)