Remove cpu & memory from VMM conf files
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 3.6|
In the VMM configuration files /etc/one/vmm_exec/vmm_exec_*.conf admins can set CPU and MEMORY values.
These values are used by the drivers to call the hypervisor, but the opennebula VM definition is not updated.
This can be a problem for the accounting, because users can create VMs without the CPU or MEMORY attribute, and the core can't know the default values that the drivers used to fill them.
#2 Updated by Carlos Martín about 8 years ago
I forgot to mention that this also interfieres with the scheduler, because if one of CPU or MEMORY doesn't exist, the placement constraints are not checked. This means that the scheduler can send infinite number of VMs to the same host without looking at its free capacity.