Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-346 Notification Support in Pegasus using Monitord
  3. PM-348

Changes to Pegasus to create a notification input file for monitord

XMLWordPrintable

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major Major
    • master, 3.1
    • Affects Version/s: master, 3.1
    • Component/s: Pegasus Planner
    • None

      Karan will help Rajiv on this.

      Format for the input file is as follows

      WORKFLOW|JOB|DAXJOB|DAGJOB ID NOTIFICATION_CONDITION ACTION
      INVOCATION JOB_IDENTIFIER INV.ID NOTIFICATION_CONDITION ACTION

      ID

      will have different meaning depending on the entity type

      • workflow - ID is wf_uuid
      • job,daxjob,dagjob - ID is the job identifier in the dag file

      NOTIFICATION_CONDITION

      is one of the following:

      never ---> (default). Never notify of anything. This is useful to temporarily disable an existing notifications.
      start ---> create a notification when the job is submitted (DAGMan state == EXECUTE).
      on_error ---> after a job finishes with failure (exitcode != 0).
      on_success ---> after a job finishes with success (exitcode == 0).
      at_end ---> after a job finishes, regardless of exitcode.
      all ---> this is like start and at_end combined.

      ACTION
      is what needs to happen when condition is satisfied. It will be executable + arguments.

      The INVOCATION lines are only generated for clustered jobs, to specifiy the finer grained notifications for each constitutent job/invocation

            Assignee:
            vahi Karan Vahi
            Reporter:
            vahi Karan Vahi
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: