<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Cambria",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">+1 as well – this makes intuitive sense to me as a user, we should include something in the mouseover text explaining that KVM acceleration will be used if possible based on hardware capabilities</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vladimir Kuklin [mailto:<a href="mailto:vkuklin@mirantis.com">vkuklin@mirantis.com</a>] <br><b>Sent:</b> Monday, December 21, 2015 9:35 AM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">+1 to Andrey</p></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Mon, Dec 21, 2015 at 6:12 PM, Andrey Danin <<a href="mailto:adanin@mirantis.com" target="_blank">adanin@mirantis.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">I suggest to call this item in the Wizard as "QEMU-KVM" with the following description:<br>"Select this option if you want to use QEMU as a hypervisor with capability of KVM acceleration."</p></div><div><div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Mon, Dec 21, 2015 at 5:22 PM, Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><p class="MsoNormal">> Qemu is not a hypervisor This will be even more confusing.<br><br>It looks like hypervisor much more than libvirt. Moreover, according<br>to Wikipedia [1] (don't blame me guys) Qemu is Type-2 hypervisor.<br><br>[1] <a href="https://en.wikipedia.org/wiki/Hypervisor" target="_blank">https://en.wikipedia.org/wiki/Hypervisor</a><br><br>> Today, when a user selects KVM, Fuel attempts to use KVM acceleration and<br>> defaults to QEMU in the case that KVM acceleration is not possible.<br><br>Sheena, are you sure it works this way? Some time ago we didn't<br>support this. However, I fully support this idea and believe this is<br>the way to go. In this case the hypervisor entry could be called<br>something like "Qemu (+ KVM if available)".</p><div><div><p class="MsoNormal"><br><br>On Mon, Dec 21, 2015 at 4:04 PM, Sheena Gregson <<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>> wrote:<br>> We should collapse this into one entry - I don't have any preference on<br>> the naming convention, but as Fuel checks to see whether the hardware is<br>> capable of performing KVM acceleration, there's no reason to continue<br>> giving a selection to the user regarding KVM.<br>><br>> Today, when a user selects KVM, Fuel attempts to use KVM acceleration and<br>> defaults to QEMU in the case that KVM acceleration is not possible. We<br>> should keep this behavior and make the entry a single KVM/QEMU selection<br>> to eliminate the false perception of choice (and the ability for users to<br>> select the incorrect option).<br>><br>> -----Original Message-----<br>> From: Bob Ball [mailto:<a href="mailto:bob.ball@citrix.com" target="_blank">bob.ball@citrix.com</a>]<br>> Sent: Monday, December 21, 2015 7:32 AM<br>> To: OpenStack Development Mailing List (not for usage questions)<br>> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>> Subject: Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt<br>> on Wizard<br>><br>>> On Mon, Dec 21, 2015 at 1:43 PM, Igor Kalnitsky<br>>> <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>><br>>> wrote:<br>>> > What about hypervisor "Qemu", and checkbox option on Settings tab -<br>>> > "Use KVM extension"?<br>>> Qemu is not a hypervisor This will be even more confusing.<br>>> I think "Libvirt" + some tooltip which says "Qemu and KVM" will be ok.<br>><br>> Libvirt isn't a hypervisor either. Note that Xen, Virtuozzo CT, Virtuozzo<br>> VM, LXC and KVM on ppc64 and s390x are all valid hypervisors to use with<br>> Libvirt and OpenStack (taken from<br>> <a href="http://docs.openstack.org/developer/nova/support-matrix.html" target="_blank">http://docs.openstack.org/developer/nova/support-matrix.html</a>)<br>><br>> Bob<br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></p></div></div></blockquote></div><p class="MsoNormal"><br><br clear="all"></p></div></div><p class="MsoNormal">-- </p><div><p class="MsoNormal">Andrey Danin<br><a href="mailto:adanin@mirantis.com" target="_blank">adanin@mirantis.com</a><br>skype: gcon.monolake</p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></p></blockquote></div><p class="MsoNormal"><br><br clear="all"></p><div><p class="MsoNormal"> </p></div><p class="MsoNormal">-- </p><div><div><div><div><p class="MsoNormal">Yours Faithfully,<br>Vladimir Kuklin,<br>Fuel Library Tech Lead,<br>Mirantis, Inc.<br>+7 (495) 640-49-04<br>+7 (926) 702-39-68<br>Skype kuklinvv<br>35bk3, Vorontsovskaya Str.<br>Moscow, Russia,<br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.com</a><br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.ru</a><br><a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></p></div></div></div></div></div></div></body></html>