cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8841) Storage XenMotion from XS 6.2 to XS 6.5 fails.
Date Thu, 21 Apr 2016 10:21:25 GMT


ASF GitHub Bot commented on CLOUDSTACK-8841:

Github user sateesh-chodapuneedi commented on the pull request:
    >Purpose of doing this change is if some user intentionally want to do migration from
lower to higher then he can do it via API(from UI he can not do this). Other way around hypervisor
will not allow him.
    @priyankparihar Even if user intentionally tries to perform migration via API, ACS should
fail the attempt after checking for version check condition, rather than leaving this to hypervisor.
Construct the condition per hypervisor documentation and simply fail it with information/documentation
references, if required. 
    Also leaving it to hypervisor may be costlier, this being, storage migration task, is
an async job which increase async job count to be tracked/managed by management server and
also may involve multiple hypervisor API calls, even for failure cases. It's good to reduce
the jobs and API calls if the outcome is known definitively in advance. 

> Storage XenMotion from XS 6.2 to XS 6.5 fails.
> ----------------------------------------------
>                 Key: CLOUDSTACK-8841
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Priyank Parihar
> Storage XenMotion from XS 6.2 to XS 6.5 fails with error.

This message was sent by Atlassian JIRA

View raw message