cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4047) [sM][VMWare][ZWPS]: no need of storage migration while migrating VM when the root volume is on zone wide primary storage
Date Wed, 07 Aug 2013 01:38:47 GMT

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

ASF subversion and git services commented on CLOUDSTACK-4047:
-------------------------------------------------------------

Commit c14c736d7afbfa53fe0fdf2ad5d73860343fa75f in branch refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c14c736 ]

CLOUDSTACK-4047 [sM][VMWare][ZWPS]: no need of storage migration while migrating VM when the
root volume is on zone wide primary storage

Introduced check for zone wide pools while listing hosts for migration.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>

                
> [sM][VMWare][ZWPS]: no need of storage migration while migrating VM when the root volume
is on zone wide primary storage 
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4047
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4047
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>         Environment: VMWARE, zone wide primary storage
>            Reporter: Srikanteswararao Talluri
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> ==============
> 1. On a VMWare deployment with only zone wide primary storage, Issue findhostsformigration
API
> It marks the isstoragemotionrequired=true in the findHostsForMigration API response thought
storagemigration is not required. when you actually use UI to migrate VM it 
> { "findhostsformigrationresponse" : { "count":1 ,"host" : [  {"id":"668f9bcc-a645-4a64-96d2-b19c885448b9","name":"10.147.40.21","state":"Up","type":"Routing","ipaddress":"10.147.40.21","zoneid":"c78cbdfb-d138-4950-9af8-db478b60a3fb","zonename":"sm","podid":"0d491fa6-cb78-4964-bd22-de0793a47029","podname":"pod","version":"4.2.0-SNAPSHOT","hypervisor":"VMware","cpunumber":4,"cpuspeed":2394,"cpuallocated":"0%","cpuused":"0.23%","cpuwithoverprovisioning":"9576.0","networkkbsread":0,"networkkbswrite":0,"memorytotal":17169539072,"memoryallocated":0,"memoryused":1099928,"capabilities":"hvm","lastpinged":"1970-01-16T18:37:03+0530","managementserverid":7363452993625,"clusterid":"ab7f3e99-f3e3-4c27-ac24-39f20f8fa262","clustername":"10.147.60.13/sm/smclus1","clustertype":"ExternalManaged","islocalstorageactive":false,"created":"2013-08-02T21:57:07+0530","events":"HostDown;
Remove; ManagementServerDown; ShutdownRequested; AgentDisconnected; Ping; PingTimeout; AgentConnected;
StartAgentRebalance","suitableformigration":true,"requiresStorageMotion":true,"resourcestate":"Enabled","hypervisorversion":"5.1","hahost":false,"jobstatus":0}
] } 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message