Maksim Malchuk 08b149a2fb Blacklist didn't work if running VirtualBox ...

This commit fixes blacklist procedure if running VirtualBox because with
version 5.0 of VirtualBox the 'virt-what' reports several hypervisors,
such as "virtualbox" and "kvm".

Change-Id: Ifba124c4c89fe08f573a56cdf71165309bfd5709
Partial-Bug: #1523526

2016-06-14 18:18:23 +03:00

..

boothook_centos.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

boothook_fuel_6.1_centos.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

boothook_fuel_6.1_ubuntu.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

boothook_fuel_7.0_centos.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

boothook_fuel_7.0_ubuntu.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

boothook_ubuntu.jinja2

Blacklist didn't work if running VirtualBox

2016-06-14 18:18:23 +03:00

cloud_config_centos.jinja2

Add processing of 'identity' parameter for mcollective config

2016-06-14 18:18:23 +03:00

cloud_config_ubuntu.jinja2

Add processing of 'identity' parameter for mcollective config

2016-06-14 18:18:23 +03:00

meta_data_centos.jinja2

Add versioning for cloud-init templates

2015-09-22 18:07:38 +03:00

meta_data_ubuntu.jinja2

Add versioning for cloud-init templates

2015-09-22 18:07:38 +03:00