Bug #1924
Scheduler shouldn't add VMs that cannot be deployed to the MAX_VMS limit
| Status: | Closed | Start date: | 04/17/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Scheduler | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.0 |
Description
Otherwise, the scheduler can leave out of the scheduling cycle good VMs because of VMs that will never be deployed (insufficient resources, wrong requirements, etc).
Associated revisions
bug #1924: Add to comment to the Scheduler configuration file for MAX_VM=0
History
#1
Updated by Ruben S. Montero about 8 years ago
- Assignee set to Ruben S. Montero
#2
Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Closed
- Resolution set to fixed