| 2017-07-28 00:52:04 |
Ying Zuo |
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. |
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-used) * 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. |
|
| 2017-07-28 04:41:40 |
Ying Zuo |
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-used) * 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. |
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 a total of 4 vCPU and 2 vCPU have been allocated. cpu_allocation_ratio is 3. I expect that this host is considered a qualified host if I make a request to the <placement api>/resource_providers?resources=VCPU:5 because Capacity = (total-reserved) x allocation_ratio - used which is 10. 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. |
|
