)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7787,"name":"Kevin Benton","email":"kevin@benton.pub","username":"blak111"},"change_message_id":"17a2113672b6f08953c59bd19ff5ff7e90718ffe","unresolved":false,"context_lines":[{"line_number":12,"context_line":"the new_host where the port will be migrated."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"In order to facilitate the live migration these host extensions"},{"line_number":15,"context_line":"will be added to the Portbinding table."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Change-Id: I7bc41410a7c72cb7ac41ccccf00788453e8dd222"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"fa69d971_4ef24a71","line":15,"updated":"2016-01-07 20:50:23.000000000","message":"It\u0027s hard to guage if this is the best approach without knowing how this will be leveraged.\n\nCan you add a small workflow to the commit message that shows which fields will be updated during a live migration and what each field will be used for internally in Neutron (i.e. by DVR and ML2)?","commit_id":"bab41a7734ab4db5c4f23c097b21a06045b83024"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"ce309fb1ae19abaad71c580b5f19a56b7fc3f8ad","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Today a physical port is bound to a single host, but if we migrate"},{"line_number":10,"context_line":"a VM, in the process of VM migration we should be able to update"},{"line_number":11,"context_line":"the port temporarily with the two hosts, one the current existing"},{"line_number":12,"context_line":"host and the other new_host where the port will finally end up."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Once the physical port lands on the destination node, new_host"},{"line_number":15,"context_line":"will be set to none or retain the same host and the host attribute"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"9a68dd71_a66c63d1","line":12,"range":{"start_line":11,"start_character":21,"end_line":12,"end_character":62},"updated":"2016-01-26 10:34:01.000000000","message":"I guess not with two ports but with just destination host","commit_id":"de05f58de0a84ef262288a9dca27f0704ac12d14"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"ce309fb1ae19abaad71c580b5f19a56b7fc3f8ad","unresolved":false,"context_lines":[{"line_number":16,"context_line":"will point to the right compute host."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"During Nova live migration the pre-live-migration task will set"},{"line_number":19,"context_line":"the destination host of the port to the new_host attribute."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"With this information the Neutron can take advantage of it and"},{"line_number":22,"context_line":"try to pro-actively create the l2 and l3 networks in the destination"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"9a68dd71_0609afdd","line":19,"range":{"start_line":19,"start_character":40,"end_line":19,"end_character":58},"updated":"2016-01-26 10:34:01.000000000","message":"can we use existing \u0027binding:profile\u0027 dict field in a PortBinding table which nova could update with, like, {\u0027status\u0027: \u0027migrating\u0027, \u0027destination\u0027: \u0027node-10\u0027} on pre_live_migration step (setup_networks_on_host())? Then neutron plugin can prepare networks on host \u0027node-10\u0027 if needed. On post_migration step nova will update port\u0027s binding:host and clear binding:profile.","commit_id":"de05f58de0a84ef262288a9dca27f0704ac12d14"},{"author":{"_account_id":7016,"name":"Swaminathan Vasudevan","email":"swvasude@cisco.com","username":"souminathan"},"change_message_id":"05564fd2ff81f4adf6d94bb31724e7c9e9a06e7c","unresolved":false,"context_lines":[{"line_number":16,"context_line":"will point to the right compute host."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"During Nova live migration the pre-live-migration task will set"},{"line_number":19,"context_line":"the destination host of the port to the new_host attribute."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"With this information the Neutron can take advantage of it and"},{"line_number":22,"context_line":"try to pro-actively create the l2 and l3 networks in the destination"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"7a5de9d1_c1efa885","line":19,"range":{"start_line":19,"start_character":40,"end_line":19,"end_character":58},"in_reply_to":"9a68dd71_0609afdd","updated":"2016-01-28 22:03:30.000000000","message":"will think about this and if that is the right direction we should be moving in that direction.","commit_id":"de05f58de0a84ef262288a9dca27f0704ac12d14"}],"neutron/db/portbindings_db.py":[{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"ce309fb1ae19abaad71c580b5f19a56b7fc3f8ad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"9a68dd71_66a2eb9c","side":"PARENT","updated":"2016-01-26 10:34:01.000000000","message":"I think neutron.plugins.ml2.models.PortBinding table is the one used for port bindings, at least by ml2 plugin","commit_id":"5ffa890a9937cb92de3266ecad1b87db447e030c"},{"author":{"_account_id":7016,"name":"Swaminathan Vasudevan","email":"swvasude@cisco.com","username":"souminathan"},"change_message_id":"05564fd2ff81f4adf6d94bb31724e7c9e9a06e7c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"7a5de9d1_01ace032","side":"PARENT","in_reply_to":"9a68dd71_66a2eb9c","updated":"2016-01-28 22:03:30.000000000","message":"You may be right.\nBut what does this table do. Is anyone even using it.","commit_id":"5ffa890a9937cb92de3266ecad1b87db447e030c"}]}