)]}'
{"doc/source/specs/remote_device_communication.rst":[{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"acefc560397a454d8d2c0d6697ee1267f80f5983","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Remote Device Communication\r"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"},{"line_number":10,"context_line":"\r"},{"line_number":11,"context_line":"This spec proposes the solution of communicating to a remote device which\r"},{"line_number":12,"context_line":"is not managed by Dragonflow.\r"},{"line_number":13,"context_line":"\r"},{"line_number":14,"context_line":"Problem Description\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_af6b26b8","line":11,"range":{"start_line":11,"start_character":0,"end_line":11,"end_character":1},"updated":"2016-06-13 08:33:10.000000000","message":"Create a blueprint and put the link here","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"acefc560397a454d8d2c0d6697ee1267f80f5983","unresolved":false,"context_lines":[{"line_number":16,"context_line":"\r"},{"line_number":17,"context_line":"In the common scenario, a VM not only needs to communicate with another VM\r"},{"line_number":18,"context_line":"but also a physical machine, and we may deploy the physical router device\r"},{"line_number":19,"context_line":"as the gateway or next hop for logical routers in Dragonflow, however, the\r"},{"line_number":20,"context_line":"physical machine or router device may not be managed by Dragonflow, in this\r"},{"line_number":21,"context_line":"spec we call them remote device, so we must resolve the communication problem\r"},{"line_number":22,"context_line":"between VM and remote device.\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_ef69aebf","line":19,"range":{"start_line":19,"start_character":27,"end_line":19,"end_character":30},"updated":"2016-06-13 08:33:10.000000000","message":"of","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"dabf256bebace5958e0fee71c489c241fb498798","unresolved":false,"context_lines":[{"line_number":37,"context_line":"When we invoke the create_port Neutron API provided by Neutron plugin in\r"},{"line_number":38,"context_line":"Dragonflow, it will process it:\r"},{"line_number":39,"context_line":"\r"},{"line_number":40,"context_line":"1. We put the info that indicate the Neutron port is a remote device port\r"},{"line_number":41,"context_line":"into the binding_profile field, the field could be like this:\r"},{"line_number":42,"context_line":"\r"},{"line_number":43,"context_line":"binding_profile \u003d {\"port_key\": \"remote_port\",\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_4fbc42bb","line":40,"range":{"start_line":40,"start_character":0,"end_line":40,"end_character":9},"updated":"2016-06-13 08:47:25.000000000","message":"Does neutron plugin do this?\nOr the neutron plugin just receives the message that includes the","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"dabf256bebace5958e0fee71c489c241fb498798","unresolved":false,"context_lines":[{"line_number":37,"context_line":"When we invoke the create_port Neutron API provided by Neutron plugin in\r"},{"line_number":38,"context_line":"Dragonflow, it will process it:\r"},{"line_number":39,"context_line":"\r"},{"line_number":40,"context_line":"1. We put the info that indicate the Neutron port is a remote device port\r"},{"line_number":41,"context_line":"into the binding_profile field, the field could be like this:\r"},{"line_number":42,"context_line":"\r"},{"line_number":43,"context_line":"binding_profile \u003d {\"port_key\": \"remote_port\",\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_0f9a3a6e","line":40,"range":{"start_line":40,"start_character":24,"end_line":40,"end_character":32},"updated":"2016-06-13 08:47:25.000000000","message":"indicates","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"acefc560397a454d8d2c0d6697ee1267f80f5983","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Dragonflow, it will process it:\r"},{"line_number":39,"context_line":"\r"},{"line_number":40,"context_line":"1. We put the info that indicate the Neutron port is a remote device port\r"},{"line_number":41,"context_line":"into the binding_profile field, the field could be like this:\r"},{"line_number":42,"context_line":"\r"},{"line_number":43,"context_line":"binding_profile \u003d {\"port_key\": \"remote_port\",\r"},{"line_number":44,"context_line":"                   \"host_ip\": remote_chassis_ip}\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_8f7e2a68","line":41,"range":{"start_line":41,"start_character":48,"end_line":41,"end_character":50},"updated":"2016-06-13 08:33:10.000000000","message":"look","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"acefc560397a454d8d2c0d6697ee1267f80f5983","unresolved":false,"context_lines":[{"line_number":46,"context_line":"2. When Neutron plugin find it is a remote port by the binding_profile field\r"},{"line_number":47,"context_line":"in the create_port message, it will generate a specific chassis name for the\r"},{"line_number":48,"context_line":"remote port, store the lport in DF DB and publish the message with the\r"},{"line_number":49,"context_line":"SEND_ALL_TOPIC, the chassis name could be like this:\r"},{"line_number":50,"context_line":"\r"},{"line_number":51,"context_line":"chassis_name \u003d \"RemoteChassis:remote_chassis_ip\"\r"},{"line_number":52,"context_line":"\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_afb32699","line":49,"range":{"start_line":49,"start_character":0,"end_line":49,"end_character":14},"updated":"2016-06-13 08:33:10.000000000","message":"Why publish the message to SEND_ALL_TOPIC, this is not good for scale out.","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"acefc560397a454d8d2c0d6697ee1267f80f5983","unresolved":false,"context_lines":[{"line_number":63,"context_line":"itself to the specific remote chassis, if not, it will create the tunnel\r"},{"line_number":64,"context_line":"port and establish the tunnel to the remote chassis.\r"},{"line_number":65,"context_line":"\r"},{"line_number":66,"context_line":"3. After the tunnel port has been created, local controller will notify the\r"},{"line_number":67,"context_line":"create_lport message to Apps, it will be considered a normal remote port as\r"},{"line_number":68,"context_line":"in current implementation.\r"},{"line_number":69,"context_line":"\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_ea4cfc43","line":66,"range":{"start_line":66,"start_character":25,"end_line":66,"end_character":28},"updated":"2016-06-13 08:33:10.000000000","message":"This design is a little bit complex. Consider letting dragonflow newtron plugin publish two message in sequence, one is chassis_created, the other is logical port created, then the logic of local controller will be much simpler.","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"dabf256bebace5958e0fee71c489c241fb498798","unresolved":false,"context_lines":[{"line_number":68,"context_line":"in current implementation.\r"},{"line_number":69,"context_line":"\r"},{"line_number":70,"context_line":"On the other hand, when the remote device port is deleted from local cache,\r"},{"line_number":71,"context_line":"it means there are no need to communicate to the remote chassis anymore\r"},{"line_number":72,"context_line":"for the local controller, it should delete the corresponding tunnel port and\r"},{"line_number":73,"context_line":"forwarding rules.\r"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_4acd5030","line":71,"range":{"start_line":71,"start_character":22,"end_line":71,"end_character":26},"updated":"2016-06-13 08:47:25.000000000","message":"s","commit_id":"85f1c5aeffbf0fd129a649dade6fe0f4f1e82692"},{"author":{"_account_id":20229,"name":"Omer Anson","email":"omer.anson@toganetworks.com","username":"oanson"},"change_message_id":"6085ecda0cbe51070076c9e6b23b2a569f54442e","unresolved":false,"context_lines":[{"line_number":23,"context_line":"as the gateway or next hop of logical routers in Dragonflow, however, the\r"},{"line_number":24,"context_line":"physical machine or router device may not be managed by Dragonflow, in this\r"},{"line_number":25,"context_line":"spec we call them remote device, so we must resolve the communication problem\r"},{"line_number":26,"context_line":"between VM and remote device.\r"},{"line_number":27,"context_line":"\r"},{"line_number":28,"context_line":"Proposed Change\r"},{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7aa08908_7ef06491","line":26,"updated":"2016-06-15 05:14:02.000000000","message":"What information do the remote devices have? Do they know about tenants, or tenant networks? Do they have access to the DF DB? Can they match network ID to a subnet or a VM?\n\nConsider also adding some use cases.","commit_id":"748c52b508efe40296ae206ed88b5b7b4f4991b5"},{"author":{"_account_id":20287,"name":"hujie","email":"mike.hu@huawei.com","username":"hujie"},"change_message_id":"b48b60d796497a8d7612549032755e0ed8c9c890","unresolved":false,"context_lines":[{"line_number":23,"context_line":"as the gateway or next hop of logical routers in Dragonflow, however, the\r"},{"line_number":24,"context_line":"physical machine or router device may not be managed by Dragonflow, in this\r"},{"line_number":25,"context_line":"spec we call them remote device, so we must resolve the communication problem\r"},{"line_number":26,"context_line":"between VM and remote device.\r"},{"line_number":27,"context_line":"\r"},{"line_number":28,"context_line":"Proposed Change\r"},{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7aa08908_3ae25602","line":26,"in_reply_to":"7aa08908_7ef06491","updated":"2016-06-15 12:09:30.000000000","message":"1.The remote device is just a virtual or physical machine which is not managed by Dragonflow, we assume it belongs to a remote chassis which has the VTEP port, if local controller in Dragonflow wants to visit the remote device, it should encap the packet dst to the remote VTEP port.\n2.Remote device could belong to one tenant, or it has no tenant info at all, we should not limit it.\n3.From the aspect of a Dragonflow System, the remote device is not managed by it and of course could not access the DF DB in the system, the remote device may be managed by another cloud OS, if the remote device wants to visit a vm in the Dragonflow system, the cloud OS must know the vm info which is similar for Dragonflow system get the info of remote device described in this spec.","commit_id":"748c52b508efe40296ae206ed88b5b7b4f4991b5"},{"author":{"_account_id":18186,"name":"Denis Makogon","username":"denismakogon","inactive":true},"change_message_id":"0e928ebcd3b00acb0547d88d86035f33de5c222c","unresolved":false,"context_lines":[{"line_number":23,"context_line":"as the gateway or next hop of logical routers in Dragonflow, however, the\r"},{"line_number":24,"context_line":"physical machine or router device may not be managed by Dragonflow, in this\r"},{"line_number":25,"context_line":"spec we call them remote device, so we must resolve the communication problem\r"},{"line_number":26,"context_line":"between VM and remote device.\r"},{"line_number":27,"context_line":"\r"},{"line_number":28,"context_line":"Proposed Change\r"},{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7aa08908_69389ed5","line":26,"in_reply_to":"7aa08908_7ef06491","updated":"2016-06-15 11:08:20.000000000","message":"Agreed","commit_id":"748c52b508efe40296ae206ed88b5b7b4f4991b5"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":1,"context_line":"..\r"},{"line_number":2,"context_line":" This work is licensed under a Creative Commons Attribution 3.0 Unsuported\r"},{"line_number":3,"context_line":" License.\r"},{"line_number":4,"context_line":"\r"},{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_e3a5a947","line":2,"range":{"start_line":2,"start_character":64,"end_line":2,"end_character":74},"updated":"2016-06-15 22:23:54.000000000","message":"Unsuported -\u003e Unported\n\nNote that the word is Unported, not Unsupported.","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Remote Device Communication\r"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"},{"line_number":10,"context_line":"\r"},{"line_number":11,"context_line":"The URL of your launchpad Blueprint:\r"},{"line_number":12,"context_line":"\r"},{"line_number":13,"context_line":"https://blueprints.launchpad.net/dragonflow/+spec/remote-device-communication\r"},{"line_number":14,"context_line":"\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_c35ced4e","line":11,"updated":"2016-06-15 22:23:54.000000000","message":"I think you can remove line 11. I think it\u0027s just part of the template not part of the final document.","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":21,"context_line":"In the common scenario, a VM not only needs to communicate with another VM\r"},{"line_number":22,"context_line":"but also a physical machine, however, the virtual or physical machine\r"},{"line_number":23,"context_line":"may not be managed by Dragonflow, in this spec we call them remote device,\r"},{"line_number":24,"context_line":"if a vm in Dragonflow wants to communicate to remote device, Dragonflow\r"},{"line_number":25,"context_line":"needs to know some info of the remote device.\r"},{"line_number":26,"context_line":"\r"},{"line_number":27,"context_line":"Usually we would deploy a VTEP for virtual or physical machine in DC network,\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_833945f5","line":24,"range":{"start_line":24,"start_character":5,"end_line":24,"end_character":7},"updated":"2016-06-15 22:23:54.000000000","message":"vm -\u003e VM","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":27,"context_line":"Usually we would deploy a VTEP for virtual or physical machine in DC network,\r"},{"line_number":28,"context_line":"such as the Openvswitch vxlan port, the VTEP TOR(top of rack) and the\r"},{"line_number":29,"context_line":"physical router which support VTEP, so if Dragonflow knows the correct VTEP\r"},{"line_number":30,"context_line":"IP, vm in Dragonflow could access remote device by the overlay network.\r"},{"line_number":31,"context_line":"\r"},{"line_number":32,"context_line":"The remote device may belong to one tenant, or it has no tenant info at all,\r"},{"line_number":33,"context_line":"it could be managed by another cloud OS and how the remote device know the\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_e32ac98f","line":30,"range":{"start_line":30,"start_character":4,"end_line":30,"end_character":6},"updated":"2016-06-15 22:23:54.000000000","message":"vm -\u003e VM","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":29,"context_line":"physical router which support VTEP, so if Dragonflow knows the correct VTEP\r"},{"line_number":30,"context_line":"IP, vm in Dragonflow could access remote device by the overlay network.\r"},{"line_number":31,"context_line":"\r"},{"line_number":32,"context_line":"The remote device may belong to one tenant, or it has no tenant info at all,\r"},{"line_number":33,"context_line":"it could be managed by another cloud OS and how the remote device know the\r"},{"line_number":34,"context_line":"location of the vm in Dragonflow and access it is out of the scope of this\r"},{"line_number":35,"context_line":"spec.\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_be38dad5","line":32,"updated":"2016-06-15 22:23:54.000000000","message":"I\u0027d suggest removing both commas and putting a period after \"all\" and capitalize It on the next line to start a new sentence.","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":30,"context_line":"IP, vm in Dragonflow could access remote device by the overlay network.\r"},{"line_number":31,"context_line":"\r"},{"line_number":32,"context_line":"The remote device may belong to one tenant, or it has no tenant info at all,\r"},{"line_number":33,"context_line":"it could be managed by another cloud OS and how the remote device know the\r"},{"line_number":34,"context_line":"location of the vm in Dragonflow and access it is out of the scope of this\r"},{"line_number":35,"context_line":"spec.\r"},{"line_number":36,"context_line":"\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_9e351edd","line":33,"range":{"start_line":33,"start_character":66,"end_line":33,"end_character":70},"updated":"2016-06-15 22:23:54.000000000","message":"know -\u003e knows","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":31,"context_line":"\r"},{"line_number":32,"context_line":"The remote device may belong to one tenant, or it has no tenant info at all,\r"},{"line_number":33,"context_line":"it could be managed by another cloud OS and how the remote device know the\r"},{"line_number":34,"context_line":"location of the vm in Dragonflow and access it is out of the scope of this\r"},{"line_number":35,"context_line":"spec.\r"},{"line_number":36,"context_line":"\r"},{"line_number":37,"context_line":"Proposed Change\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_9e3cfec0","line":34,"range":{"start_line":34,"start_character":16,"end_line":34,"end_character":18},"updated":"2016-06-15 22:23:54.000000000","message":"vm -\u003e VM\naccess -\u003e accesses","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":38,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"},{"line_number":39,"context_line":"\r"},{"line_number":40,"context_line":"To resolve the problem, the general idea is we should tell the info of remote\r"},{"line_number":41,"context_line":"device to Dragonflow, we can invoke the Neutron API create_port and provide\r"},{"line_number":42,"context_line":"the info of remote device, plugin will assign a specific chassis name for\r"},{"line_number":43,"context_line":"the remote device and publish the create_port message. After chassis receive\r"},{"line_number":44,"context_line":"the message, it will create corresponding tunnel port to the remote chassis\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_5e71f6a7","line":41,"updated":"2016-06-15 22:23:54.000000000","message":"I\u0027d suggest changing the comma to a period and captializing \"We\"","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":40,"context_line":"To resolve the problem, the general idea is we should tell the info of remote\r"},{"line_number":41,"context_line":"device to Dragonflow, we can invoke the Neutron API create_port and provide\r"},{"line_number":42,"context_line":"the info of remote device, plugin will assign a specific chassis name for\r"},{"line_number":43,"context_line":"the remote device and publish the create_port message. After chassis receive\r"},{"line_number":44,"context_line":"the message, it will create corresponding tunnel port to the remote chassis\r"},{"line_number":45,"context_line":"and install the forwarding rules.\r"},{"line_number":46,"context_line":"\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_7ea31201","line":43,"range":{"start_line":43,"start_character":61,"end_line":43,"end_character":76},"updated":"2016-06-15 22:23:54.000000000","message":"\"the chassis receives\"","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"56caa40cabec2fcd76ba39194d392ce9dad34a60","unresolved":false,"context_lines":[{"line_number":56,"context_line":"binding_profile \u003d {\"port_key\": \"remote_port\",\r"},{"line_number":57,"context_line":"                   \"host_ip\": remote_chassis_ip}\r"},{"line_number":58,"context_line":"\r"},{"line_number":59,"context_line":"2. When Neutron plugin find it is a remote port by the binding_profile field\r"},{"line_number":60,"context_line":"in the create_port message, it will generate a specific chassis name for the\r"},{"line_number":61,"context_line":"remote port, store the lport in DF DB and publish the message with\r"},{"line_number":62,"context_line":"corresponding topic, if the lport belongs to some tenant, we could use\r"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7aa08908_5e7f3666","line":59,"range":{"start_line":59,"start_character":8,"end_line":59,"end_character":27},"updated":"2016-06-15 22:23:54.000000000","message":"\"the Neutron plugin finds\"","commit_id":"6eaaf30be2f6564e902c26594379d365584eed3b"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"7a3099dd813f9de0897d34823c1426dd9dda6004","unresolved":false,"context_lines":[{"line_number":30,"context_line":"The remote device may belong to one tenant or it has no tenant info at all.\r"},{"line_number":31,"context_line":"It could be managed by another cloud OS and how the remote device knows the\r"},{"line_number":32,"context_line":"location of the VM in Dragonflow and accesses it is out of the scope of this\r"},{"line_number":33,"context_line":"spec.\r"},{"line_number":34,"context_line":"\r"},{"line_number":35,"context_line":"Proposed Change\r"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a9d85d2_0a81014b","line":33,"updated":"2016-06-20 09:17:04.000000000","message":"sounds similar to what networking-l2gw does.  have you considered it?","commit_id":"ebaef49a3a8d61ee610c87352c109deb158829b4"},{"author":{"_account_id":20287,"name":"hujie","email":"mike.hu@huawei.com","username":"hujie"},"change_message_id":"ca1407ef020fc92af62b8023453578bba515cb26","unresolved":false,"context_lines":[{"line_number":30,"context_line":"The remote device may belong to one tenant or it has no tenant info at all.\r"},{"line_number":31,"context_line":"It could be managed by another cloud OS and how the remote device knows the\r"},{"line_number":32,"context_line":"location of the VM in Dragonflow and accesses it is out of the scope of this\r"},{"line_number":33,"context_line":"spec.\r"},{"line_number":34,"context_line":"\r"},{"line_number":35,"context_line":"Proposed Change\r"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1aa78d24_849c575e","line":33,"in_reply_to":"1aa78d24_e43f7c23","updated":"2016-07-06 03:24:44.000000000","message":"1. I think it depends on different scenarios, if you want to realize the different type network communication(e.g, vxlan to gre), maybe you could consider networking-l2gw, and if you want to realize same type network communication(e.g, vxlan vm to vxlan pm), the mechanism in this patch is better, we do not need a additional l2gw device.\n2. I\u0027m not sure whether network-l2gw support vxlan to gre and other dif type network communication, currently I only saw vxlan to vlan.\n3.Could network-l2gw support L3 communication? In the introduction I only saw it\u0027s responsible for L2 broadcast domain.","commit_id":"ebaef49a3a8d61ee610c87352c109deb158829b4"},{"author":{"_account_id":20287,"name":"hujie","email":"mike.hu@huawei.com","username":"hujie"},"change_message_id":"ced40569cdd45b74f3ef05561e2f0e254fbd813f","unresolved":false,"context_lines":[{"line_number":30,"context_line":"The remote device may belong to one tenant or it has no tenant info at all.\r"},{"line_number":31,"context_line":"It could be managed by another cloud OS and how the remote device knows the\r"},{"line_number":32,"context_line":"location of the VM in Dragonflow and accesses it is out of the scope of this\r"},{"line_number":33,"context_line":"spec.\r"},{"line_number":34,"context_line":"\r"},{"line_number":35,"context_line":"Proposed Change\r"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a9d85d2_0e5c47ec","line":33,"in_reply_to":"5a9d85d2_0a81014b","updated":"2016-06-21 03:29:47.000000000","message":"no matter what the remote device is, I think the mechanism is similar, right? The problem is we should confirm whether it\u0027s a standard method to do this work:)","commit_id":"ebaef49a3a8d61ee610c87352c109deb158829b4"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"5e89ee984f54d89602e8c1ed5846ca1b6a0c5ffd","unresolved":false,"context_lines":[{"line_number":30,"context_line":"The remote device may belong to one tenant or it has no tenant info at all.\r"},{"line_number":31,"context_line":"It could be managed by another cloud OS and how the remote device knows the\r"},{"line_number":32,"context_line":"location of the VM in Dragonflow and accesses it is out of the scope of this\r"},{"line_number":33,"context_line":"spec.\r"},{"line_number":34,"context_line":"\r"},{"line_number":35,"context_line":"Proposed Change\r"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\r"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1aa78d24_e43f7c23","line":33,"in_reply_to":"5a9d85d2_0e5c47ec","updated":"2016-07-04 09:42:27.000000000","message":"sure, and you think it\u0027s better to do it separately from networking-l2gw?\nwhile i\u0027m not necessarily against, i\u0027m curious why.","commit_id":"ebaef49a3a8d61ee610c87352c109deb158829b4"}]}