NodePit Runner: Nodes

Node to configure the server endpoints

Nodes for different authorization methods

Manage users of the NodePit Runner, including registration, login, and password recovery.

Most activities on the Runner are organized within “projets” which allow users with different roles to collaborate.

Manage “Executors” which are responsible for running schedules. From an architectural perspective, executors are separate Docker services which connect to the API, execute a “Run” based on a “Schedule” and provide results. Executors are responsible for spawning workers, which are separate Docker containers to execute a “Run” - once finished, the worker is removed.

Manage global configuration such as email setup, license keys, etc.

Manage “Environments” which are the foundation for running “Schedules”. The Runner supports different types of environments, e.g. “Shell” for running shell scripts or “KNIME” for running KNIME workflows.

Manage, upload, and download files. Files can be e.g. uploaded by the user to supply scripts or workflows to a schedule, or provided by the Runner as artifacts which were generated during a “Run”.

Schedules are one of the central parts for the Runner. A schedule defines the execution of a task (e.g. a shell script, a KNIME workflow, …) at a specified time (e.g. every Monday at 15:00) within an “Environment”. Once a schedule is started, it is represented as a “Run”.

A “Run” is the exection of a “Schedule”. The run is started either automatically or manually and will then keep information about the execution, i.e. log output, statistics, status, and artifacts.

Various functionalities which do not fit into any other category.

Nodes for advanced configuration