This doesn't really answer the question but KVM can be used to migrate a VM 
from one process to another on a single compute host. I wonder if this is what 
you are seeing.

Will

From: Abhishek Talwar [mailto:[email protected]]
Sent: Tuesday, May 26, 2015 10:27 PM
To: Saju M
Cc: [email protected]
Subject: [Openstack-operators] #PERSONAL# Re: Can single node devstack 
OpenStack installation have VM migration

Hi Saju,

It is on KVM. I had tried on setting up a multinode environment with a 
controller, network and 2 compute nodes. But I am facing issues in that. 
Actually, one of the compute's is able to boot a VM and the VM goes to Active 
state. While on the other when I try to boot a VM it stay in scheduling state 
only. Also if I try to migrate the Active VM from 1 compute to other it gives 
me an error and the VM is left in error state.

So I thought of trying it on single-node kilo openstack, where I noticed that 
we have only 1 compute host in single-node setups but then also the VM gets 
migrated. So my question was where does the VM gets migrated when we don't have 
another compute host.

Regards
Abhishek

-----Saju M <[email protected]<mailto:[email protected]>> wrote: -----
To: Abhishek Talwar <[email protected]<mailto:[email protected]>>
From: Saju M <[email protected]<mailto:[email protected]>>
Date: 05/27/2015 10:43AM
Cc: 
[email protected]<mailto:[email protected]>,
 "Kris G. Lindgren" <[email protected]<mailto:[email protected]>>, 
David Medberry <[email protected]<mailto:[email protected]>>
Subject: Re: [Openstack-operators] Can single node devstack OpenStack 
installation have VM migration

Hi Abhishek,
Anyway, You are planning to work on VM migration. So it is better to setup 
multinode environment. Where is your single node setup ? Is it on KVM or 
Virtualbox VM?
On May 27, 2015 10:33 AM, "Abhishek Talwar" 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

But this link talks about only resizing in single node. I was talking about VM 
migration in single node ?

So how does this relates to VM migration ?

[email protected]<mailto:[email protected]> wrote: -----
To: "Kris G. Lindgren" <[email protected]<mailto:[email protected]>>
From: David Medberry
Sent by: [email protected]<mailto:[email protected]>
Date: 05/27/2015 10:22AM
Cc: Abhishek Talwar <[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>"
 
<[email protected]<mailto:[email protected]>>
Subject: Re: [Openstack-operators] Can single node devstack OpenStack 
installation have VM migration
Good info Kris. I've never used/modified that setting. I learn something (lots 
actually) every day.

On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren 
<[email protected]<mailto:[email protected]>> wrote:
I belive this can be possible by setting the allow_resize_same_host.  More 
details can be found here: http://www.madorn.com/resize-on-single-compute.html 
.  I believe the issue Dave is talking about is specifically targeting the same 
host for resize assuming the host can support it in a milti-node setup.  As 
getting the scheduler to choose the current host in the multihost setup is 95  
percent of the battle.

-------- Original message --------
From: David Medberry <[email protected]<mailto:[email protected]>>
Date: 05/26/2015 4:36 AM (GMT-08:00)
To: Abhishek Talwar <[email protected]<mailto:[email protected]>>
Cc: 
[email protected]<mailto:[email protected]>
Subject: Re: [Openstack-operators] Can single node devstack OpenStack 
installation have VM migration
No. Providing a mechanism for this is discussed from time to time, but it is 
not currently available.

All


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

_______________________________________________
OpenStack-operators mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to