Instance multi-create doesn't support available resources spread between children RPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Medium
|
Wenping Song | ||
Ussuri |
New
|
Medium
|
Unassigned |
Bug Description
If a flavor asks for resources that are provided by nested Resource Provider inventories (eg. VGPU) and the user wants multi-create (ie. say --max 2) then the scheduler could be returning a NoValidHosts exception even if each nested Resource Provider can support at least specific instance, if the total wanted capacity is not supported by only one nested RP.
For example, if two children RP have 4 VGPU inventories :
- you can ask for a flavor with 2 VGPU with --max 2
- but you can't ask for a flavor with 4 VGPU and --max 2
======
Original report :
When boot more than one instance with accelerator, and the accelerators are in one compute node, there will be two problems as below:
One problem is as we always get the first item(alloc_reqs[0]) in alloc_reqs, when we iterator the second instance, it will throw conflict exception when putting the allocations.
Another is as we always get the first item in alloc_reqs_
More details you can see: https:/
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → Wenping Song (wenping1) |
tags: | added: schedul |
tags: |
added: cyborg scheduler removed: schedul |
summary: |
- Boot more than one instances failed with accelerators in its flavor + Instance multi-create doesn't support available resources spread between + children RPs |
tags: | added: vgpu |
description: | updated |
Given we are after RC1 (which means that we only accept regression bugfixes for RC2 and later versions), I think we should just document the current caveat in https:/ /docs.openstack .org/api- guide/compute/ accelerator- support. html and trying to backport the bugfix for a later Ussuri release (say 21.0.1).