JCOP FWWG 4 April 2023
JCOP Framework Working Group Meeting, 4th April 2023
INDICO Link: https://indico.cern.ch/event/1266843/
Present:
in the room: Stefan Schlenker, Fernando Varela, Mariusz Suder, Luis Miguens, Piotr Golonka
via ZOOM: Michael Ludwig, Pavel Fiala, Georgios Leventis, Raul, Cristina Vazquez, Geraldine Thomas, Piero Giorgio Verdini, Wassef Karimeh, Frank Glege, Ben Farnham, Soham Biswas, Luis GC
Complete set of slides available in INDICO
ELTEK OPC UA Server
- Ben presented the current status of the OPC-UA Server for ELTEK power rectifiers. The 1.0.0 version is available for Linux and Windows (on the OPC-UA Servers page of the JCOP website). It exposes the items that are visible in the web interface of ELTEK devices - it is a subset of the complete available set of items declared in the SNMP MIB files, and likely the "sensible set".
- Ben requested the users to review the list of items (using eg. the OPC-UA Expert tool) and tell if there is anything missing. Only once this is established it would make sense to start the development of the WinCC OA component. Agreed that feedback must be given before end of April.
- if no feedback received, we will proceed with integrating all the items present in the 1.0.0 release of the OPC UA Server
- CMS confirmed that they will likely also use ELTEK as this is the standard CERN EPool's solution for AC/DC rectifiers these days.
- ATLAS confirmed that they component is indeed needed: even though the operation could be done with the web interface, the very missing part is archiving of data.
- Michael asked if Ben uses MIB files or does a "SNMP walk" to detect hardware. Ben is using MIB files for this implementation.
WinCC OA 3.19
Piotr announced the general availability of WinCC OA 3.19 for users at CERN and in collaborating institutes, together with the JCOP Framework 9.0.0. They are available in the standard download pages, and there is a validation page - see links in the presentation
Luis presented the new installer for WinCC OA 3.19 on Windows. It is much simpler and user friendly, notably where it comes to installing a new "patch" version; in many situations reboot is not needed anymore (unless a subpackage such as MS VisualStudio Runtime requiring it needs to be installed) . The new numbering scheme was explained, as required by the WIX tool used by ETM for packaging - see the presentation for details
It was unclear whether WinCC OA 3.19 and 3.16 could be installed and used on the same machine. Seems to be some confusion, as this is a "must have solution" notably to have the UIs of both versions running in Terminal Servers during the transition/upgrade period in which both version may need to be run. Action: Luis to clarify this and if neeed escalate with ETM.
Mariusz presented the status and roadmap for the JCOP Framework 9 releases and the notable work that had to be done.
ATLAS singaled that they may need some help in porting a driver (used in one of subdetectors) to CMake build system. It was confirmed that the experience built by BE-ICS-FT in this domain during the framework porting should be adequate.
Piotr presented the new licensing mechanism and the process of activating a license ticket. Note that the assignment of tickets is currently a manual process and hence expect delays. An alternative is to use the CERN License Server, which was presented by Georgios. It requires that the machine is at CERN and the user has a CERN login; otherwise it works "out-of-the-box", and the scripts to start the "ssh tunnel" that is required for it are already present in the WinCC OA 3.19 distribution. The license server has some limitations and it is in the testing phase at the moment; we also expect some robustness improvements for the licensing mechanism to be implemented by ETM.
A question was asked if the tunnel to the license server could be used without kerberos. Yes, definitely: the user will be prompted for the password in this case.
Another question was if it was tried to run the tunnel as a kind of a service. It was explained that the idea was to integrate it more tightly with WinCC OA Project Administrator panel, whereby it would be trivial to start and stop it. This is work-in-progress at the moment.
Certiticate expiry warning
In the AOB part Mariusz reported on the analysis of the situation with the expiring certificates used by WinCC OA 3.16 and older. This has recently been announced by ETM/Siemens in a warning message that souded quite scary. Apparently we are not affected as we do not use mxProxy or httpServer features of WinCC OA, and for OPC-UA we do not use the security features hence the expired certificate would not affect our OPC-UA connectivity for the framework devices. And even if someone enabled them, the actual certificate would expire only in 2028, not 2023 as verified by Mariusz. The presentation shows how one could verify the certificate expiry dates.