)]}'
{"specs/ocata/approved/resource-providers-scheduler-db-filters.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7f8d02a8280d49545523b16c5707d1a3803e59e4","unresolved":false,"context_lines":[{"line_number":137,"context_line":"(compute hosts) that meet a set of requested resource amounts."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Initially, since no nova-computes had successfully run through their periodic"},{"line_number":140,"context_line":"audit interval, the placement database would be empty and thus the request from"},{"line_number":141,"context_line":"the scheduler to the placement API for resource providers would return an empty"},{"line_number":142,"context_line":"list. We will place code into the scheduler that, upon seeing an empty list of"},{"line_number":143,"context_line":"resource providers returned from the placement API, will fall back to the"},{"line_number":144,"context_line":"legacy behaviour of calling ComputeNodeList.get_all(). This will allow the old"},{"line_number":145,"context_line":"scheduler behaviour to take over in between the time when the new placement"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa31d9ce_e313be5a","line":142,"range":{"start_line":140,"start_character":63,"end_line":142,"end_character":5},"updated":"2017-02-10 20:16:43.000000000","message":"So this is wrong now too. Given the update below (which is correct), we don\u0027t even call placement until all computes are running ocata. So we wouldn\u0027t make a request to the placement service before that, we\u0027ll fallback to the old compute_nodes table lookup. If after everything is upgraded and we query placement and get nothing back, then it\u0027s a NoValidHost as always.\n\nUltimately the end result is the same for the end user and operator, so the wording here isn\u0027t a sticking point for me, but it\u0027s technically correct based on how things were implemented.","commit_id":"0b634d36994d403bfa2e29defe118f8f51292653"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"520ed601fdc579a717008be1a3eb70844c958c3a","unresolved":false,"context_lines":[{"line_number":137,"context_line":"(compute hosts) that meet a set of requested resource amounts."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Initially, since no nova-computes had successfully run through their periodic"},{"line_number":140,"context_line":"audit interval, the placement database would be empty and thus the request from"},{"line_number":141,"context_line":"the scheduler to the placement API for resource providers would return an empty"},{"line_number":142,"context_line":"list. We will place code into the scheduler that, upon seeing an empty list of"},{"line_number":143,"context_line":"resource providers returned from the placement API, will fall back to the"},{"line_number":144,"context_line":"legacy behaviour of calling ComputeNodeList.get_all(). This will allow the old"},{"line_number":145,"context_line":"scheduler behaviour to take over in between the time when the new placement"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa31d9ce_83520212","line":142,"range":{"start_line":140,"start_character":63,"end_line":142,"end_character":5},"in_reply_to":"fa31d9ce_e313be5a","updated":"2017-02-10 20:17:51.000000000","message":"Yeah, good catch. I\u0027ll reword.","commit_id":"0b634d36994d403bfa2e29defe118f8f51292653"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"2947aac07a3362be3274ca56fc4fe059fd6078e9","unresolved":false,"context_lines":[{"line_number":132,"context_line":"self-healing process into the new behaviour of the scheduler calling to the"},{"line_number":133,"context_line":"placement API to winnow the set of compute hosts that are acted upon. If the"},{"line_number":134,"context_line":"placement service has been set up but all nova-computes have yet to be upgraded"},{"line_number":135,"context_line":"to Ocata, the scheduler will continue to use its existing behaviour of querying"},{"line_number":136,"context_line":"the Nova cell database compute_nodes table. Once all nova-compute workers have"},{"line_number":137,"context_line":"been upgraded to Ocata, the new Ocata scheduler will attempt to contact the"},{"line_number":138,"context_line":"placement service to get a list of resource providers (compute hosts) that meet"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa31d9ce_8e2b0982","line":135,"range":{"start_line":135,"start_character":58,"end_line":135,"end_character":67},"updated":"2017-02-10 20:47:45.000000000","message":"This could have been copy/paste\u0027d from the existing version, but normally I -1 for this out of consistency :(","commit_id":"3c48c2295b20b1b6e947b13635f01e04134115ff"}]}