Hermes workshop

[lior-antonov]

Hermes is a tool that reads a json file that describes a workflow using nodes that describe jobs and runs it. As part of its integration into the UI we will proabably need to build some sort of workshop/editor to edit such jsons. Since it is built like and ETL, we will need a node based editing layout like: n8n, NodeRED, Blender's Node Editor, etc...

From a quick Google search I found ReactFlow which looks promising.

Currently our main usage of Hermes are workflow for OpenFOAM simulation that are too bothersome to do by hand. We will also want to generally build workflows to simplify monotonous tasks we do here and can't directly integrate into the UI.
Until now we have been writing those json's manually which is very annoying and not readable. Using a node editor as I described would make this tool a lot more user friendly.

@erasta what do you think?

[erasta]

ReactFlow is definitely the best for this.
is it possible to obtain the possibilities and contents of the nodes programmatically from hera/hermes?
where should the json generated be stored at? locally / remotely / configurable?
should we start with this before #810 or some consolidation so action options are clearer?

[lior-antonov]

The entire workflow json is saved in the db. You can get it with the hermes workflow using either of the get methods it implements. Almost any workflow had a parameters node which will be the focus when working implementing actions. Not to be confused with the parameters field in the mongo document that contains the values of all the parameters of all nodes.

The user will have to enter the path to use to save the hermes workflow. Generally it should only be saved in the db. There a method that exports the db version and overrides/generates the file specified in the resource field.

I think focusing on this issue prior to #810 is better, it will simplify the creation of actions which in itself is a good testing ground for this issue.