Thank you Alireza and Carlos,
I will follow your hints when start to manipulate images. BTW how this
"storage cleanup" scripts can interfere the process?? What do they do ?
Vadim.
-----Original Message-----
From: create...@gmail.com [mailto:create...@gmail.com] On Behalf Of Carlos
Reategui
Sent: Wednesday, November 19, 2014 9:49 PM
To: users@cloudstack.apache.org; Alireza Eskandari
Subject: Re: VM migration to cloudstack
If cloud monkey can create an instance without starting it then maybe you can
try the following approach....
create instance matching your source VM, find disk image querying the DB and
replace it with that from your source VM.
I more or less did this manually with a handful of instances but you should be
able to automate it. In my case I was going from independent XenServer with
local storage to XenServer on CS with shared NFS storage so I had to export the
VMs as vhd. I was creating the new instances from the UI to match the OS of
the source VM and then stopping it. After stopping I would rename the vhd and
get rid of the old one. Worked like a charm.
You may need to disable the vhd/shared storage cleanup script that runs to
avoid any problems. Maybe create a few instances then stop CS before doing the
disk manipulation.
worth experimenting in a test environment.
On Wed, Nov 19, 2014 at 11:06 AM, Alireza Eskandari <
astro.alir...@yahoo.com.invalid> wrote:
> No, cloudmonkey is the CLI of CloudStack. You can automate jobs that
> CloudStack should do with it.
> For example you should find a way that take an image of your current
> VMs and put it in a place then CloudMonkey will get those images,
> register them as a template and create VMs from them. You can do
> CloudMonkey side jobs with a simple scripting but taking image from
> VMs depends on your type of hypervisor
>
> -------- Original message --------
> From: Vadim Kimlaychuk <vadim.kimlayc...@elion.ee>
> Date: 19/11/2014 21:55 (GMT+03:30)
> To: users@cloudstack.apache.org
> Subject: RE: VM migration to cloudstack
>
> Can cloudmonkey do this? If I need to register like 500 templates and
> then create VM from then it may take a lot of time.
>
> Vadim.
> ________________________________________
> From: Andrija Panic [andrija.pa...@gmail.com]
> Sent: Wednesday, November 19, 2014 18:48
> To: users@cloudstack.apache.org
> Subject: Re: VM migration to cloudstack
>
> Basicaly, convert existing vms to qcow2 or vhd or vmdk... upload
> template to ACS, deploy new VM from template...
>
> Not sure of other way ?
>
> Sent from Google Nexus 4
> On Nov 19, 2014 5:35 PM, "Vadim Kimlaychuk"
> <vadim.kimlayc...@elion.ee>
> wrote:
>
> > Hello,
> >
> > Hope this problem has already risen and been solved: have
> > VM-s running on stand-alone hypervisors (Xen, KVM, VmWare) and need
> > to "export-import" them into cloudstack. Are there any
> > instructions/tools to automate this process?
> >
> > Thanks,
> >
> > Vadim.
> >
>
