Feature #1798

optionally limit the resources exposed by a host

Added by Karanbir Singh over 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:03/08/2013
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Scheduler
Target version:Release 4.6
Resolution:fixed Pull request:

Description

In some cases, its valuable to be able to limit the resources opennebula uses from a specific host. It should be possible to control that, either at host create time or update time. This might include
  • RAM ( eg. use only 16GiB from a host that has 32GiB )
  • CPU core count ( eg. use only 8 cores from a machine that has 16 )
  • network with the dummy driver ( eg. only use br0 and br1, but not br2 on this host ).

Related issues

Related to Feature #1847: Overcommitment at the cluster level Closed 04/01/2013
Related to Feature #1849: HYPERVISOR_MEM as an amount rather than percentage. Closed 04/01/2013

Associated revisions

Revision 7577d6d6
Added by Ruben S. Montero over 5 years ago

feature #1798: Optionally reserve capacity from a host. Cluster defaults can be defined

Revision f8977e26
Added by Ruben S. Montero over 5 years ago

feature #1798: Get rid of HYPERVISOR_MEM as resources can be now limited host or cluster-wise

Revision 330b6376
Added by Ruben S. Montero over 5 years ago

feature #1798: always show RESERVED attributes in Host and Cluster templates

Revision 444b5bf8
Added by Carlos Martín over 5 years ago

Feature #1798: Add host reserved_cpu/mem attributes each monitoring step

History

#1 Updated by Ruben S. Montero over 6 years ago

  • Category set to Scheduler

This should be probably implemented per host using update.

#2 Updated by Ruben S. Montero over 6 years ago

The values should be also defined by cluster

#3 Updated by OpenNebula Systems Support Team about 6 years ago

  • Target version set to Release 4.6

#4 Updated by Jaime Melis over 5 years ago

  • Assignee set to Ruben S. Montero

#5 Updated by Ruben S. Montero over 5 years ago

  • Related to Feature #1849: HYPERVISOR_MEM as an amount rather than percentage. added

#6 Updated by Ruben S. Montero over 5 years ago

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

Implemented and ready in master. RESERVED_CPU y RESERVED_MEM can be defined host-wise or cluster-wise

Also available in: Atom PDF