Feature #1284

Remove cpu & memory from VMM conf files

Added by Carlos Martín about 9 years ago. Updated about 9 years ago.

Status:ClosedStart date:05/21/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 3.6
Resolution:fixed Pull request:

Description

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.

Associated revisions

Revision 0875bef8
Added by Ruben S. Montero about 9 years ago

feature #1288 #1284: Memory and CPU are now mandatory for VMs. Default values have been removed from the driver configuration files

History

#1 Updated by Ruben S. Montero about 9 years ago

  • Category set to Core & System
  • Assignee set to Ruben S. Montero
  • Target version set to Release 3.8

#2 Updated by Carlos Martín about 9 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.

#3 Updated by Ruben S. Montero about 9 years ago

  • Target version changed from Release 3.8 to Release 3.6

#4 Updated by Ruben S. Montero about 9 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF