You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jake (JIRA)" <ji...@apache.org> on 2013/04/12 08:01:20 UTC
[jira] [Created] (CLOUDSTACK-2016) CS Migration wizard for existing
VM in vCenter Cluster or host
Jake created CLOUDSTACK-2016:
--------------------------------
Summary: CS Migration wizard for existing VM in vCenter Cluster or host
Key: CLOUDSTACK-2016
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2016
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: API, Management Server, UI, VMware
Affects Versions: Future
Environment: VMware vCenter 5.X , ESXi 5.X Hosts, Cloudstack 4.X
Reporter: Jake
Hi All,
The existing migration method for existing VMware VMs is not realistic. Currently existing VMs on a VMware host require exporting as an OVF/OVA, then importing into Cloudstack as a template, then deploying within CS again. This method is also unstable as many migrations fail with a BSoD or Kernal Panic.
If this is the only way to migrate then Cloudstack is going to have a big problem trying to get people with large existing infrastructures to switch over to Cloudstack.
I would like to request a feature/method that would allow for a streamlined migration process. I believe this will increase adoption by small, medium and Enterprise class businesses tremendously.
I would like to see Cloudstack, through a GUI Based wizard (prefered) or at least CLI/API scripting process which can look at attached vCenter cluster or host for existing VMs and perform the following.
1. Lists Existing VMs on a Cloudstack attached vCenter cluster or host.
2. Allow admin to select the VMs they want to migrate into cloudstack zone and assign each vm to a user or group account in Cloudstack.
-Click migrate button
-Two possible processes below-
3.a A process starts to snapshot the existing server, renames and copies the VM files to Cloudstack format and places in CS primary storage. Continue to #4
-or-
3.b A process starts that initiates Storage vMotion on the existing server, renames the VM files to Cloustack format and places in CS primary storage. Continue to #4
4. Cloudstack then updates its database to reflect the new inventory.
I am sure my process is missing a bunch of things, but in general this should be possible I think.
I wish I was a programmer so I could help with this.
Thank you very much!
--
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