When you say convert, I'm not certain whats implied. You may have to make it more streamlined (create several templates and install apps on top), unless you want to manage many templates and convert each VM as template to be imported into CS.
You can certainly tie your existing VC with CS. CS will only manage what it deployed. Meaning if you have other VMs that you deployed independent of CloudStack, they will run on their own and CS wont know about them. It would be cleaner to have a separate vSphere cluster, but in my opinion it's not a hard requirement - I've yet to see an issue. If you properly spec out your virtual infrastructure, I don't believe there is going to be issues. I run my non prod environments with CloudStack but its not solely dedicated for CS only and other platforms used it as well. To make an example: 1 VC, manages about 32 hypervisors, 6 clusters and 1000 VMs. I have had no issues with vSphere 5 and CS 4.1 (custom build to support DVS). My prod environment will have a dedicate cluster for cloudstack, but I will still use the same virtual center that will manage other non CS managed clusters. Its all about your design and if you properly spec your environment. Regards ilya -----Original Message----- From: venkatesh.a [mailto:venkates...@dmxtechnologies.com] Sent: Monday, March 25, 2013 9:51 AM To: users@cloudstack.apache.org Subject: Porting VMWare virtual setup into CloudStack Hi How can I convert existing VMWare virtual setup to CloudStack. Is it possible port ? Thanks and Regards Venkatesh.A
