Fuel UI should not allow to deploy Murano and Sahara on environments with QEMU hypervisor

[Timur Nurlygayanov]

Here is the many "bugs" about random fails of Murano and Sahara OSTF tests [1], which failed on some virtual environments with QEMU hypervisor for VMs in OpenStack cloud.
In fact, Murano and Sahara were designed to deploy many VMs and run some tasks with high load on these VMs and these components require good performance of OpenStack compute nodes.
When we deploy some environments with QEMU hepervisor we can see some random fails because we will have worse performance of VMs in this cloud.

The main use case for Murano and Sahara is to work in large clusters with the high performance compute nodes, we don't want to support cases for small environments where VMs with Ubuntu can boot more than 10 minutes.

Steps To Reproduce:
1. Create new environment and select QEMU hepervisor, "install Murano and Sahara".
2. Deploy environment
3. Run Platform OSTF tests for Murano and Sahara

Observed Results:
User can deploy environments with QEMU, Murano and Sahara. In fact, Murano and Sahara will be not functional (only basic functionality will be available) and deployment will fail randomly with timeouts.

Expected Results:
It should be not possible to deploy Murano and Sahara on environments with QEMU hypervisor.

[1]
https://bugs.launchpad.net/fuel/+bug/1463354
https://bugs.launchpad.net/fuel/+bug/1467185

[Anastasia Palkina (apalkina)]

Verified on ISO #15

"build_id": "2015-06-24_16-12-23", "build_number": "15", "release_versions": {"2014.2.2-7.0": {"VERSION": {"build_id": "2015-06-24_16-12-23", "build_number": "15", "api": "1.0", "fuel-library_sha": "7d19bc3783177aebf64fa4c2ae20d845cbd5348f", "nailgun_sha": "b74f847ec89c4bff1addb830704206dc503125f0", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-7.0", "production": "docker", "python-fuelclient_sha": "1b8574a7c4ea884862763a15c636b066d51f49e7", "astute_sha": "776157f722b13aff5f59bc098cf948793e6498ef", "fuel-ostf_sha": "69e7fa120e8efa7ed74d98efc63079d2f5c69d7b", "release": "7.0", "fuelmain_sha": "3b866d2ff3091a60362327028085fa62fd16c5a0"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "7d19bc3783177aebf64fa4c2ae20d845cbd5348f", "nailgun_sha": "b74f847ec89c4bff1addb830704206dc503125f0", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-7.0", "production": "docker", "python-fuelclient_sha": "1b8574a7c4ea884862763a15c636b066d51f49e7", "astute_sha": "776157f722b13aff5f59bc098cf948793e6498ef", "fuel-ostf_sha": "69e7fa120e8efa7ed74d98efc63079d2f5c69d7b", "release": "7.0", "fuelmain_sha": "3b866d2ff3091a60362327028085fa62fd16c5a0"

[Denis Egorenko (degorenko)]

This bug is invalid, because all "bugs" related to using VirtualBox or not enough hardware resources. But in fact, Sahara and Murano will work with QEMU hypervisor fine with enough resources. Also, we can use QEMU hypervisor on real hardware, but this bug doesn't allow to do this. And it's wrong.

[Sergey Reshetnyak (sreshetniak)]

Agree with Denis. Also I don't understand why Sahara team have not been notified about this change.

[Yaroslav Lobankov (ylobankov)]

I agree with guys. QEMU hypervisor shouldn't block users to use Sahara.