)]}'
{"doc/networking-guide/source/deploy-lb-ha-vrrp.rst":[{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":9,"context_line":"(VRRP) via ``keepalived`` and provides failover of routing for self-service"},{"line_number":10,"context_line":"networks. It requires a minimum of two network nodes because VRRP creates"},{"line_number":11,"context_line":"one master (active) instance and at least one backup instance of each"},{"line_number":12,"context_line":"router. If the layer-3 agent or network node that contains the master"},{"line_number":13,"context_line":"instance fails, VRRP promotes one of the backup instances to master."},{"line_number":14,"context_line":"Consider the following attributes of this high-availability mechanism to"},{"line_number":15,"context_line":"determine practicality in your environment:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_e78d2c32","line":12,"updated":"2016-09-21 19:35:03.000000000","message":"keepalived performs a failover when it stops receiving hello messages from the current master, so we don\u0027t failover if the L3 agent dies, only if a node dies or because of a network interruption.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":9,"context_line":"(VRRP) via ``keepalived`` and provides failover of routing for self-service"},{"line_number":10,"context_line":"networks. It requires a minimum of two network nodes because VRRP creates"},{"line_number":11,"context_line":"one master (active) instance and at least one backup instance of each"},{"line_number":12,"context_line":"router. If the layer-3 agent or network node that contains the master"},{"line_number":13,"context_line":"instance fails, VRRP promotes one of the backup instances to master."},{"line_number":14,"context_line":"Consider the following attributes of this high-availability mechanism to"},{"line_number":15,"context_line":"determine practicality in your environment:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_2018d4d2","line":12,"in_reply_to":"7a8ec9b2_e78d2c32","updated":"2016-09-21 23:43:20.000000000","message":"Will correct as per IRC discussion. On Ubuntu/Debian, stopping the layer-3 agent via init script also terminates the keepalived processes which triggers a failover.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  operate at layer-2 and rely on physical network infrastructure for"},{"line_number":28,"context_line":"  redundancy."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"* Only maintains state of network connections for instances with a floating"},{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_c704b07f","line":30,"updated":"2016-09-21 19:35:03.000000000","message":"I don\u0027t think this is strictly speaking accurate. The L3 HA solution doesn\u0027t use conntrackd replication at all, so this comes down to stateful NAT vs. stateless NAT. AFAIK if you use a FIP, it\u0027s a 1:1 stateless NAT and thus there is no state to replicate and traffic will just happily flow. If you don\u0027t use a FIP, you\u0027re using SNAT, in which case there is state tracking, and when you failover, state will not exist and incoming packets will be dropped as conntrackd won\u0027t identify these packets as part of an existing flow. I\u0027ve noticed that Brian Haley knows a lot about this area, you can ask him to comb over this further.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  operate at layer-2 and rely on physical network infrastructure for"},{"line_number":28,"context_line":"  redundancy."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"* Only maintains state of network connections for instances with a floating"},{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_408080bf","line":30,"in_reply_to":"7a8ec9b2_c704b07f","updated":"2016-09-21 23:43:20.000000000","message":"Perhaps I should reword this using the actual reason and note the side effects?","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"For production deployments, we recommend at least three network nodes"},{"line_number":35,"context_line":"with sufficient resources to handle network traffic for the entire"},{"line_number":36,"context_line":"environment if one network node fails."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_c72bd0e9","line":34,"updated":"2016-09-21 19:35:03.000000000","message":"The requirement is 2+, recommending anything over than that is strictly about the amount of routers and data plane traffic you expect to have. There is nothing special about the number 3.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"29e846e6812175b84df4bfcab918c3412b316dd1","unresolved":false,"context_lines":[{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"For production deployments, we recommend at least three network nodes"},{"line_number":35,"context_line":"with sufficient resources to handle network traffic for the entire"},{"line_number":36,"context_line":"environment if one network node fails."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a98d1f4_3f1afc6e","line":34,"in_reply_to":"5a8bc5a2_782bcf94","updated":"2016-09-29 22:59:05.000000000","message":"Done","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"c8b3ade27391ef9a69a380bc7bcc8222320881cf","unresolved":false,"context_lines":[{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"For production deployments, we recommend at least three network nodes"},{"line_number":35,"context_line":"with sufficient resources to handle network traffic for the entire"},{"line_number":36,"context_line":"environment if one network node fails."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a8bc5a2_782bcf94","line":34,"in_reply_to":"7a8ec9b2_40b3209a","updated":"2016-09-23 12:19:57.000000000","message":"I see. Maybe that could be explained then.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":31,"context_line":"  IP address. Instances with a fixed IP address must restore existing"},{"line_number":32,"context_line":"  network connections."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"For production deployments, we recommend at least three network nodes"},{"line_number":35,"context_line":"with sufficient resources to handle network traffic for the entire"},{"line_number":36,"context_line":"environment if one network node fails."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_40b3209a","line":34,"in_reply_to":"7a8ec9b2_c72bd0e9","updated":"2016-09-21 23:43:20.000000000","message":"I think the idea behind the recommendation involves the ability to continue operating with failover capabilities after a node fails and/or continue to balance traffic among two nodes.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":".. warning::"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"   This high-availability mechanism is not compatible with the layer-2"},{"line_number":41,"context_line":"   population mechanism. You must disable layer-2 population in the"},{"line_number":42,"context_line":"   ``linuxbridge_agent.ini`` file and restart the Linux bridge agent"},{"line_number":43,"context_line":"   on all existing network and compute nodes prior to deploying the example"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_270e348c","line":40,"updated":"2016-09-21 19:35:03.000000000","message":"As you know Anil fixed [1] the general issue so I no longer recommend to disable l2pop *when using the OVS agent*. I recall there was a bug about LB + L3 HA + l2pop but I don\u0027t know if it was actually root caused.\n\n[1] https://review.openstack.org/#/c/255237/","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":".. warning::"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"   This high-availability mechanism is not compatible with the layer-2"},{"line_number":41,"context_line":"   population mechanism. You must disable layer-2 population in the"},{"line_number":42,"context_line":"   ``linuxbridge_agent.ini`` file and restart the Linux bridge agent"},{"line_number":43,"context_line":"   on all existing network and compute nodes prior to deploying the example"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_864c6043","line":40,"in_reply_to":"7a8ec9b2_270e348c","updated":"2016-09-21 23:43:20.000000000","message":"Using LB+L3HA on Mitaka, the VMs and DHCP servers could see each other, but not the router... nor could the router see the VMs or DHCP servers. I have a feeling I hit https://bugs.launchpad.net/neutron/+bug/1523031, which later became https://bugs.launchpad.net/neutron/+bug/1590845. I see a patch for the latter, but the bug changed state from fix released to confirmed and back to fix released (without actually changing the state again). This patch may address the issue, but didn\u0027t tag the bug(s) - https://review.openstack.org/#/c/255237/. Given the confusion, I prefer to disable L2P with LB+L3HA until we can confirm a solution to the problem, or recommend enabling at own risk.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Restart the following services:"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"   * Layer-3 agent"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Network node 2"},{"line_number":107,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_e7652c45","line":104,"updated":"2016-09-21 19:35:03.000000000","message":"There is no need to restart agents after you enable l3_ha on the controller.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Restart the following services:"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"   * Layer-3 agent"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Network node 2"},{"line_number":107,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_0032f80f","line":104,"in_reply_to":"7a8ec9b2_e7652c45","updated":"2016-09-21 23:43:20.000000000","message":"Done","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Similar to :ref:`deploy-lb-selfservice`, the configuration supports multiple"},{"line_number":183,"context_line":"VXLAN self-service networks. The Networking service lacks support for adding"},{"line_number":184,"context_line":"VRRP to an existing router, so the following procedure creates an additional"},{"line_number":185,"context_line":"self-service network and router. After enabling high-availability, all"},{"line_number":186,"context_line":"additional routers use VRRP."},{"line_number":187,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_67ae7c2f","line":184,"updated":"2016-09-21 19:35:03.000000000","message":"Heyyyy that\u0027s not true :)\n\nPseudo bash:\nneutron router-update router --admin_state\u003dFalse\nneutron router-update router --ha\u003dTrue\nneutron router-update router --admin_state\u003dTrue\n\nYou will have a data plane interruption as the router is unscheduled from a L3 agent, updated in the DB to HA then scheduled again.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"29e846e6812175b84df4bfcab918c3412b316dd1","unresolved":false,"context_lines":[{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Similar to :ref:`deploy-lb-selfservice`, the configuration supports multiple"},{"line_number":183,"context_line":"VXLAN self-service networks. The Networking service lacks support for adding"},{"line_number":184,"context_line":"VRRP to an existing router, so the following procedure creates an additional"},{"line_number":185,"context_line":"self-service network and router. After enabling high-availability, all"},{"line_number":186,"context_line":"additional routers use VRRP."},{"line_number":187,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a98d1f4_bf244caf","line":184,"in_reply_to":"5a8bc5a2_5807f31b","updated":"2016-09-29 22:59:05.000000000","message":"Done","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Similar to :ref:`deploy-lb-selfservice`, the configuration supports multiple"},{"line_number":183,"context_line":"VXLAN self-service networks. The Networking service lacks support for adding"},{"line_number":184,"context_line":"VRRP to an existing router, so the following procedure creates an additional"},{"line_number":185,"context_line":"self-service network and router. After enabling high-availability, all"},{"line_number":186,"context_line":"additional routers use VRRP."},{"line_number":187,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_800d2840","line":184,"in_reply_to":"7a8ec9b2_67ae7c2f","updated":"2016-09-21 23:43:20.000000000","message":"In which version of the neutron client (or OSC) did this appear?","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"c8b3ade27391ef9a69a380bc7bcc8222320881cf","unresolved":false,"context_lines":[{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Similar to :ref:`deploy-lb-selfservice`, the configuration supports multiple"},{"line_number":183,"context_line":"VXLAN self-service networks. The Networking service lacks support for adding"},{"line_number":184,"context_line":"VRRP to an existing router, so the following procedure creates an additional"},{"line_number":185,"context_line":"self-service network and router. After enabling high-availability, all"},{"line_number":186,"context_line":"additional routers use VRRP."},{"line_number":187,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a8bc5a2_5807f31b","line":184,"in_reply_to":"7a8ec9b2_800d2840","updated":"2016-09-23 12:19:57.000000000","message":"It\u0027s been there forever.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"b865638a5000370f0065d406400eaad79d9ea32e","unresolved":false,"context_lines":[{"line_number":495,"context_line":"   should see a minimal, if any, interruption of connectivity to the"},{"line_number":496,"context_line":"   instance."},{"line_number":497,"context_line":""},{"line_number":498,"context_line":"#. On the network node with the master router, stop the layer-3 agent."},{"line_number":499,"context_line":""},{"line_number":500,"context_line":"#. On the network node with the backup router, verify that the interfaces"},{"line_number":501,"context_line":"   in the ``router`` namespace contain IP addresses."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_b92b4c81","line":498,"updated":"2016-09-21 19:35:03.000000000","message":"As mentioned earlier this step should not cause a failover. You can suggest here to kill a NIC or a node.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"77fa72c5a094e5421fd44307b39475abea56ee75","unresolved":false,"context_lines":[{"line_number":495,"context_line":"   should see a minimal, if any, interruption of connectivity to the"},{"line_number":496,"context_line":"   instance."},{"line_number":497,"context_line":""},{"line_number":498,"context_line":"#. On the network node with the master router, stop the layer-3 agent."},{"line_number":499,"context_line":""},{"line_number":500,"context_line":"#. On the network node with the backup router, verify that the interfaces"},{"line_number":501,"context_line":"   in the ``router`` namespace contain IP addresses."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a8ec9b2_630bc624","line":498,"in_reply_to":"7a8ec9b2_b92b4c81","updated":"2016-09-21 23:43:20.000000000","message":"I\u0027ll change this to administratively downing a NIC.","commit_id":"ce7293272395abbbb388d670d3fd08af331c76b6"}],"doc/networking-guide/source/deploy-lb-selfservice.rst":[{"author":{"_account_id":4656,"name":"Sean M. Collins","email":"sean@coreitpro.com","username":"scollins"},"change_message_id":"2e323dab618f8096fdfa73daf683f9efbd81b040","unresolved":false,"context_lines":[{"line_number":13,"context_line":".. note::"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"   The Linux bridge agent only supports the VXLAN overlay network"},{"line_number":16,"context_line":"   protocol."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Prerequisites"},{"line_number":19,"context_line":"~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8ec9b2_a4b586d1","line":16,"updated":"2016-09-13 18:04:02.000000000","message":"We may want to add a little something like \"GRE, Geneve, and other tunnel protocols are not currently supported\" just so that they understand that it\u0027s the only tunneling protocol supported - and that VLAN is still supported.","commit_id":"8135fbad51623b7c17c5a8ee96cfd908115fd34d"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"8463540cabe4573ee357079983f3bf79159f2f2f","unresolved":false,"context_lines":[{"line_number":13,"context_line":".. note::"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"   The Linux bridge agent only supports the VXLAN overlay network"},{"line_number":16,"context_line":"   protocol."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Prerequisites"},{"line_number":19,"context_line":"~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8ec9b2_651ee6bb","line":16,"in_reply_to":"7a8ec9b2_a4b586d1","updated":"2016-09-14 14:18:33.000000000","message":"Done","commit_id":"8135fbad51623b7c17c5a8ee96cfd908115fd34d"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"8bcd071b0158ec029bdc6e612f4f3cdfe2c91700","unresolved":false,"context_lines":[{"line_number":13,"context_line":".. note::"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"   The Linux bridge agent only supports the VXLAN overlay network"},{"line_number":16,"context_line":"   protocol."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Prerequisites"},{"line_number":19,"context_line":"~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8ec9b2_67f2a09c","line":16,"in_reply_to":"7a8ec9b2_a4b586d1","updated":"2016-09-13 18:29:01.000000000","message":"Done","commit_id":"8135fbad51623b7c17c5a8ee96cfd908115fd34d"},{"author":{"_account_id":4656,"name":"Sean M. Collins","email":"sean@coreitpro.com","username":"scollins"},"change_message_id":"2e323dab618f8096fdfa73daf683f9efbd81b040","unresolved":false,"context_lines":[{"line_number":724,"context_line":"Create initial networks"},{"line_number":725,"context_line":"-----------------------"},{"line_number":726,"context_line":""},{"line_number":727,"context_line":"FIXME a nearly limitless quantity of entirely virtual networks. For more"},{"line_number":728,"context_line":"the example creates two self-service networks that use SNAT/DNAT via"},{"line_number":729,"context_line":"virtual router to access the provider network. For more information on"},{"line_number":730,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8ec9b2_c4ba92c0","line":727,"updated":"2016-09-13 18:04:02.000000000","message":".. FIXME ?","commit_id":"8135fbad51623b7c17c5a8ee96cfd908115fd34d"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"8bcd071b0158ec029bdc6e612f4f3cdfe2c91700","unresolved":false,"context_lines":[{"line_number":724,"context_line":"Create initial networks"},{"line_number":725,"context_line":"-----------------------"},{"line_number":726,"context_line":""},{"line_number":727,"context_line":"FIXME a nearly limitless quantity of entirely virtual networks. For more"},{"line_number":728,"context_line":"the example creates two self-service networks that use SNAT/DNAT via"},{"line_number":729,"context_line":"virtual router to access the provider network. For more information on"},{"line_number":730,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8ec9b2_e7fdd06f","line":727,"in_reply_to":"7a8ec9b2_c4ba92c0","updated":"2016-09-13 18:29:01.000000000","message":"Reminders for myself. They\u0027ll go away before I remove the WIP.","commit_id":"8135fbad51623b7c17c5a8ee96cfd908115fd34d"}],"doc/networking-guide/source/figures/deploy-lb-ha-vrrp-overview.png":[{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"e7d16ccd2efc19815cd5110e2b2abdc519c70d87","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":10,"id":"3a98d1f4_f8918a53","updated":"2016-09-30 02:21:20.000000000","message":"In the \"Compute Nodes\" block it is not clear where the red lines from \"Interface 1\" are going. (There are similar diagrams in other sections.)","commit_id":"22b84b745b8bfa032337f5d67e220a788667dff3"},{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"fdae5ccb14c6ed2877b95361c93931d9ae112200","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":10,"id":"1a95cdbc_8aca3c4e","in_reply_to":"1a95cdbc_6aaa50d6","updated":"2016-10-04 23:36:27.000000000","message":"I think if you could route the lines around the boxes instead of under them it would be clearer. That might result in a messier overall look though.","commit_id":"22b84b745b8bfa032337f5d67e220a788667dff3"},{"author":{"_account_id":9515,"name":"Matthew Kassawara","email":"mkassawara@gmail.com","username":"ionosphere80"},"change_message_id":"ab2cd38a568bcf59d6db0a3e16046108de70fed3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":10,"id":"1a95cdbc_6aaa50d6","in_reply_to":"3a98d1f4_f8918a53","updated":"2016-10-04 23:16:10.000000000","message":"Those lines are trying to indicate that each agent has connectivity to the control plane via the management interface. I tried a variety of methods to make it more obvious and none of them work perfectly. Open to ideas!","commit_id":"22b84b745b8bfa032337f5d67e220a788667dff3"}]}