)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"c231878b67c8ade780a8e9bcabd1499a0e80297c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"3ac89ac0_b9a78259","updated":"2025-07-10 09:07:44.000000000","message":"I\u0027m not convinced yet, but maybe wait for what gmaan says about this","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"895ba77faaf1f564201a6c403bd86d0f3db85406","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ce0c3c79_9abe5f03","updated":"2025-07-10 05:32:22.000000000","message":"if the metadata agent is getting deprecated now, it cannot be removed earlier than 2026.2. I would suggest to leave testing it in grenade in place until then to ensure that existing deployments are not getting broken","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"da8a64cf5a66f9d8d6c2f21e40d058c8f76f7271","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"13b64731_eb10d9d3","updated":"2025-07-02 20:07:36.000000000","message":"lgtm","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"e6eb85b57777efdffe741629ce75c47bf9be9b4c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c7231ed4_c2739b44","updated":"2025-07-09 14:36:05.000000000","message":"ping fellow reviewers","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"efcf830b7d1d9288918e96f210311d3504d93989","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2e09cb34_dcbc808d","updated":"2025-06-27 11:41:05.000000000","message":"recheck openstack-tox-docs","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"511f1b823e0c5d768239200a780bfa1e5274a3c1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"459aaa25_c9d511f6","in_reply_to":"207c6606_c0c8d800","updated":"2025-07-18 11:27:08.000000000","message":"I\u0027ve added the following patches:\n* https://review.opendev.org/c/openstack/devstack/+/955187. This patch allows a grenade job to set this new variable that will replace the OVN Metadata agent with the OVN agent.\n* https://review.opendev.org/c/openstack/devstack/+/955348. There is a bug in grenade, we are not stopping/starting the OVN agents","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"832085c20d809a57085643cac0332f0b8ab7a338","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"831298ae_e48e71c6","in_reply_to":"6ee79f6c_79c088b4","updated":"2025-07-10 08:10:35.000000000","message":"--\u003e https://review.opendev.org/c/openstack/neutron/+/954567","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"c231878b67c8ade780a8e9bcabd1499a0e80297c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b5081b5d_324cf94f","in_reply_to":"831298ae_e48e71c6","updated":"2025-07-10 09:07:44.000000000","message":"I would still prefer to make this change only one cycle after the corresponding change has been made in devstack. another option would be to deploy the old side with the metadata agent and then migrate to the OVN agent during the upgrade? that would maybe be a better match for what one could expect to happen in real deployments, but I\u0027m not sure how complicated that would be.","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"798a97488056c40f7c5eb005418b57cc013f10c6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e3a70537_1281623f","in_reply_to":"b5081b5d_324cf94f","updated":"2025-07-11 16:36:02.000000000","message":"Usually/by default, testing what is latest recommended and not the deprecated one. Having deprecated things tested in some job (periodic is fine). Having a separate job testing metadata agent on 2025.2 test the same things that 2025.2 works fine for metadata agent as well as agent so upgrades are tested indirectly here. That is why I am ok with this change and we do not need to wait for one more cycle for greande testing.\n\nBut I think Frickler\u0027s request to test upgrade within the grenade job (old with metadata agent and new with agent) is as close to testing how a real deployment will be done. If that can be done, it\u0027s perfect; otherwise, I am ok with the current way of separate job also.","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"7103ca122dd40c60f2c4ae1e6035be1ed26098ec","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f182312c_6fad98a7","in_reply_to":"ce0c3c79_9abe5f03","updated":"2025-07-10 06:58:23.000000000","message":"In the Neutron CI we are still running a job using the OVN metadata agent [1] in the periodic queue.\n\nI\u0027ll create a job here in grenade using the OVN Metadata agent and running in the Neutron periodic queue. Is that enough?\n\n[1]https://review.opendev.org/c/openstack/neutron/+/953403/4/zuul.d/base.yaml#264","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"aa1241eb09a6fec79843350abcb07008e4fc15ef","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e8626d5c_d14c5dda","in_reply_to":"e3a70537_1281623f","updated":"2025-07-14 08:11:17.000000000","message":"I\u0027ll check if that is possible. I\u0027ll update this thread.","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"daa88a1ba344fdd7d8852e463921ed4e05adac05","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"207c6606_c0c8d800","in_reply_to":"e49681e3_7b85e688","updated":"2025-07-14 17:58:29.000000000","message":"sounds good to me. one suggestion for naming-  \u0027TARGET_ENABLE_OVN_AGENT\u0027 so that we know this is effective on target branch only.","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"5a1984d453066c9409d6370e9fefdf567a31a12a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e49681e3_7b85e688","in_reply_to":"e8626d5c_d14c5dda","updated":"2025-07-14 10:42:21.000000000","message":"Hi folks, same as I commented in the qa channel: my suggestion is to add a temporary configuration variable, in particular for \"new\". Something like ENABLE_OVN_AGENT. This variable will setup the OVN agent and disable the OVN Metadata agent. This is the only way I found to provide this upgrade capability in grenade.\nThis variable will be (only) used in a Neutron CI job that will be executed in the periodic queue (reviewed all weeks in the CI meeting).\nThis variable will be removed in 2026.2.","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"7123dfaa465bddbb0f3e8f89bc1fb3acfbf62e47","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6ee79f6c_79c088b4","in_reply_to":"f182312c_6fad98a7","updated":"2025-07-10 07:39:40.000000000","message":"qq: is ok if I implement this grenade job only in the Neutron repo??","commit_id":"4fd6b1492bc48440ac909769450650c0ca7c667b"}]}