We had a Hyper-V based environment previously so the migration to OpenStack was made easier by having Hyper-V also in the cloud.
We also find this avoids a set of driver issues and gives us a single vendor stack when we are reporting problems. It's good to make sure we keep the correct architecture that the hypervisor is not 'hardcoded' into the infrastructure. Downside is some additional packaging work but Puppet looks after most of the configuration. In addition, we currently only have volumes with ceph on the KVM base since there is no ceph driver for Windows We've around 200 Hyper-V hypervisors but the majority (about 3,200) are on KVM. Tim From: Maish Saidel-Keesing [mailto:[email protected]] Sent: 19 March 2015 08:19 To: [email protected] Subject: Re: [Openstack-operators] Hypervisor decision That is interesting Tim. Why Hyper-V if I may ask? Why not stick just with KVM? Maish On 19/03/15 08:22, Tim Bell wrote: At CERN, we run KVM and Hyper-V. Both work fine. Depending on the size of your cluster, you may have other factors to consider such as monitoring and configuration management. We use Puppet to configure both environnments. Images are tagged with a property hypervisor_type which is used to schedule workloads to the appropriate hypervisor. Tim From: matt [mailto:[email protected]] Sent: 18 March 2015 23:24 To: Abel Lopez Cc: [email protected]<mailto:[email protected]> Subject: Re: [Openstack-operators] Hypervisor decision most openstack environments at kvm, so if you want to stick with the herd, that's the way to go. On Wed, Mar 18, 2015 at 5:53 PM, Abel Lopez <[email protected]<mailto:[email protected]>> wrote: Interesting topic, since you're already running Hyper-v and ESX, I'm inferring that your workload is heavy on windows VMs. If you're doing majority windows, and minority linux, stick with hyper-v. The benchmarks I've read show that windows VMs run fastest on hyper-v VS all others. If you expect an even split, it might make sense to create Host Aggregates of various hypervisiors like hyper-v and KVM, and utilize extra-specs in the flavors and guest images to aid in scheduling, for example "Windows images launch on the hyper-v pool" > On Mar 18, 2015, at 2:41 PM, Vytenis Silgalis > <[email protected]<mailto:[email protected]>> wrote: > > Hello, > > I'm looking to champion openstack at my company, we currently run both a > small hyper-v cluster and 3 VMware clusters. However we are not married to > any specific hypervisor. What I'm looking for is recommendations for which > hypervisor we should look at for our openstack environments and the > pros/con's people have run into with the various hypervisors supported by > openstack. > > > Thanks, > Vytenis > _______________________________________________ > OpenStack-operators mailing list > [email protected]<mailto:[email protected]> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Best Regards, Maish Saidel-Keesing
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
