Open Stack

According to Andrew Woodward (xarses), this is the current implementation.


-----Original Message-----
From: Igor Kalnitsky [mailto:ikalnitsky at mirantis.com]
Sent: Monday, December 21, 2015 8:23 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt
on Wizard

> Qemu is not a hypervisor This will be even more confusing.

It looks like hypervisor much more than libvirt. Moreover, according to
Wikipedia [1] (don't blame me guys) Qemu is Type-2 hypervisor.

[1] https://en.wikipedia.org/wiki/Hypervisor

> Today, when a user selects KVM, Fuel attempts to use KVM acceleration
> and defaults to QEMU in the case that KVM acceleration is not possible.

Sheena, are you sure it works this way? Some time ago we didn't support
this. However, I fully support this idea and believe this is the way to
go. In this case the hypervisor entry could be called something like
"Qemu (+ KVM if available)".


On Mon, Dec 21, 2015 at 4:04 PM, Sheena Gregson <sgregson at mirantis.com>
wrote:
> We should collapse this into one entry - I don't have any preference
> on the naming convention, but as Fuel checks to see whether the
> hardware is capable of performing KVM acceleration, there's no reason
> to continue giving a selection to the user regarding KVM.
>
> Today, when a user selects KVM, Fuel attempts to use KVM acceleration
> and defaults to QEMU in the case that KVM acceleration is not
> possible.  We should keep this behavior and make the entry a single
> KVM/QEMU selection to eliminate the false perception of choice (and
> the ability for users to select the incorrect option).
>
> -----Original Message-----
> From: Bob Ball [mailto:bob.ball at citrix.com]
> Sent: Monday, December 21, 2015 7:32 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave
> Libvirt on Wizard
>
>> On Mon, Dec 21, 2015 at 1:43 PM, Igor Kalnitsky
>> <ikalnitsky at mirantis.com>
>> wrote:
>> > What about hypervisor "Qemu", and checkbox option on Settings tab -
>> > "Use KVM extension"?
>> Qemu is not a hypervisor This will be even more confusing.
>> I think "Libvirt" + some tooltip which says "Qemu and KVM" will be ok.
>
> Libvirt isn't a hypervisor either.  Note that Xen, Virtuozzo CT,
> Virtuozzo VM, LXC and KVM on ppc64 and s390x are all valid hypervisors
> to use with Libvirt and OpenStack (taken from
> http://docs.openstack.org/developer/nova/support-matrix.html)
>
> Bob
>
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev