Multiple backends for execution of FMUs?

[CThuleHansen]

FMUs are developed for different platforms, where the main ones are Linux 32 and 64, Windows 32 and 64, and Mac 64. Some FMUs are cross-platform in the sense that they contain binaries for all platforms. Yet, many of them are not and only contain binaries for a single platform.

Maestro has a mechanism for connecting to a daemon on a different platform from where the master is executed. @lausdahl can elaborate on this once needed.

Yet, the dynamic fmu checker does not have anything like this.

It would be great with a general strategy and implementation on how we would like to perform this in the future - also from view of the into-cps cloud app.

In context of the into-cps cloud app we would most likely need some sort of authentication such that the usage of our servers does not sky rocket.

Tasks

I see the tasks being:

1. Develop and Deploy Generic Daemons to different platforms that can execute both dynamic fmu checker and maestro daemons and what else might be needed?
2. Demonstrate how to use 1. and hopefully publish about it
3. Test strategy for cross-platform FMUs. Both external (supplied by third party) and internal (produced by us)
4. INTO-CPS Cloud App connect to this infrastructure

Publication

• Formalise the communication with the daemon? kulik?
• Work in this area - can we make a novel approach?

Input

I would love inputs on this!!! Tagging: @pglvdm @clagms @IDhugo @clegaard @lausdahl @mdinc1972 @kulikthomas

[clagms]

Summary of the discussion so far:

• This is important, as many of the bugs found had to do with platform specific issues.
• currently, I'm all tied up exploring the next dynamic fmu check iteration (for model checking and model based testing).
• we will come back to this later to see how it can be implemented.

[idhugoid]

This is a good idea. Currently the cloud app has a login feature based on Firebase. So the sky rocket resources usage problem can be solved using it, but I think what we are looking for is an API key.

The cloud app does a prototypical launch an managing of COEs by itself, but on a Linux platform only. It would be interesting to have a web service providing the COE pool concept (as conceptualized in the Overture app paper) with the features you describe.

For starters it would allow other services (as the into-cps cloud) to request validation and co-simulation services targeting different platforms... Then it would put in practice a separation of concerns: the app interfaces with the users while the backend provides the different COEs.

This looks promising. I am in!