Skip to content
  • John Snow's avatar
    2da4617a
    blockjobs: add prepare callback · 2da4617a
    John Snow authored
    
    
    Some jobs upon finalization may need to perform some work that can
    still fail. If these jobs are part of a transaction, it's important
    that these callbacks fail the entire transaction.
    
    We allow for a new callback in addition to commit/abort/clean that
    allows us the opportunity to have fairly late-breaking failures
    in the transactional process.
    
    The expected flow is:
    
    - All jobs in a transaction converge to the PENDING state,
      added in a forthcoming commit.
    - Upon being finalized, either automatically or explicitly
      by the user, jobs prepare to complete.
    - If any job fails preparation, all jobs call .abort.
    - Otherwise, they succeed and call .commit.
    
    Signed-off-by: default avatarJohn Snow <jsnow@redhat.com>
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
    2da4617a
    blockjobs: add prepare callback
    John Snow authored
    
    
    Some jobs upon finalization may need to perform some work that can
    still fail. If these jobs are part of a transaction, it's important
    that these callbacks fail the entire transaction.
    
    We allow for a new callback in addition to commit/abort/clean that
    allows us the opportunity to have fairly late-breaking failures
    in the transactional process.
    
    The expected flow is:
    
    - All jobs in a transaction converge to the PENDING state,
      added in a forthcoming commit.
    - Upon being finalized, either automatically or explicitly
      by the user, jobs prepare to complete.
    - If any job fails preparation, all jobs call .abort.
    - Otherwise, they succeed and call .commit.
    
    Signed-off-by: default avatarJohn Snow <jsnow@redhat.com>
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
Loading