JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 8

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 9

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The JOC Cockpit manages the inventory of workflows, jobs and related objects. In addition, the JOC Cockpit is used to monitor and to control workflow execution by other components.
    • An outage of JOC Cockpit does not impact workflow execution by the Controller or by Agents.
    • An outage of JOC Cockpit translates to the fact that users are unaware about what workflows are currently executed, however, this does not indicate that workflows would not run.
    • Any results about workflow execution are reported later on by a Controller when the JOC Cockpit becomes available.
  • The Controller orchestrates Agents and forwards, for example, JS7 - Workflows and the JS7 - Daily Plan to Agents.
    • If the Controller is not available then this does not affect availability of JOC Cockpit. 
    • For Agents the loss of a connection from the Controller means that they cannot immediately report back execution results. However, Agents will continue to execute workflows that are within their reach of autonomous workflow instructions and will store the information about JS7 - Order State Transitions and log output created by jobs with their journal. This information will then be forwarded to a Controller later.. Find details about JS7 - Workflow Instructions that are eligible for Agent autonomy from the JS7 - Workflow Execution with Controllers and Agents article.
    • A prominent The exception to this rule are workflows that implement cross-platform scheduling, i.e. executing jobs within the same workflow on different Agents. In this situation an Agent can proceed with a workflow only to the nodes only that are assigned to that Agent.
  • An Agent will execute JS7 - Workflow Instructions as long as the instructions - including the execute execution of jobs - are assigned that Agent.
    • Agents expect Controllers to establish a connection and will respond to connection requests but cannot actively establish a connection to a Controller.
    • Agents receive Workflow configurations and the Daily Plan from a Controller and know when to run orders. Agents therefore work semi-autonomously within the limits of being assigned the relevant workflow instructions.

...