The only issues I've run into are that you can only have one vCenter Datacenter per zone, and that if you're separating the guest and public traffic on different NICs that you take care to ensure the respective vSphere and KVM network labels are correct. If you need this last part and don't do it, you're going to have difficulty communicating between VMs running on the different hypervisors.
-tim On Fri, May 2, 2014 at 2:04 PM, Willard Rathjen <[email protected] > wrote: > It’s not an issue. You need to bring them in as different clusters. Any > templates will need to be create for each hypervisor type, but other than > that, it will work well. > > Willard Rathjen > Cloud Systems Engineer > > Office +1.800.735.7104 | Direct +1.515.612.7813 > [email protected] | www.appcore.com > > ---------------------------------------------------------------------- > The information in this message is intended for the named recipients only. > It may contain information that is privileged, confidential or otherwise > protected from disclosure. If you are not the intended recipient, you are > hereby notified that any disclosure, copying, distribution, or the taking > of any action in reliance on the contents of this message is strictly > prohibited. If you have received this e-mail in error, do not print it or > disseminate it or its contents. In such event, please notify the sender by > return e-mail and delete the e-mail file immediately thereafter. Thank you. > > > > On May 2, 2014, at 12:44 PM, Jeff Barnett <[email protected]> wrote: > > > I was thinking of giving Cloudstack a try; I wanted to know if you could > use ESXi and KVM host in the same CloudStack zone, and what that looks like. > >
