Psot scheduler 1.0.0

Accepts one of the following messages:

• #0new jobnew_job

  Part 1/2 of the 'new_job' conversation
  Creates a new job and a location for the job related data. The job will be in an uninitialized state until it is submitted. Uninitialized jobs are removed after a period of time. Expected reply: reply_new_job

  Payload

  object

  job object

  Additional properties are NOT allowed.

  Headers

  object

  action

  string

  Allowed values:
  • "new_job"

  Additional properties are NOT allowed.

  Examples

  Payload

  {}
  

  This example has been generated automatically.

  Headers

  {
    "action": "new_job"
  }
  

  This example has been generated automatically.

• #1submit jobsubmit_job

  Part 1/2 of the 'submit_job' conversation
  After a job was created with new_job, a job submitter can initialize everything and submit it here.

  Payload

  object

  uid: submit_job

  Datatype to submit psos jobs to the psos scheduler

  id

  required

  string

  format: uuid

  The job id.

  data

  required

  object

  job related data, is individual for each type of job

  Additional properties are allowed.

  plan

  required

  array<object>

  non-emptyuid: execution

  the execution plan

  name

  string

  address

  required

  string

  states

  array<object>

  uid: job_state

  value

  required

  string

  label

  required

  string

  Additional properties are NOT allowed.

  Headers

  object

  action

  string

  Allowed values:
  • "submit_job"

  Additional properties are NOT allowed.

  Examples

  Payload

  {
    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
    "data": {},
    "plan": [
      {
        "name": "string",
        "address": "string",
        "states": [
          {
            "value": "string",
            "label": "string"
          }
        ]
      }
    ]
  }
  

  This example has been generated automatically.

  Headers

  {
    "action": "submit_job"
  }
  

  This example has been generated automatically.

• #2Executor reports free capacityreport_executor

  Part 1/3 of the 'hand over job to executor' conversation
  The executor sends this message to the scheduler if the executor has the capacity to handle another job. Expected reply: reply_report_executor_1

  Payload

  string

  The channel name specific for the scheduler

  Headers

  object

  action

  string

  Allowed values:
  • "report_executor"

  Additional properties are NOT allowed.

  Examples

  Payload

  string

  This example has been generated automatically.

  Headers

  {
    "action": "report_executor"
  }
  

  This example has been generated automatically.

• #3Update job dataupdate_job_data

  Part 1/2 of the 'update job' conversation
  Replaces the jobs data with the data send in the payload

  Payload

  object

  id

  string

  job id

  data

  object

  The new job data

  Additional properties are allowed.

  Additional properties are NOT allowed.

  Headers

  object

  action

  string

  Discriminator to distinguish different message types

  Allowed values:
  • "update_job_data"

  Additional properties are NOT allowed.

  Examples

  Payload

  {
    "id": "string",
    "data": {}
  }
  

  This example has been generated automatically.

  Headers

  {
    "action": "update_job_data"
  }
  

  This example has been generated automatically.

• #4Report execution resultreport_execution_result

  Part 1/2 of the 'report execution result' conversation
  

  Payload

  object

  id

  string

  job id

  status

  string

  Allowed values:
  • "success"
  • "failure"

  Additional properties are NOT allowed.

  Headers

  object

  action

  string

  Allowed values:
  • "report_execution_result"

  Additional properties are NOT allowed.

  Examples

  Payload

  {
    "id": "string",
    "status": "success"
  }
  

  This example has been generated automatically.

  Headers

  {
    "action": "report_execution_result"
  }
  

  This example has been generated automatically.

• #5delete jobdelete_job

  Part 1/2 of the 'delete_job' conversation
  Deletes a job

  Payload

  string

  job id

  Headers

  object

  action

  string

  Allowed values:
  • "delete_job"

  Additional properties are NOT allowed.

  Examples

  Payload

  string

  This example has been generated automatically.

  Headers

  {
    "action": "delete_job"
  }
  

  This example has been generated automatically.

• #6new jobget_job

  Part 1/2 of the 'get_job' conversation
  Retrieves a job by its id

  Payload

  string

  Headers

  object

  action

  string

  Allowed values:
  • "get_job"

  Additional properties are NOT allowed.

  Examples

  Payload

  string

  This example has been generated automatically.

  Headers

  {
    "action": "get_job"
  }
  

  This example has been generated automatically.

Accepts the following message:

{
  "action": "report_free_capacity"
}

Accepts one of the following messages:

• #0Is aliveis_alive

  Part 1/2 of the 'is alive' conversation
  Scheduler asks the executor if it is still running. Expected reply: reply_is_alive

  Headers

  object

  action

  string

  Discriminator to distinguish different message types

  Allowed values:
  • "is_alive"

  Additional properties are NOT allowed.

  Examples

  Headers

  {
    "action": "is_alive"
  }
  

  This example has been generated automatically.

• #1Cancel jobcancel_job

  Part 1/2 of the 'cancel job' conversation
  Scheduler instructs executor to cancel the job with the given id. Expected reply: reply_cancel_job

  Payload

  restricted any

  id

  string

  job id

  Headers

  object

  action

  string

  Allowed values:
  • "cancel_job"

  Additional properties are NOT allowed.

  Examples

  Payload

  {
    "id": "string"
  }
  

  This example has been generated automatically.

  Headers

  {
    "action": "cancel_job"
  }
  

  This example has been generated automatically.

Accepts the following message:

{
  "job_object": {
    "id": "string",
    "created": "2019-08-24T14:15:22Z",
    "lastUpdated": "2019-08-24T14:15:22Z",
    "deleteAt": "2019-08-24T14:15:22Z",
    "location": "string",
    "state": {
      "value": "Failed",
      "label": "string"
    },
    "data": {}
  }
}

{
  "action": "deleted"
}

Accepts the following message:

{
  "action": "timeout"
}