Feature: Simulation State Machine

[YannickP99]

✨ Feature Overview

Implement a state machine for the simulation. Currently the simulation is automatically started on the container startup and one the simulation finishes or fails, the container closes automatically. A state-machine will enable more control over the simulation and prevent constant open and closing of containers if user needs multiple runs of simulation.

🚀 Proposed Solution

• Possible states could be:

  • idle: container waits for commands
  • running: simulation is running
  • completed: simulation finished successfully
  • failed: simulation finished because of an error
  • shutting-down: container is in process of shutting down

• This would also make the monitoring of running containers more easy and enable to run a saving function of the scene on shutting down

⚙️ Technical Requirements

• Possible frameworks, states and API-calls to control the simulation need to be researched/created

❔Open Questions

• How to communicate between frontend-backend-simulation (additional API server inside container?)
• How to monitor internal container status
• Create own sub-module for simulation to handle complexity and retain API structure? (sub-module like scene-manager)
• Simulation files in own repo and take repo as git submodule

Alternative Solution:

Think about use of load balancing and Kubernetes to control load - possible to control used resources on server -> talk to Oussama Raies