Automatic default selection of virtualization type depending on bootstrap data

Registered by Andrey Korolyov on 2013-11-22

Fuel environments may contain nodes with different virtualization type. It is already possible case, though not really practical one, when we can have multiple nodes with kvm, and multiple with qemu only available. For further partners integrations we may have more virtualization types, for example xen or esx.

Consequently, we need to have:
a) automatic determination of hypervisor type for node where possible. However it is likely that we need to leave an ability to specify another type if needed
b) force user to choose virtualization type for node where it has not been detected automatically for some reason
c) We need to add an ability to group nodes by virtualization type
d) user should be able to set virt type for group of nodes, not only one-by-one
e) if both qemu and kvm are available, it should be kvm by default

Status can be taken from 'grep -Eq 'svm|vmx' /proc/cpuinfo ; echo $?'

Blueprint information

Status:
Not started
Approver:
Mike Scherbakov
Priority:
Medium
Drafter:
Vitaly Kramskikh
Direction:
Approved
Assignee:
Vitaly Kramskikh
Definition:
New
Series goal:
Accepted for future
Implementation:
Not started
Milestone target:
milestone icon next

Whiteboard

I think there could be a few such parameters. We already have kernel parameters that could be different for any node. I think we need a flag in settings sections of openstack.yaml which says whether or not the settings should present in node-specific configiuration

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.