)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"513d951b42907ec10ba6f4c82267632341af3730","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a207a59b_75ffff81","updated":"2026-10-22 18:05:12.000000000","message":"Sorry for being late to the party :)","commit_id":"7bf9473d6dc71475181a536ffda6614edba734d1"}],"doc/source/admin/api-feature-matrix.rst":[{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"513d951b42907ec10ba6f4c82267632341af3730","unresolved":true,"context_lines":[{"line_number":202,"context_line":"   The in-tree OVN BGP and EVPN features overlap in scope with the external"},{"line_number":203,"context_line":"   `ovn-bgp-agent \u003chttps://opendev.org/openstack/ovn-bgp-agent\u003e`__ project,"},{"line_number":204,"context_line":"   and the project direction is to converge on the in-tree implementation."},{"line_number":205,"context_line":"   The in-tree implementation does not yet have full feature parity with"},{"line_number":206,"context_line":"   ``ovn-bgp-agent``; for example, VLAN provider network support is not yet"},{"line_number":207,"context_line":"   available in-tree. The ``leak_routes``, ``evpn_vni`` and"},{"line_number":208,"context_line":"   ``advertise_host`` attributes described above are the API surface that"},{"line_number":209,"context_line":"   configures the in-tree implementation."},{"line_number":210,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"eaa0cbd8_705733ae","line":207,"range":{"start_line":205,"start_character":3,"end_line":207,"end_character":21},"updated":"2026-10-22 18:05:12.000000000","message":"I would argue ovn-bgp-agent \"supports\" VLAN networks. What it does is that it essentially removes the tag and sends the traffic from the VLAN network to the fabric untagged. That means there is no segregation in the underlay and it relies on the IP cidrs not overlapping.","commit_id":"7bf9473d6dc71475181a536ffda6614edba734d1"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"101a9a517c7f52e40574a3cdd8f59b701ff0f667","unresolved":true,"context_lines":[{"line_number":202,"context_line":"   The in-tree OVN BGP and EVPN features overlap in scope with the external"},{"line_number":203,"context_line":"   `ovn-bgp-agent \u003chttps://opendev.org/openstack/ovn-bgp-agent\u003e`__ project,"},{"line_number":204,"context_line":"   and the project direction is to converge on the in-tree implementation."},{"line_number":205,"context_line":"   The in-tree implementation does not yet have full feature parity with"},{"line_number":206,"context_line":"   ``ovn-bgp-agent``; for example, VLAN provider network support is not yet"},{"line_number":207,"context_line":"   available in-tree. The ``leak_routes``, ``evpn_vni`` and"},{"line_number":208,"context_line":"   ``advertise_host`` attributes described above are the API surface that"},{"line_number":209,"context_line":"   configures the in-tree implementation."},{"line_number":210,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"87f9f1fc_a1e74690","line":207,"range":{"start_line":205,"start_character":3,"end_line":207,"end_character":21},"in_reply_to":"eaa0cbd8_705733ae","updated":"2026-10-22 19:16:54.000000000","message":"Yeah, guess I could have waited to push this - can you do a quick follow-up patch with this change?","commit_id":"7bf9473d6dc71475181a536ffda6614edba734d1"}]}