)]}'
{"doc/source/user/aggregates.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"a838127879d0d46160497dde3547c620b84b3052","unresolved":false,"context_lines":[{"line_number":79,"context_line":"cold migrate, live migrate, and unshelve. Move operations typically go through"},{"line_number":80,"context_line":"the scheduler to pick the target host *unless* a target host is specified and"},{"line_number":81,"context_line":"the request forces the server to that host by bypassing the scheduler. Only"},{"line_number":82,"context_line":"evacuate and live migrate can forcefully bypass the server to a specified host"},{"line_number":83,"context_line":"and even then it is highly recommended to *not* force and bypass the scheduler."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"With respect to availability zones, a server is restricted to a zone if:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_a647771d","line":82,"range":{"start_line":82,"start_character":41,"end_line":82,"end_character":58},"updated":"2019-04-05 21:28:45.000000000","message":"Do you mean \"bypass the scheduler\" or something like \"send the server\"? What\u0027s here is mixed up a bit.","commit_id":"4a11d1b10d1f40cc7af11d3cc3a4027a2605bb6b"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f8cd88105a68949b4ad8ea4cbea2d547df42501a","unresolved":false,"context_lines":[{"line_number":79,"context_line":"cold migrate, live migrate, and unshelve. Move operations typically go through"},{"line_number":80,"context_line":"the scheduler to pick the target host *unless* a target host is specified and"},{"line_number":81,"context_line":"the request forces the server to that host by bypassing the scheduler. Only"},{"line_number":82,"context_line":"evacuate and live migrate can forcefully bypass the server to a specified host"},{"line_number":83,"context_line":"and even then it is highly recommended to *not* force and bypass the scheduler."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"With respect to availability zones, a server is restricted to a zone if:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e6281f34","line":82,"range":{"start_line":82,"start_character":41,"end_line":82,"end_character":58},"in_reply_to":"5fc1f717_a647771d","updated":"2019-04-05 21:36:29.000000000","message":"Yes I meant \"bypass the scheduler\". Will fix.","commit_id":"4a11d1b10d1f40cc7af11d3cc3a4027a2605bb6b"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"a838127879d0d46160497dde3547c620b84b3052","unresolved":false,"context_lines":[{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Knowing this, it is dangerous to force a server to another host with evacuate"},{"line_number":99,"context_line":"or live migrate if the server is restricted to a zone and is then forced to"},{"line_number":100,"context_line":"move to a host in another zone, because that will create an inconsistency in"},{"line_number":101,"context_line":"the internal tracking of where that server should live and may require manually"},{"line_number":102,"context_line":"updating the database for that server."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"Design"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_a670d773","line":101,"range":{"start_line":100,"start_character":40,"end_line":101,"end_character":42},"updated":"2019-04-05 21:28:45.000000000","message":"The meaning or damage caused by this inconsistency is one of the things that is not well defined, so you might consider expanding on why this is bad.","commit_id":"4a11d1b10d1f40cc7af11d3cc3a4027a2605bb6b"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f8cd88105a68949b4ad8ea4cbea2d547df42501a","unresolved":false,"context_lines":[{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Knowing this, it is dangerous to force a server to another host with evacuate"},{"line_number":99,"context_line":"or live migrate if the server is restricted to a zone and is then forced to"},{"line_number":100,"context_line":"move to a host in another zone, because that will create an inconsistency in"},{"line_number":101,"context_line":"the internal tracking of where that server should live and may require manually"},{"line_number":102,"context_line":"updating the database for that server."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"Design"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_66142fea","line":101,"range":{"start_line":100,"start_character":40,"end_line":101,"end_character":42},"in_reply_to":"5fc1f717_a670d773","updated":"2019-04-05 21:36:29.000000000","message":"I wasn\u0027t sure how much detail I should get into here, but it\u0027s basically that if the user creates their server in zone A, the admin forces it to zone B, and then the user resizes the server it could be moved back to zone A, or worse - if the admin deleted or renamed zone A - the scheduling request will fail. This is because the ``availability_zone`` persisted with the RequestSpec is not updated during a forced live migration or evacuate. It\u0027s the latter part there about the RequestSpec that I\u0027m not sure I should mention in the docs here since it\u0027s so low level.","commit_id":"4a11d1b10d1f40cc7af11d3cc3a4027a2605bb6b"}]}