)]}'
{"cinder/scheduler/simple.py":[{"author":{"_account_id":13900,"name":"Accela Zhao","email":"accelazh@gmail.com","username":"accelazh"},"change_message_id":"1ca697c93698884532ca5d8cf54a8e00657a1e89","unresolved":false,"context_lines":[{"line_number":30,"context_line":"                               \u0027CapabilitiesFilter\u0027]"},{"line_number":31,"context_line":"  scheduler_default_weighers \u003d \u0027ChanceWeigher\u0027"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"If one prefers the scheduler to pick the back-end which has the smallest"},{"line_number":34,"context_line":"allocated space that the scheduler can see (like SimpleScheduler did), use"},{"line_number":35,"context_line":"following combination of filters and weighers with FilterScheduler."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"7a016987_a68c70d7","line":33,"updated":"2015-06-01 11:14:31.000000000","message":"\"the smallest allocated space\" seems a bit confusing. It sounds like to select a back-end which has the smallest space (allocated by the operator). How about keep the original one, the \"most available space\"?","commit_id":"32b25fa5473785e42460915a5cbde29488f9a31b"},{"author":{"_account_id":13900,"name":"Accela Zhao","email":"accelazh@gmail.com","username":"accelazh"},"change_message_id":"a0dff57e9fba88c98f7509b945aa3e56fe46ea9e","unresolved":false,"context_lines":[{"line_number":30,"context_line":"                               \u0027CapabilitiesFilter\u0027]"},{"line_number":31,"context_line":"  scheduler_default_weighers \u003d \u0027ChanceWeigher\u0027"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"If one prefers the scheduler to pick the back-end which has the smallest"},{"line_number":34,"context_line":"allocated space that the scheduler can see (like SimpleScheduler did), use"},{"line_number":35,"context_line":"following combination of filters and weighers with FilterScheduler."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"5afe65bd_87d9ef85","line":33,"in_reply_to":"7a016987_61878261","updated":"2015-06-03 12:01:49.000000000","message":"Good point! Thanks for clarifying it.","commit_id":"32b25fa5473785e42460915a5cbde29488f9a31b"},{"author":{"_account_id":9171,"name":"Vipin Balachandran","email":"vipin.bl@gmail.com","username":"vbala"},"change_message_id":"5ceb210407fd1e07cbce15d62102175a09f861ff","unresolved":false,"context_lines":[{"line_number":30,"context_line":"                               \u0027CapabilitiesFilter\u0027]"},{"line_number":31,"context_line":"  scheduler_default_weighers \u003d \u0027ChanceWeigher\u0027"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"If one prefers the scheduler to pick the back-end which has the smallest"},{"line_number":34,"context_line":"allocated space that the scheduler can see (like SimpleScheduler did), use"},{"line_number":35,"context_line":"following combination of filters and weighers with FilterScheduler."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"7a016987_61878261","line":33,"in_reply_to":"7a016987_a68c70d7","updated":"2015-06-01 11:24:26.000000000","message":"\u003eHow about keep the original one, the \"most available space\"?\n\nThe below settings (AllocatedCapacityWeigher with a negative weight) picks a host with the least allocated space which may not be the one with most available space.","commit_id":"32b25fa5473785e42460915a5cbde29488f9a31b"}]}