)]}'
{"specs/rocky/approved/add-force-in-cold-migration.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"fb739382354c8455d60526101d7e54117fa31cd4","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"If the scheduler check cannot be bypassed,"},{"line_number":22,"context_line":"VM instances cannot be moved to the target host in some cases"},{"line_number":23,"context_line":"during administrative operation."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"---------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3fa0c359_be953c42","line":23,"range":{"start_line":21,"start_character":0,"end_line":23,"end_character":32},"updated":"2018-02-21 15:38:32.000000000","message":"why would you care what node the instance get migrated too as long as it not one you are performing an administrative operation on. e.g. why can you not just mark the nodes under maintenance as down and then let the scheduler decide where to put the vm instance like normal.","commit_id":"d2ad8d25ce8ceb16d583d00b95fae4584560e62c"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"66d3458a647c062c8ba5de34a263575bf3eec470","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"If the scheduler check cannot be bypassed,"},{"line_number":22,"context_line":"VM instances cannot be moved to the target host in some cases"},{"line_number":23,"context_line":"during administrative operation."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"---------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3fa0c359_195c8aeb","line":23,"range":{"start_line":21,"start_character":0,"end_line":23,"end_character":32},"in_reply_to":"3fa0c359_be953c42","updated":"2018-02-21 16:06:40.000000000","message":"They want to tell the scheduler where to put the instance (which they can since queens). I\u0027m fine with that. But I\u0027m not OK with bypassing the scheduler since we can then get into all sorts of trouble with respect to allocation tracking in Placement, and duplication in the conductor code that still needs to update placement for the allocations made on the forced dest host because we bypassed the scheduler (which we have to do today for evacuate and live migrate if you\u0027re forcing the host). There are TODOs in that code for removing the technical debt still:\n\nhttps://github.com/openstack/nova/blob/addbfae6769c1033c618019868314ef3100746d9/nova/conductor/tasks/live_migrate.py#L87","commit_id":"d2ad8d25ce8ceb16d583d00b95fae4584560e62c"}]}