<div dir="ltr">I was under the impression hyper-v didn't charge a per seat license on non windows instances?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 19, 2015 at 12:05 PM, Fox, Kevin M <span dir="ltr"><<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF">
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">So, in the pets vs cattle cloud philosophy, you want to be able to have as many cattle as you need, rather then limit the sets to a smaller number of more pet like things.<br>
<br>
kvm allows unlimited numbers of vm's, which is very cloudy. but due to Windows licensing, tends to only work well with linux/bsd VM's.<br>
<br>
Windows is a whole nother kettle of fish. They either license it per vm, which is very pet like, or alternately, the more cattle friendly way is to buy a DataCenter* version of windows.<br>
<br>
Each hypervisor needs to be the DataCenter version, but it allows you to run unlimited Windows VM's on that hypervisor. So if you want to run lots of windows cattle, its can be the way to go.<br>
<br>
Due to its high cost, it does not usually make sense to run all your linux vm's on Windows DataCenter version, so you run both kvm for linux/bsd vm's and Windows DataCenter licensed hyperv for windows vm's.<br>
<br>
* <a href="http://www.microsoft.com/licensing/about-licensing/virtualization.aspx" target="_blank">http://www.microsoft.com/licensing/about-licensing/virtualization.aspx</a><br>
<br>
Thanks,<br>
Kevin<br>
<div style="font-family:Times New Roman;color:#000000;font-size:16px">
<hr>
<div style="direction:ltr"><font face="Tahoma" color="#000000"><b>From:</b> Maish Saidel-Keesing [<a href="mailto:maishsk@maishsk.com" target="_blank">maishsk@maishsk.com</a>]<br>
<b>Sent:</b> Thursday, March 19, 2015 12:19 AM<br>
<b>To:</b> <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.openstack.org</a><div><div class="h5"><br>
<b>Subject:</b> Re: [Openstack-operators] Hypervisor decision<br>
</div></div></font><br>
</div><div><div class="h5">
<div></div>
<div>That is interesting Tim.<br>
<br>
Why Hyper-V if I may ask? Why not stick just with KVM?<br>
<br>
Maish<br>
<br>
<div>On 19/03/15 08:22, Tim Bell wrote:<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">At CERN, we run KVM and Hyper-V. Both work fine.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">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.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Images are tagged with a property hypervisor_type which is used to schedule workloads to the appropriate hypervisor.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Tim</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> matt [<a href="mailto:matt@nycresistor.com" target="_blank">mailto:matt@nycresistor.com</a>]
<br>
<b>Sent:</b> 18 March 2015 23:24<br>
<b>To:</b> Abel Lopez<br>
<b>Cc:</b> <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">
openstack-operators@lists.openstack.org</a><br>
<b>Subject:</b> Re: [Openstack-operators] Hypervisor decision</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">most openstack environments at kvm, so if you want to stick with the herd, that's the way to go.</p>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Wed, Mar 18, 2015 at 5:53 PM, Abel Lopez <<a href="mailto:alopgeek@gmail.com" target="_blank">alopgeek@gmail.com</a>> wrote:</p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Interesting topic, since you're already running Hyper-v and ESX, I'm inferring that your workload is heavy on windows VMs.<br>
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.<br>
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"</p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
> On Mar 18, 2015, at 2:41 PM, Vytenis Silgalis <<a href="mailto:vsilgalis@outlook.com" target="_blank">vsilgalis@outlook.com</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> 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.<br>
><br>
><br>
> Thanks,<br>
> Vytenis<br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></p>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
<br>
<fieldset></fieldset> <br>
<pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
<div>-- <br>
Best Regards, Maish Saidel-Keesing</div>
</div>
</div></div></div>
</div>
</div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>