cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8762) Check KVM disk files for activity before starting VM
Date Thu, 27 Aug 2015 10:00:46 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716407#comment-14716407
] 

ASF GitHub Bot commented on CLOUDSTACK-8762:
--------------------------------------------

GitHub user bhaisaab opened a pull request:

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

    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.yadav@shapeblue.com>

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

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

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

    https://github.com/apache/cloudstack/pull/753.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 #753
    
----
commit 758801ed47e3c98f673fba1bf0c1f294953b7840
Author: Rohit Yadav <rohit.yadav@shapeblue.com>
Date:   2015-08-27T09:58:54Z

    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.yadav@shapeblue.com>

----


> Check KVM disk files for activity before starting VM
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-8762
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8762
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.5.3, 4.6.0
>
>
> KVM hosts have real issue with fencing when storage are accessible by multiple hosts
such as in the case of NFS, in which case there is a possibility of qcow2 disks being accessed
by multiple hosts causing disk corruptions. The aim of this ticket is to explore ways to delay
starting a VM if the qcow2 disks/files are still being accessed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message