)]}'
{"doc/source/admin/ovn/router_availability_zones.rst":[{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":120,"context_line":".. end"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"When scheduling the gateway ports of a router, the OVN driver will take"},{"line_number":123,"context_line":"in consideration the router availability zones and make sure that the"},{"line_number":124,"context_line":"ports are scheduled on the nodes belonging to those availability zones."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Note that in the router object we have two attributes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_2fcdab65","line":123,"range":{"start_line":123,"start_character":0,"end_line":123,"end_character":2},"updated":"2020-06-04 10:08:13.000000000","message":"nitnit: should this be into?\nI\u0027m not a native English speaker so perhaps it\u0027s all good and I\u0027m just used to \u0027into consideration\u0027 :)","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":120,"context_line":".. end"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"When scheduling the gateway ports of a router, the OVN driver will take"},{"line_number":123,"context_line":"in consideration the router availability zones and make sure that the"},{"line_number":124,"context_line":"ports are scheduled on the nodes belonging to those availability zones."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Note that in the router object we have two attributes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_daccafbc","line":123,"range":{"start_line":123,"start_character":0,"end_line":123,"end_character":2},"in_reply_to":"ff570b3c_2fcdab65","updated":"2020-06-04 10:47:25.000000000","message":"I think you are right","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":137,"context_line":"This distinction makes more sense in the **ML2/OVS** driver"},{"line_number":138,"context_line":"where it tries to schedule the router namespace according to the"},{"line_number":139,"context_line":"``availability_zone_hints`` attribute. After the resource is scheduled,"},{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_6fc32339","line":140,"range":{"start_line":140,"start_character":27,"end_line":140,"end_character":37},"updated":"2020-06-04 10:08:13.000000000","message":"s/attributes/attribute ?","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":137,"context_line":"This distinction makes more sense in the **ML2/OVS** driver"},{"line_number":138,"context_line":"where it tries to schedule the router namespace according to the"},{"line_number":139,"context_line":"``availability_zone_hints`` attribute. After the resource is scheduled,"},{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_fac9b3ab","line":140,"range":{"start_line":140,"start_character":27,"end_line":140,"end_character":37},"in_reply_to":"ff570b3c_6fc32339","updated":"2020-06-04 10:47:25.000000000","message":"Done","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_8fe157d3","line":143,"range":{"start_line":143,"start_character":23,"end_line":143,"end_character":33},"updated":"2020-06-04 10:08:13.000000000","message":"attribute","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_0fcd475c","line":143,"range":{"start_line":143,"start_character":40,"end_line":143,"end_character":51},"updated":"2020-06-04 10:08:13.000000000","message":"in **ML2/OVN**","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_bad3bb5f","line":143,"range":{"start_line":143,"start_character":40,"end_line":143,"end_character":51},"in_reply_to":"ff570b3c_0fcd475c","updated":"2020-06-04 10:47:25.000000000","message":"Done","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_9ad6b74e","line":143,"range":{"start_line":143,"start_character":23,"end_line":143,"end_character":33},"in_reply_to":"ff570b3c_8fe157d3","updated":"2020-06-04 10:47:25.000000000","message":"Done","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"OVN Database information"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_8ff4b75c","line":146,"range":{"start_line":143,"start_character":35,"end_line":146,"end_character":48},"updated":"2020-06-04 10:08:13.000000000","message":"This whole paragraph is a bit confusing to me. The namespaces thing is perhaps creating the confusion as it doesn\u0027t seem totally relevant for the point made here IMHO (and/or I see it as an implementation detail).\n\nThe fact that ovn-controller is acting as the \"L3 agent\" and deployed everywhere is what makes them always match, right?\n\nIn the ML2/OVS case it could happen that L3 agent is not deployed on a given availability zone but this is not possible with ML2/OVN as ovn-controller must be deployed everywhere. It can also happen that ovn-controller is not alive but this is another story :)\n\nWhat do you think?","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"OVN Database information"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_cf006f69","line":146,"range":{"start_line":146,"start_character":6,"end_line":146,"end_character":10},"updated":"2020-06-04 10:08:13.000000000","message":"again it sounds better without the \u0027with\u0027 to me but I may be wrong :)","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":140,"context_line":"the ``availability_zones`` attributes is populated with the **real**"},{"line_number":141,"context_line":"information about those namespaces placement. That means that in"},{"line_number":142,"context_line":"**ML2/OVS** the ``availability_zone_hints`` not always will match with the"},{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"OVN Database information"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_baa29bac","line":146,"range":{"start_line":143,"start_character":35,"end_line":146,"end_character":48},"in_reply_to":"ff570b3c_8ff4b75c","updated":"2020-06-04 10:47:25.000000000","message":"My thinking here was like one router \u003d\u003d a namespace. But I think that your argument is simpler to understand so I will change it. Thanks :D","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":143,"context_line":"``availability_zones`` attributed. But, **ML2/OVN** there\u0027s no concept"},{"line_number":144,"context_line":"of an *L3 agent* and there are no router namespaces being scheduled"},{"line_number":145,"context_line":"on certain nodes so, the ``availability_zone_hints`` will **always**"},{"line_number":146,"context_line":"match with the ``availability_zones`` attribute."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"OVN Database information"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_1acc6787","line":146,"range":{"start_line":146,"start_character":6,"end_line":146,"end_character":10},"in_reply_to":"ff570b3c_cf006f69","updated":"2020-06-04 10:47:25.000000000","message":"Done","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":149,"context_line":"OVN Database information"},{"line_number":150,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"In order to check which availability zones of the routers"},{"line_number":153,"context_line":"via the OVN Northbound database, one can look for the"},{"line_number":154,"context_line":"``neutron:availability_zone_hints`` key in the ``external_ids``"},{"line_number":155,"context_line":"column for the entries in the ``Logical_Router`` table:"},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_af2c1b02","line":153,"range":{"start_line":152,"start_character":0,"end_line":153,"end_character":31},"updated":"2020-06-04 10:08:13.000000000","message":"In order to check the availability zones of a given router ..?","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":149,"context_line":"OVN Database information"},{"line_number":150,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"In order to check which availability zones of the routers"},{"line_number":153,"context_line":"via the OVN Northbound database, one can look for the"},{"line_number":154,"context_line":"``neutron:availability_zone_hints`` key in the ``external_ids``"},{"line_number":155,"context_line":"column for the entries in the ``Logical_Router`` table:"},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_ba38db9f","line":153,"range":{"start_line":152,"start_character":0,"end_line":153,"end_character":31},"in_reply_to":"ff570b3c_af2c1b02","updated":"2020-06-04 10:47:25.000000000","message":"So many typos. Thanks for the suggestion.","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":23804,"name":"Daniel Alvarez","email":"dalvarez@redhat.com","username":"dalvarez"},"change_message_id":"2b1ac3df5f3413b5164930ecb20362746fee1700","unresolved":false,"context_lines":[{"line_number":181,"context_line":".. end"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"As mentioned in the `Using router availability zones`_ section, the"},{"line_number":184,"context_line":"scheduling of the gateway router ports will take in consideration the"},{"line_number":185,"context_line":"availability zones that the router belongs to. We can confirm this"},{"line_number":186,"context_line":"behavior by looking in the ``Gateway_Chassis`` table from the OVN"},{"line_number":187,"context_line":"Southbound database:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_2f400ba5","line":184,"range":{"start_line":184,"start_character":49,"end_line":184,"end_character":51},"updated":"2020-06-04 10:08:13.000000000","message":"ditto","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"f9377fedb3722fea6970468211a42d4a73db233b","unresolved":false,"context_lines":[{"line_number":181,"context_line":".. end"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"As mentioned in the `Using router availability zones`_ section, the"},{"line_number":184,"context_line":"scheduling of the gateway router ports will take in consideration the"},{"line_number":185,"context_line":"availability zones that the router belongs to. We can confirm this"},{"line_number":186,"context_line":"behavior by looking in the ``Gateway_Chassis`` table from the OVN"},{"line_number":187,"context_line":"Southbound database:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff570b3c_5ab89f0f","line":184,"range":{"start_line":184,"start_character":49,"end_line":184,"end_character":51},"in_reply_to":"ff570b3c_2f400ba5","updated":"2020-06-04 10:47:25.000000000","message":"Done","commit_id":"d539b6d0b9b83bd297b6e98bf3674dbddd6594b6"}]}