I haven't tried it yet but may be forced to in the not so distant future for a internal group who bought a bunch of ESXi hosts and didn't buy vSphear server because they were confused by the fact that they use the same client and thought vSphear was included. So I did a little research on the subject. Not I haven't tested it yet Yes there is support for using ESXi as a compute node however it looks like you need a VM or an other external host to act as a proxy for each ESXi host unless VMWare has created an install package, I'm not sure if they have or not. The reason for this is it manages the ESXi host via the CIM based vSphear API's . The reason VMWare created it is to prevent themselves from being completely pushed out of the lucrative cloud hosting market. As for using it for migration I don't think it will work too well unless you somehow managed to figure out a way to shoehorn your existing VMs into Novas database <div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my HP Pre3</div> <hr align="left" style="width:75%">On Mar 6, 2013 3:50 PM, Keith Basil <kbasil@redhat.com> wrote: > Sorry, I am, obviously, not one of the *intended* recipients of such a > question. > > Having seen it, though, I must confess I was puzzled, at first... > > My familiarity with VMware's contribution to OpenStack is minimal. > Especially when it comes down to the Core OpenStack Components. We do > know, however, that ESX is a supported hypervisor. > > This does mean we can have have Compute Nodes running ESX while all the > control infrastructure and other Core Components would be RHOS. We can, > of course, go as far as to admit all the non-physical nodes to be > running as VMware VMs. > > Can anyone tell me what the business case could be, for such a setup ? > Besides the very valid one "that's what the client wants" ! Not sure if there is a business case to be made here. If this is requested, I would like to understand the rationale behind it? Does the customer think that because the hypervisor is VMware based that they will get HA and vMotion-like benefits with OpenStack? Are they erroneously mixing and matching cloud types (enterprise virtualization vs. an elastic cloud)? > Never mind, I just figured it out... What if you had a bunch of VMware > infrastructure and wanted to try things out before jumping in ? Besides, > this could smooth-out the transition to a mixed environment. Chances are > the client will be more at-ease with a smooth transition. As a proof of concept, maybe. As production infrastructure, probably not for many reasons. My guess is that it's a philosophical misunderstanding of the nature of the two cloud types: one designed for virtualization, static/legacy workloads, etc (VMware) and one designed for new elastic applications where the apps *expect* the infrastructure to fail (OpenStack). -k -- keith basil | principal product manager, OpenStack kbasil@redhat.com | redhat.com/openstack 757-769-8674 (m) | 978-813-1323 (o) skype/twitter/github/irc, life: noslzzp _______________________________________________ rhos-list mailing list rhos-list@redhat.com https://www.redhat.com/mailman/listinfo/rhos-list