GitHub user bhaisaab opened a pull request:

    https://github.com/apache/cloudstack/pull/754

    CLOUDSTACK-8762: Check to confirm disk activity before starting a VM

    Implements a VM volume/disk file activity checker that checks if QCOW2 file
    has been changed before starting the VM. This is useful as a pessimistic
    approach to save VMs that were running on faulty hosts that CloudStack could
    try to launch on other hosts while the host was not cleanly fenced. This is
    optional and available only if you enable the settings in agent.properties
    file, on per-host basis.
    
    Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack 4.5-CLOUDSTACK-8762

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/754.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #754
    
----
commit bd12614c2fe56aebb4ea81e128368368fec6f092
Author: Rohit Yadav <rohit.ya...@shapeblue.com>
Date:   2015-08-27T09:47:19Z

    CLOUDSTACK-8762: Check to confirm disk activity before starting a VM
    
    Implements a VM volume/disk file activity checker that checks if QCOW2 file
    has been changed before starting the VM. This is useful as a pessimistic
    approach to save VMs that were running on faulty hosts that CloudStack could
    try to launch on other hosts while the host was not cleanly fenced. This is
    optional and available only if you enable the settings in agent.properties
    file, on per-host basis.
    
    Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to