Weight policy to stack/spread instances and "max_placement_results"
Bug #1805989 reported by
Belmiro Moreira
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Weights are applyed by the scheduler.
This means that if using "max_placement_
the weight policy will only be applied to the subset of allocation candidates retrieved by placement.
As consequence we lose the policy to stack/spread instances.
To post a comment you must log in.
Can you give a more detailed explanation/example of this:
"with a number bellow to the existing resources,"
By resources do you mean number of hosts? Or resources as in inventory, e.g. number of available VCPUs?
As for:
"the weight policy will only be applied to the subset of allocation candidates retrieved by placement."
This has always been the case - the weights are applied to the hosts after those hosts are filtered, so even if you had 1000 hosts in a deployment, maybe only 10 apply to a given flavor/image and then those 10 hosts are weighed. Placement is just doing initial filtering.
What am I missing?