)]}'
{"specs/newton/approved/migration-use-target-vif.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"ce703887c5b3d9eaf5bb9c1b618c943bd820abf8","unresolved":false,"context_lines":[{"line_number":27,"context_line":"the information from the migration source host. This is relevant in the"},{"line_number":28,"context_line":"following scenarios:"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"#. Migration between hosts that run different l2 agents"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"   Today Live Migration is only working between nodes that run the same Neutron"},{"line_number":33,"context_line":"   l2 agent. If compute nodes run different l2 agents, for example the source"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_36bc70db","line":30,"updated":"2016-05-17 11:08:36.000000000","message":"This seems out of scope really.\n\nIs there a reason why it should be in scope? Maybe migrating between neutron technologies?","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"97e5978915cc2eeea1f914d957b16d1969ab36a2","unresolved":false,"context_lines":[{"line_number":27,"context_line":"the information from the migration source host. This is relevant in the"},{"line_number":28,"context_line":"following scenarios:"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"#. Migration between hosts that run different l2 agents"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"   Today Live Migration is only working between nodes that run the same Neutron"},{"line_number":33,"context_line":"   l2 agent. If compute nodes run different l2 agents, for example the source"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_dcc1c34f","line":30,"in_reply_to":"dab17558_36bc70db","updated":"2016-05-17 11:44:42.000000000","message":"The use case is migrating between Neutron technologies, exactly. For example if people want to switch from lb to ovs agent. Or another use case is switching from the ovs-hybrid firewall driver to the new ovs firewall driver.","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"ce703887c5b3d9eaf5bb9c1b618c943bd820abf8","unresolved":false,"context_lines":[{"line_number":75,"context_line":"    you have to consider this Neutron bug:"},{"line_number":76,"context_line":"    https://bugs.launchpad.net/neutron/+bug/1560957"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"#. Migration with Neutron MacVTap agent in some special configuration"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"   The Neutron MacVTap agent needs a physical_interface_mapping configuration"},{"line_number":81,"context_line":"   set up. On a high level, it specifies which NICs should be used for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_d6a6c4a9","line":78,"updated":"2016-05-17 11:08:36.000000000","message":"This isn\u0027t supported today, macvtap live-migration. Seems like a separate topic in its own right.","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"d7f2e92cebe44b9e3f30fef9a0518644059ef74b","unresolved":false,"context_lines":[{"line_number":75,"context_line":"    you have to consider this Neutron bug:"},{"line_number":76,"context_line":"    https://bugs.launchpad.net/neutron/+bug/1560957"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"#. Migration with Neutron MacVTap agent in some special configuration"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"   The Neutron MacVTap agent needs a physical_interface_mapping configuration"},{"line_number":81,"context_line":"   set up. On a high level, it specifies which NICs should be used for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abb7d3a_05e05428","line":78,"in_reply_to":"dab17558_9ca0db91","updated":"2016-05-31 13:59:31.000000000","message":"ah, OK.","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"97e5978915cc2eeea1f914d957b16d1969ab36a2","unresolved":false,"context_lines":[{"line_number":75,"context_line":"    you have to consider this Neutron bug:"},{"line_number":76,"context_line":"    https://bugs.launchpad.net/neutron/+bug/1560957"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"#. Migration with Neutron MacVTap agent in some special configuration"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"   The Neutron MacVTap agent needs a physical_interface_mapping configuration"},{"line_number":81,"context_line":"   set up. On a high level, it specifies which NICs should be used for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_9ca0db91","line":78,"in_reply_to":"dab17558_d6a6c4a9","updated":"2016-05-17 11:44:42.000000000","message":"sorry for the confusion here. This is not about the sr-iov macvtap support, but for the macvtap agent (independent from sr-iov) that was added during Mitaka [1]. Will precise that\n\n[1] https://bugs.launchpad.net/neutron/+bug/1480979","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"97e5978915cc2eeea1f914d957b16d1969ab36a2","unresolved":false,"context_lines":[{"line_number":145,"context_line":""},{"line_number":146,"context_line":"Above we identified 2 sub problems"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"#. Nova needs to get the vif information used on the migration target"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"   This information comes from the Neutron server and is stored in"},{"line_number":151,"context_line":"   the related Neutron Port information. Just querying the Port does not work,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_fce3e7a1","line":148,"updated":"2016-05-17 11:44:42.000000000","message":"Just moving this into pre_live_migration will work for the reference implemenations, but not for TOR switch drivers that Neutron configures as well. Therefore a Neutron effort has been set up [1] to allow a port to be bound to multiple hosts at the same time.\n\n[1] https://bugs.launchpad.net/neutron/+bug/1580880","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"d7f2e92cebe44b9e3f30fef9a0518644059ef74b","unresolved":false,"context_lines":[{"line_number":145,"context_line":""},{"line_number":146,"context_line":"Above we identified 2 sub problems"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"#. Nova needs to get the vif information used on the migration target"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"   This information comes from the Neutron server and is stored in"},{"line_number":151,"context_line":"   the related Neutron Port information. Just querying the Port does not work,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abb7d3a_c56c8cd2","line":148,"in_reply_to":"dab17558_fce3e7a1","updated":"2016-05-31 13:59:31.000000000","message":"yeah, the above effort is important here.","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"10a3c0e3e95a565ba2b450bef24e02d307fa28ea","unresolved":false,"context_lines":[{"line_number":185,"context_line":"REST API impact"},{"line_number":186,"context_line":"---------------"},{"line_number":187,"context_line":""},{"line_number":188,"context_line":"None"},{"line_number":189,"context_line":""},{"line_number":190,"context_line":"Security impact"},{"line_number":191,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abb7d3a_85d5641d","line":188,"updated":"2016-05-31 14:01:48.000000000","message":"I am not quite sure what the user is doing to trigger this.\n\nWhy are they moving between neutron tech, just because they are moving to a new host?\n\nIt feels like this should really be part of the live-resize spec, where you switch flavors to show you have switched neutron types. But even that doesn\u0027t sound great.","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"5cadc4bf2a06cc42f2650c712e66075129a03aac","unresolved":false,"context_lines":[{"line_number":185,"context_line":"REST API impact"},{"line_number":186,"context_line":"---------------"},{"line_number":187,"context_line":""},{"line_number":188,"context_line":"None"},{"line_number":189,"context_line":""},{"line_number":190,"context_line":"Security impact"},{"line_number":191,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abb7d3a_84e4d4ac","line":188,"in_reply_to":"9abb7d3a_85d5641d","updated":"2016-06-02 09:52:03.000000000","message":"This should be totally transparent to the user! It\u0027s the cloud operator who defines which neutron technology is being used. And it\u0027s also the operator who says that a new neutron tech should be used (e.g. moving the new and faster ovs conntrackd firewalldriver). If so, he could migrate the users instances to the new host running the new neutron technology, without any impact for the user.\n\nFor Nova there\u0027s no ReST API change or so. But a new Neutron API is required, that allows a port to be bound to multiple hosts. This api would be called by nova - but not by the user.\n\nNot sure about the live-resize thing. The problem is, that only one neutron technology can be run per host. So to change technology, you need to migrate to another host!","commit_id":"556f9acc1ef9f2481d88e1312fcb3d1563d5b24f"}]}