This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Ganeti core".

The branch, master has been updated
       via  5e67cc2c7eb81612c03267a90c8cf08cdf228196 (commit)
       via  712f8a8a7ae2fe1e6d17a0fce7c01c49e48802a2 (commit)
       via  2602dd1f95c71e380dedd408a1a0417b85be7ce2 (commit)
       via  0702d0e4ae25d3f1536d529e27a953b6acb12dbd (commit)
       via  d0135eb81b0b2894c1f37fd3b63eb432102293e4 (commit)
       via  87e5927fafaee6aebf5bdbb6ed7e9fa1b7966e1b (commit)
       via  9ef96cec60916b830011bd515f4dc58fa01fce15 (commit)
       via  2e41a7c199414558e80ba86b332c4f9278496c8e (commit)
      from  976538e51bef20ed0d523a20b945623e9a297c12 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5e67cc2c7eb81612c03267a90c8cf08cdf228196
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 11:48:21 2014 +0200

    After killing check for death
    
    Once we sent a sigKILL to a process there is a high chance that it
    actually died. So this is a good point in time to verify death and
    clean up the job queue.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 712f8a8a7ae2fe1e6d17a0fce7c01c49e48802a2
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 12:01:11 2014 +0200

    Export function for job-death detection
    
    ...so that LuxiD can trigger that test directly, if it has reasons
    to believe a job died (e.g., after sending it a KILL signal).
    
    The function is a wrapper around checkForDeath that looks up the
    job by its id in the list of running jobs.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 2602dd1f95c71e380dedd408a1a0417b85be7ce2
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 12:44:40 2014 +0200

    Guard --kill by --yes-do-it
    
    Forcefully killing a job has high potential of messing up
    parts of the cluster. So better double-check the user's intent.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 0702d0e4ae25d3f1536d529e27a953b6acb12dbd
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 12:36:14 2014 +0200

    Document the --kill option in gnt-job cancel
    
    Also add a warning, that this option is a good way to mess
    up any objects touched by the job.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit d0135eb81b0b2894c1f37fd3b63eb432102293e4
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 10:36:03 2014 +0200

    Add a kill option to gnt-job cancel
    
    Add a new --kill option to gnt-job cancel. This option
    will expose the new "kill" option of the CancelJob luxi
    command.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 87e5927fafaee6aebf5bdbb6ed7e9fa1b7966e1b
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 10:42:45 2014 +0200

    Expose the optional kill in CancelJob in the luxi client
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 9ef96cec60916b830011bd515f4dc58fa01fce15
Author: Klaus Aehlig <[email protected]>
Date:   Wed Sep 24 11:21:11 2014 +0200

    Handle the kill option in CancelJob luxi requests
    
    To do so, extend the cancelJob function by an additional kill flag.
    Also, if we kill a job, we expect it to die regardless of whether it
    already acquired all the needed locks.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

commit 2e41a7c199414558e80ba86b332c4f9278496c8e
Author: Klaus Aehlig <[email protected]>
Date:   Tue Sep 23 17:50:01 2014 +0200

    Extend the cancel-job luxi request by a kill flag
    
    This flag will instruct luxid to send send a SIGKILL
    instead of a SIGTERM if the job to be canceled has
    already started. To not have to change RAPI all in
    one big change, we keep the wire protocol backwards
    compatible even though this is not strictly necessary
    for the luxi protocol.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Petr Pudlak <[email protected]>

-----------------------------------------------------------------------

Summary of changes:
 lib/client/gnt_job.py       |   24 ++++++++++++++++++++----
 lib/luxi.py                 |    4 ++--
 man/gnt-job.rst             |    7 ++++++-
 src/Ganeti/JQScheduler.hs   |    9 +++++++++
 src/Ganeti/JQueue.hs        |   19 +++++++++++--------
 src/Ganeti/Luxi.hs          |   14 +++++++++-----
 src/Ganeti/Query/Server.hs  |    6 ++++--
 test/hs/Test/Ganeti/Luxi.hs |    2 +-
 8 files changed, 62 insertions(+), 23 deletions(-)


hooks/post-receive
-- 
Ganeti core

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ganeti-commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to