)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"517547e43b91cfa95dd3ac32eabe2722d4525b19","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4e10967c_92b2f13c","updated":"2024-03-05 08:21:39.000000000","message":"ping fellow reviewers","commit_id":"452802732908dedf5fe20c2c82f6d717af1b0f1e"}],"zuul.d/2023_2_jobs.yaml":[{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"5a42e5b82f4220b015cd9dd38e9b225346204054","unresolved":true,"context_lines":[{"line_number":209,"context_line":"          (^neutron_tempest_plugin.scenario.test_mtu.NetworkWritableMtuTest)\""},{"line_number":210,"context_line":"      devstack_localrc:"},{"line_number":211,"context_line":"        NETWORK_API_EXTENSIONS: \"{{ (network_api_extensions_common + network_api_extensions_ovn) | join(\u0027,\u0027) }}\""},{"line_number":212,"context_line":"      devstack_services:"},{"line_number":213,"context_line":"        q-ovn-metadata-agent: true"},{"line_number":214,"context_line":"        q-ovn-agent: false"},{"line_number":215,"context_line":"      devstack_local_conf:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"beca717b_44050a11","line":212,"updated":"2024-03-05 12:14:50.000000000","message":"wondering how the it will behave when both ovn-agent(with metadata extension) and ovn-metadata-agent enabled? if they conflict likely should be handle in deployment side.","commit_id":"452802732908dedf5fe20c2c82f6d717af1b0f1e"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"3462f65e9f6b6a1927dadf53dba4de93906008ba","unresolved":false,"context_lines":[{"line_number":209,"context_line":"          (^neutron_tempest_plugin.scenario.test_mtu.NetworkWritableMtuTest)\""},{"line_number":210,"context_line":"      devstack_localrc:"},{"line_number":211,"context_line":"        NETWORK_API_EXTENSIONS: \"{{ (network_api_extensions_common + network_api_extensions_ovn) | join(\u0027,\u0027) }}\""},{"line_number":212,"context_line":"      devstack_services:"},{"line_number":213,"context_line":"        q-ovn-metadata-agent: true"},{"line_number":214,"context_line":"        q-ovn-agent: false"},{"line_number":215,"context_line":"      devstack_local_conf:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"b52e8c2b_7583580f","line":212,"in_reply_to":"beca717b_44050a11","updated":"2024-03-06 07:08:33.000000000","message":"I would need to check the devstack side (I implemented) but so far there are no protections for this. Right now, the OVN agent with metadata extension is only an ongoing development. During the next cycle I\u0027ll propose to the community to deprecate the OVN metadata agent and move to the OVN agent (with metadata extension or any other one needed).\n\nIn any case:\n1) The OVN agent is still something not used.\n2) You can use both at the same time, but the OVN agent should not have the metadata extension.\n3) Yes, I should propose a patch (to devstack right now) to check that if \"q-ovn-metadata-agent\" is enabled and \"q-ovn-agent\" with the metadata extension too, fail somehow.","commit_id":"452802732908dedf5fe20c2c82f6d717af1b0f1e"}],"zuul.d/master_jobs.yaml":[{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"565b966c7b55aec9a3c6568931c3ed6ed5577e4c","unresolved":true,"context_lines":[{"line_number":626,"context_line":"        br-ex-tcpdump: true"},{"line_number":627,"context_line":"        br-int-flows: true"},{"line_number":628,"context_line":"        q-ovn-metadata-agent: false"},{"line_number":629,"context_line":"        q-ovn-agent: true"},{"line_number":630,"context_line":"        ovn-controller: true"},{"line_number":631,"context_line":"        ovn-northd: true"},{"line_number":632,"context_line":"        ovs-vswitchd: true"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"d53f9fa8_10cc73cf","line":629,"updated":"2024-02-22 16:45:24.000000000","message":"The original patch added a new job, but this one just always uses the ovn-agent, I think it would be good to keep testing both since downstream distros might not switch-over right away and it won\u0027t be tested now.","commit_id":"452802732908dedf5fe20c2c82f6d717af1b0f1e"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"8add4311aacd84fbb6c0ca6e6e468613cfa7e843","unresolved":false,"context_lines":[{"line_number":626,"context_line":"        br-ex-tcpdump: true"},{"line_number":627,"context_line":"        br-int-flows: true"},{"line_number":628,"context_line":"        q-ovn-metadata-agent: false"},{"line_number":629,"context_line":"        q-ovn-agent: true"},{"line_number":630,"context_line":"        ovn-controller: true"},{"line_number":631,"context_line":"        ovn-northd: true"},{"line_number":632,"context_line":"        ovs-vswitchd: true"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"c0919380_33a65e8f","line":629,"in_reply_to":"d53f9fa8_10cc73cf","updated":"2024-02-26 07:44:02.000000000","message":"After talking to Slawek, I realized that adding a new CI job to test only the OVN agent could be unnecessary. We are already testing the OVN metadata in \"neutron-ovn-multinode-base\" derived jobs and \"neutron-grenade-ovn\". Despite the complexity of the metadata agent, the functionality is quite simple and in case of not working, any test will fail.\n\nI would go for this proposal instead of creating an independent job and overloading the CI. I will update the Neutron patch.","commit_id":"452802732908dedf5fe20c2c82f6d717af1b0f1e"}]}