Open Stack

Hi Naveed,

I don't think it's a good idea to suspend/pause. If you want to keep the
state of the VM then have a look at the live migration capabilities of KVM.
Our script is very simple and works for any VM without attached block
storage.

Here goes the little script. Keep in mind it's something very simple.

https://gist.github.com/diegoparrilla/6288e1521bffe741f71a

Regards
Diego



 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com <http://www.stackops.com/> | * diego.parrilla at stackops.com |
+34 91 005-2164 | skype:diegoparrilla




On Thu, May 22, 2014 at 8:36 AM, Naveed Ahmad <12msccsnahmad at seecs.edu.pk>wrote:

>
> Hi Diego ,
>
> Thanks for sharing steps for VM migration from customer end to your cloud.
> Well! i am not going to propose new idea for VM migration. I am using VM
> migration  for POC of my research idea.
>
> I have few question for you!
>
>
> 1. Can we use suspend/pause feature instead of snapshot for saving VM
> states. ?
> 2. How you are managing VM metadata (such as instance detail from
> nova,cinder database)
>
>
>
> Is it possible for you to share script? I need this VM migration feature
> in Openstack for POC only.
> Thanks again for your reply.
>
>
> Regards
> Naveed
>
>
>
>
> On Wed, May 21, 2014 at 10:47 PM, Diego Parrilla Santamaría <
> diego.parrilla.santamaria at gmail.com> wrote:
>
>> Hi Naveed,
>>
>> we have customers running VMs in their own Private Cloud that are
>> migrating to our new Public Cloud offering. To be honest I would love to
>> have a better way to do it, but this is how we do. We have developed a tiny
>> script that basically performs the following actions:
>>
>> 1) Take a snapshot of the VM from the source Private Cloud
>> 2) Halts the source VM (optional, but good for state consistency)
>>  3) Download the snapshot from source Private Cloud
>> 4) Upload the snapshot to target Public Cloud
>> 5) Start a new VM using the uploaded image in the target public cloud
>> 6) Allocate a floating IP and attach it to the VM
>> 7) Change DNS to point to the new floating IP
>> 8) Perform some cleanup processes (delete source VM, deallocate its
>> floating IP, delete snapshot from source...)
>>
>> A bit rudimentary, but it works if your VM does not have attached volumes
>> right away.
>>
>> Still, I would love to hear some sexy and direct way to do it.
>>
>> Regards
>> Diego
>>
>>  --
>> Diego Parrilla
>> <https://mailtrack.io/trace/link/660f588f5b8ce60a3da368dfbfeda30eb0548109>
>> *CEO*
>> *www.stackops.com
>> <https://mailtrack.io/trace/link/660f588f5b8ce60a3da368dfbfeda30eb0548109> | *
>>  diego.parrilla at stackops.com | +34 91 005-2164 | skype:diegoparrilla
>>
>>
>>
>>
>> On Wed, May 21, 2014 at 7:32 PM, Naveed Ahmad <12msccsnahmad at seecs.edu.pk
>> > wrote:
>>
>>>
>>> Hi community,
>>>
>>> I need some help from you people. Openstack provides Hot (Live) and Cold
>>> (Offline) migration between clusters/compute. However i am interested to
>>> migrate Virtual Machine from one OpenStack Cloud to another.  is it
>>> possible ?  It is inter cloud VM migration not inter cluster or compute.
>>>
>>> I need help and suggestion regarding VM migration. I tried to manually
>>> migrate VM from one OpenStack Cloud to another but no success yet.
>>>
>>> Please guide me!
>>>
>>> Regards
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://mailtrack.io/trace/link/86e76f2270da640047a3867c01c2cc077eb9a20c>
>>>
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140522/359510b0/attachment.html>