Skip to content
  • John Snow's avatar
    5ccac6f1
    blockjob: add block_job_start · 5ccac6f1
    John Snow authored
    
    
    Instead of automatically starting jobs at creation time via backup_start
    et al, we'd like to return a job object pointer that can be started
    manually at later point in time.
    
    For now, add the block_job_start mechanism and start the jobs
    automatically as we have been doing, with conversions job-by-job coming
    in later patches.
    
    Of note: cancellation of unstarted jobs will perform all the normal
    cleanup as if the job had started, particularly abort and clean. The
    only difference is that we will not emit any events, because the job
    never actually started.
    
    Signed-off-by: default avatarJohn Snow <jsnow@redhat.com>
    Message-id: 1478587839-9834-5-git-send-email-jsnow@redhat.com
    Signed-off-by: default avatarJeff Cody <jcody@redhat.com>
    5ccac6f1
    blockjob: add block_job_start
    John Snow authored
    
    
    Instead of automatically starting jobs at creation time via backup_start
    et al, we'd like to return a job object pointer that can be started
    manually at later point in time.
    
    For now, add the block_job_start mechanism and start the jobs
    automatically as we have been doing, with conversions job-by-job coming
    in later patches.
    
    Of note: cancellation of unstarted jobs will perform all the normal
    cleanup as if the job had started, particularly abort and clean. The
    only difference is that we will not emit any events, because the job
    never actually started.
    
    Signed-off-by: default avatarJohn Snow <jsnow@redhat.com>
    Message-id: 1478587839-9834-5-git-send-email-jsnow@redhat.com
    Signed-off-by: default avatarJeff Cody <jcody@redhat.com>
Loading