On 08/01/2018 02:02 PM, Chris Friesen wrote:
On 08/01/2018 11:32 AM, melanie witt wrote:
I think it's definitely a significant issue that troubleshooting "No
allocation
candidates returned" from placement is so difficult. However, it's not
straightforward to log detail in placement when the request for
allocation
candidates is essentially "SELECT * FROM nodes WHERE cpu usage <
needed and disk
usage < needed and memory usage < needed" and the result is returned
from the API.
I think the only way to get useful info on a failure would be to break
down the huge SQL statement into subclauses and store the results of the
intermediate queries.
This is a good idea and something that can be done.
Unfortunately, it's refactoring work and as a community, we tend to
prioritize fancy features like NUMA topology and CPU pinning over
refactoring work.
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
