Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: wilderrodrigues <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-541-cloudstack@git.apache.org>
In-Reply-To: <git-pr-541-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate
 volume...
Content-Type: text/plain
Message-Id: <20150701075959.0817CDFBCA@git1-us-west.apache.org>
Date: Wed,  1 Jul 2015 07:59:59 +0000 (UTC)

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/541#issuecomment-117517309
  
    Hi @likitha 
    
    I understood what the issue says, but what I really meant concerns what the code does.
    
    The only practical change in the code was this:
    
    if (volume.getHypervisorType() == Hypervisor.HypervisorType.Hyperv || volume.getHypervisorType() == Hypervisor.HypervisorType.VMware) {
    ...
    }
    
    Which means that now it will also get in the IF when the Hypervisor is of HypervisorType.VMware type.
    
    So, what you really want is: support volume migration from zone-wide to cluster-wide storage when hypervisor is VMware.
    
    Is that correct?
    
    If you look further at the code, when CS will do DELETEVOLUME, it would take into account only VMware. So, HyperV wouldn't be supported.
    
    ![image](https://cloud.githubusercontent.com/assets/5129209/8450115/dc04f71c-1fd7-11e5-8cbc-127d4030ce73.png)
    
    Cheers,
    Wilder


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---