C2D.2: Orchestration layer

[alexcos20]

Former known as "operator-service", this layer handles interactions between ocean-node core layer and different execution environments.

Since we will have two types of operations (docker API & k8 API), which sometimes overlap we will start with the following structure:

• new classe, derived from C2DEngine, called C2DEngineLocal. From this one, we will create two more:
  • C2DEngineK8API
  • C2DEngineDockerAPI

In a nutshell, here is the implemented functionality of new classes

New job:

• take a new workflow (created by startJob core handler)
• insert workflow in database
• signal engine handler to take over the job execution

Views:

• exposing list of compute environments for all engines (both Docker & K8 will have compute envs defined through env variables)
• exposing list of running jobs and limits (max concurrent jobs, etc)
• read workflow status when c2d getStatus core is called
• serve job results when c2d getJobResult is called