Public bug reported:
It's great that the Placement API v1.4 provides a way to query for hosts
that can fulfill a set of allocations. However, because the max_unit
doesn't account for allocation_ratio, the result is not as expected.
For example, my host has 2 vCPU available out of a total of 4 vCPU and
cpu_allocation_ratio is 3. I expect that it's considered a qualified
host if I make a request to the <placement
api>/resource_providers?resources=VCPU:5 because capacity = (total-
reserved) * allocation which is 6. However, because the max_unit is set
as the total which is 4, my host is not in the response although it can
fulfill the requested allocation.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1707085
Title:
Max_unit should account for allocation_ratio
Status in OpenStack Compute (nova):
New
Bug description:
It's great that the Placement API v1.4 provides a way to query for
hosts that can fulfill a set of allocations. However, because the
max_unit doesn't account for allocation_ratio, the result is not as
expected.
For example, my host has 2 vCPU available out of a total of 4 vCPU and
cpu_allocation_ratio is 3. I expect that it's considered a qualified
host if I make a request to the <placement
api>/resource_providers?resources=VCPU:5 because capacity = (total-
reserved) * allocation which is 6. However, because the max_unit is
set as the total which is 4, my host is not in the response although
it can fulfill the requested allocation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1707085/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
