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-4470) findHostsForMigration API is not setting 'requiresStorageMotion' flag wrongly
Date Fri, 23 Aug 2013 09:46:51 GMT

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

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

Commit 5b319ba0cb46160451ec05de32a8409b44a08f5b in branch refs/heads/4.2-forward from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b319ba ]

CLOUDSTACK-4470, findHostsForMigration api isn't setting the requiresStorageMotion flag to
true
when a virtual machine is to be migrated across cluster and the source and destination host
do
not share storage pools. migrationRequired flag was introduced in a recent commit that was
always
set to false for XenServer. This caused the destination host to be flaged as not requiring
storage motion. Fixed the scope of the boolean and defaulted it to true. Other checks validate
if storage motion is required for XenServer.

                
> findHostsForMigration API is not setting 'requiresStorageMotion'  flag wrongly 
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4470
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4470
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.1
>            Reporter: Srikanteswararao Talluri
>            Assignee: Devdeep Singh
>            Priority: Blocker
>             Fix For: 4.2.1
>
>
> Steps to reproduce:
> ===============
> 1. have two xenserver6.1 clusters in the same zone with at least one host in each cluster.
> 2. deploy a VM.
> 3. issue findHostsForMigration API for that virtual machine
> 4. it needs to mark 'requiresStorageMotion' to true if the destination host is in a different
cluster.
> Observation:
> ===========
>  findHostsForMigration  result contains 'requiresStorageMotion' set to false for all
the hosts, which is wrong.
> http://10.147.38.166:8080/client/api?command=findHostsForMigration&VirtualMachineId=e62fc701-e6d0-4684-af23-24b0b6ccb0a3&sessionkey=DoTkY30m%2BPsRPfmt6vBah0imvoQ%3D&_=1377237882534
> <findhostsformigrationresponse cloud-stack-version="4.2.0-SNAPSHOT">
> <count>2</count>
> <host>
> <id>3a2a855b-f872-431f-b0d5-1a84f96e166d</id>
> <name>Rack1Pod1Host15</name>
> <state>Up</state>
> <disconnected>2013-08-23T02:40:08+0530</disconnected>
> <type>Routing</type>
> <ipaddress>10.147.40.15</ipaddress>
> <zoneid>5f94a329-6dcc-4657-9071-ff1e548871b4</zoneid>
> <zonename>Sandbox-XenServer</zonename>
> <podid>e0a82c4a-a817-4e27-b710-72eec5a467e8</podid>
> <podname>POD0</podname>
> <version>4.2.0-SNAPSHOT</version>
> <hypervisor>XenServer</hypervisor>
> <cpunumber>4</cpunumber>
> <cpuspeed>2394</cpuspeed>
> <cpuallocated>33.42%</cpuallocated>
> <cpuused>0.05%</cpuused>
> <cpuwithoverprovisioning>9576.0</cpuwithoverprovisioning>
> <networkkbsread>9207</networkkbsread>
> <networkkbswrite>15695</networkkbswrite>
> <memorytotal>16190157312</memorytotal>
> <memoryallocated>536870912</memoryallocated>
> <memoryused>1214196</memoryused>
> <capabilities>
> xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , hvm-3.0-x86_32p , hvm-3.0-x86_64
> </capabilities>
> <lastpinged>1970-01-16T19:05:27+0530</lastpinged>
> <managementserverid>7566222426160</managementserverid>
> <clusterid>9405d5ab-7f85-4098-bedd-e3ee6c5e8b14</clusterid>
> <clustername>C0</clustername>
> <clustertype>CloudManaged</clustertype>
> <islocalstorageactive>false</islocalstorageactive>
> <created>2013-08-23T02:27:58+0530</created>
> <events>
> PingTimeout; ManagementServerDown; AgentDisconnected; HostDown; ShutdownRequested; Remove;
StartAgentRebalance; AgentConnected; Ping
> </events>
> <suitableformigration>true</suitableformigration>
> <requiresStorageMotion>false</requiresStorageMotion>
> <resourcestate>Enabled</resourcestate>
> <hypervisorversion>6.1.0</hypervisorversion>
> <hahost>false</hahost>
> <jobstatus>0</jobstatus>
> </host>
> <host>
> <id>b09c5bc4-c134-4c69-addc-328af9a2fc48</id>
> <name>Rack1Pod1Host31</name>
> <state>Up</state>
> <type>Routing</type>
> <ipaddress>10.147.40.31</ipaddress>
> <zoneid>5f94a329-6dcc-4657-9071-ff1e548871b4</zoneid>
> <zonename>Sandbox-XenServer</zonename>
> <podid>e0a82c4a-a817-4e27-b710-72eec5a467e8</podid>
> <podname>POD0</podname>
> <version>4.2.0-SNAPSHOT</version>
> <hypervisor>XenServer</hypervisor>
> <cpunumber>4</cpunumber>
> <cpuspeed>2394</cpuspeed>
> <cpuallocated>0%</cpuallocated>
> <cpuused>0.06%</cpuused>
> <cpuwithoverprovisioning>9576.0</cpuwithoverprovisioning>
> <networkkbsread>5127</networkkbsread>
> <networkkbswrite>19389</networkkbswrite>
> <memorytotal>16190133120</memorytotal>
> <memoryallocated>1476395008</memoryallocated>
> <memoryused>2599168</memoryused>
> <capabilities>
> xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , hvm-3.0-x86_32p , hvm-3.0-x86_64
> </capabilities>
> <lastpinged>1970-01-16T19:06:14+0530</lastpinged>
> <managementserverid>7566222426160</managementserverid>
> <clusterid>698cfcac-519d-40c9-b212-26345676fceb</clusterid>
> <clustername>cluster1</clustername>
> <clustertype>CloudManaged</clustertype>
> <islocalstorageactive>false</islocalstorageactive>
> <created>2013-08-23T16:05:14+0530</created>
> <events>
> PingTimeout; ManagementServerDown; AgentDisconnected; HostDown; ShutdownRequested; Remove;
StartAgentRebalance; AgentConnected; Ping
> </events>
> <suitableformigration>true</suitableformigration>
> <requiresStorageMotion>false</requiresStorageMotion>
> <resourcestate>Enabled</resourcestate>
> <hypervisorversion>6.1.0</hypervisorversion>
> <hahost>false</hahost>
> <jobstatus>0</jobstatus>
> </host>
> </findhostsformigrationresponse>

--
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