On 03/11/2015 12:53 PM, Sylvain Bauza wrote: >> Reporting on Scheduler Fails >> ---------------------------- >> >> Apparently, some time recently, we stopped logging scheduler fails >> above DEBUG, and that behavior also snuck back into Juno as well >> (https://etherpad.openstack.org/p/PHL-ops-nova-feedback L78). This >> has made tracking down root cause of failures far more difficult. >> >> Action: this should hopefully be a quick fix we can get in for Kilo >> and backport. > It's unfortunate that failed scheduling attempts are providing only an > INFO log. A quick fix could be at least to turn the verbosity up to WARN > so it would be noticied more easily (including the whole filters stack > with their results). > That said, I'm pretty against any proposal which would expose those > specific details (ie. the number of hosts which are succeeding per > filter) in an API endpoint because it would also expose the underlying > infrastructure capacity and would ease DoS discoveries. A workaround > could be to include in the ERROR message only the name of the filter > which has been denied so the operators could very easily match what the > user is saying with what they're seeing in the scheduler logs. > > Does that work for people ? I can provide changes for both. > > -Sylvain
Bug filed for tracking this here - https://bugs.launchpad.net/nova/+bug/1431291 if any additional folks want to add details. It's been set as High and a kilo-3 item so it doesn't get lost. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ 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
