Comment 6 for bug 1431291

ok, so I've spent some time staring at the filter scheduler, and because the entire thing is written in this generator reduce model, we never have enough information flowing back. I thought this might be an easier issue to solve, but I'm not seeing a way through this.

The UX I think we want is:

on Schedule:

nova.scheduler INFO "Instance UUID scheduled to host X"

on fail to schedule

nova.scheduler WARN "Instance UUID failed to schedule due to Not Enough Y on hosts A(Y=x), B(Y=z)..."

Basically provide the closest match hosts.

All of the information is sitting in the DEBUG logs, but there is a lot of filtering and assembly to get back to a global answer there.