Meeting 27 March 2018
- Alessandro Caproni (ESO)
- Filippo Fagioli (ASTRI/CTA)
- Jazmine Maldonado (Inria Chile)
- Maximiliano Olivares (Inria Chile)
- Sebastian Fehlandt (Inria Chile)
- Progress of the docker containers for install v2 at the OSF
- Looked again at differences between postgres and MySQL and it seems that now MySQL is the fovorite. See for example DB-Engines. Any thought?
- Implementation of rules for the Weather Plugin, what should be done by the TF and what should be done by the plugin? For example:
- Alma-time timestamps Ale: in the IAS we use only UTC/ISO-8601 formatted timestamps
- Null values
Ale: plugins only collect and send values to the IAS; plugins can apply filters for example to remove noise, produce averages and so no but no rules/heuristics; the rules are implemented by means of TFs
- If we deploy by docker containers what are the steps to update the configuration in the CDB? Usually we update the CDB and restart the involved Supervisors
- The CDB of last demo was generated by createCDB.py with one Supervisor. It is ok at the beginning but in operation we want to be able to change the CDB
- release 2.0.0 of the core out
- Working on issue #80 about supporting identical devices (feedback very welcome on the issue)
- start looking at priorities #82. Any preference from your side?
- Current work on the Issues #20 and #19 of the ias-webserver.
- Remove dependency on django models for alarm management.
- Releases of AlmaWeatherPlugin, DummyPlugin, WebServer and Display.
- Still working on issue #64
- Modify the CDB dockerfile to expose the files and allow us to modify the CDB.
- Create another docker compose to deploy the IAS in the Alma Control Room (removing the dummy plugin).
- Create the releases of the AlmaWeatherPlugin, WebServer and Display.
- Remove one of the tables in the IAS Diplay
- Modify the Plugin to avoid send updates when the values are the default ones or they are null values.
