)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"379e46376e207a79e64d636412bfacb0cd5ea0be","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4cda00ee_78bedc7d","updated":"2026-05-18 08:20:37.000000000","message":"| Missing Launchpad Blueprint reference — required for OpenStack spec tracking/approval\n\nNote: we don\u0027t use launchpad","commit_id":"bccc45c8b1d96f0754843a072fbe5027f8ad3d4b"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"5ab6cd977f9cba4f6a0665975ccefb5f3575a60e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b237abb5_752202b3","in_reply_to":"4cda00ee_78bedc7d","updated":"2026-05-18 08:25:30.000000000","message":"I\u0027ll try feeding that back into the agent for future spec reviews so it doesn\u0027t flag it again","commit_id":"bccc45c8b1d96f0754843a072fbe5027f8ad3d4b"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"07370f7ba2ed81f7de9970ed8db7940deea74439","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"58bfbc12_d0bc84e5","updated":"2026-05-20 15:22:42.000000000","message":"-1 for visibility","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"b36972a27f3c59aec4e08d4bbac233ba2dc85d99","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9c82ac29_218406e9","updated":"2026-05-19 09:03:46.000000000","message":"I\u0027ve a couple of questions below that might be good to clarify\n\nThe AI review bot also spotted some issues with the proposal (see my earlier comment). I think the issues around API and Data model changes can be ignored since we\u0027ve already got the proposed change for reference. I\u0027ll try to feed those back into the bot for future proposals\n\nThe issues spotted by CI will likely need to be fixed","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"362693ebe2e04b33cbb81caf52a453a91af1b402","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3c7b2c36_2abd7e9e","updated":"2026-05-24 22:48:11.000000000","message":"Hello, please update path to file:\nspecs/2026.2/multiaz_loadbalancer.rst","commit_id":"bf08c996dbdc8029f5a643d4617aae041010ebc0"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"53233e9ea4c4f3b06638d07436b43c7d5f130dd1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"a4de6f69_047665b3","in_reply_to":"3c7b2c36_2abd7e9e","updated":"2026-05-27 11:35:04.000000000","message":"Acknowledged","commit_id":"bf08c996dbdc8029f5a643d4617aae041010ebc0"}],"specs/version15.0/multiaz_loadbalancer.rst":[{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"d2e6aaa773464c1692e4ef73db41103b0150849f","unresolved":true,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Out of current scope."},{"line_number":55,"context_line":"This case should be discussed separately, because will make logic more complex:"},{"line_number":56,"context_line":"- new option for Loadbalancer on update: availability_zones"},{"line_number":57,"context_line":"  * with extra policy - may be should be hidden from users."},{"line_number":58,"context_line":"  * may be required re-creation Amphoras in new zones."},{"line_number":59,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"a6c25787_d8f0172d","line":56,"range":{"start_line":56,"start_character":33,"end_line":56,"end_character":39},"updated":"2026-05-20 15:24:44.000000000","message":"there\u0027s a lot of parameters that cannot be updated in a LB: flavors, AZs.\nI think it\u0027s fine if we don\u0027t implement it, maybe the future \"resize\" API could help us to mitigate it","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"6b4375cbce0fd4004e3aedeee253dd6131f2c003","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Out of current scope."},{"line_number":55,"context_line":"This case should be discussed separately, because will make logic more complex:"},{"line_number":56,"context_line":"- new option for Loadbalancer on update: availability_zones"},{"line_number":57,"context_line":"  * with extra policy - may be should be hidden from users."},{"line_number":58,"context_line":"  * may be required re-creation Amphoras in new zones."},{"line_number":59,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"b96a7968_ab312cfb","line":56,"range":{"start_line":56,"start_character":33,"end_line":56,"end_character":39},"in_reply_to":"a6c25787_d8f0172d","updated":"2026-05-20 18:34:49.000000000","message":"ok, I will re-phrase it, according this comment.","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"c0b071d88e05a9235557be0f851ae92e91b93d99","unresolved":true,"context_lines":[{"line_number":61,"context_line":"^^^^^^^^"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Loadbalancer with single amphora:"},{"line_number":64,"context_line":"- no miltizone AZs - validation error"},{"line_number":65,"context_line":"- 1 multizone AZ - will be used for creation"},{"line_number":66,"context_line":"- 2+ multizone AZs - will be randomly used one of AZs"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"08ed9580_73c74031","line":64,"range":{"start_line":64,"start_character":21,"end_line":64,"end_character":37},"updated":"2026-05-20 15:22:29.000000000","message":"do you mean validation error when multizone mode is enabled in the config, right?\nplease mention it explicitly in the spec like\n\nLoadbalancer with single amphora with multizone mode enabled","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"6b4375cbce0fd4004e3aedeee253dd6131f2c003","unresolved":false,"context_lines":[{"line_number":61,"context_line":"^^^^^^^^"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Loadbalancer with single amphora:"},{"line_number":64,"context_line":"- no miltizone AZs - validation error"},{"line_number":65,"context_line":"- 1 multizone AZ - will be used for creation"},{"line_number":66,"context_line":"- 2+ multizone AZs - will be randomly used one of AZs"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"64ebf35c_6b052530","line":64,"range":{"start_line":64,"start_character":21,"end_line":64,"end_character":37},"in_reply_to":"08ed9580_73c74031","updated":"2026-05-20 18:34:49.000000000","message":"yes. I will add it in topic of this section.","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"b36972a27f3c59aec4e08d4bbac233ba2dc85d99","unresolved":true,"context_lines":[{"line_number":106,"context_line":"- Amphora1 - AZ1, Amphora2 - AZ2"},{"line_number":107,"context_line":"- multizone AZs: AZ1, AZ2"},{"line_number":108,"context_line":"- failover: Amphora1 - will be re-created in AZ1, to avoid intersection with AZ2"},{"line_number":109,"context_line":"- failover: Amphora2 - will be re-created in AZ2, to avoid intersection with AZ1"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"** - such behaviour is done to avoid fail on failover due to some multizone"},{"line_number":112,"context_line":"configuration or maintaince works on AZs"}],"source_content_type":"text/x-rst","patch_set":2,"id":"0260905a_6087ab2a","line":109,"updated":"2026-05-19 09:03:46.000000000","message":"I wonder should this be a softer anti-affinity policy than what is here currently\n\nFor example\n\n1. AZ1 goes down - Amphora 1 is offline\n2. LB operates on Amphora 2 until AZ1 recovers\n3. Amphora 2 hit some issue\n4. Entire LB is down while Amphora 2 is rebuilt\n\nIt\u0027s an edge case, but a soft anti affinity policy would let Amphora1 be created in AZ2 until AZ1 is recovered, ensuring at least a degree of high availability","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"6b4375cbce0fd4004e3aedeee253dd6131f2c003","unresolved":false,"context_lines":[{"line_number":106,"context_line":"- Amphora1 - AZ1, Amphora2 - AZ2"},{"line_number":107,"context_line":"- multizone AZs: AZ1, AZ2"},{"line_number":108,"context_line":"- failover: Amphora1 - will be re-created in AZ1, to avoid intersection with AZ2"},{"line_number":109,"context_line":"- failover: Amphora2 - will be re-created in AZ2, to avoid intersection with AZ1"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"** - such behaviour is done to avoid fail on failover due to some multizone"},{"line_number":112,"context_line":"configuration or maintaince works on AZs"}],"source_content_type":"text/x-rst","patch_set":2,"id":"8a296af2_4fc44012","line":109,"in_reply_to":"0260905a_6087ab2a","updated":"2026-05-20 18:34:49.000000000","message":"Actually this soft option is already used in https://review.opendev.org/c/openstack/octavia/+/976100\n\nHowever your scenario requires manual disabling AZ or removing option \"use_in_multizone\". In this case algorithm will stop to schedule amphoras in this AZ.\n\nIt could not be done without manual change AZ status, because when amphora does not respond and we start failover Octavia does not know: it is issue with particular amphora (simple failover will fix it) OR it\u0027s issue with whole AZ. (that\u0027s why I prefer to add extra option for AZ - use_in_multizone)\n\nI will add one more example for this case","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"b36972a27f3c59aec4e08d4bbac233ba2dc85d99","unresolved":true,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"- Availability Zone has new option use_in_multizone, which identify, that zone"},{"line_number":152,"context_line":"could be used for creation Loadbalancer in multizone mode."},{"line_number":153,"context_line":"- New option availability_zones for Loadbalancer API, allows to ignore default"},{"line_number":154,"context_line":"multizone settings and create Loadbalancer in specified zones with amphora\u0027s"},{"line_number":155,"context_line":"distribution across specified AZs."},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"982558c5_56c7af09","line":153,"updated":"2026-05-19 09:03:46.000000000","message":"Would this replace the existing availability_zone in the AZ creation in the API? Or is it in addition to the current option?\n\nMy opinion would be to have both availability_zone and availability_zones as options, and in time we can roll them together and deprecate the original to make the API a bit easier to read","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"c0b071d88e05a9235557be0f851ae92e91b93d99","unresolved":true,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"- Availability Zone has new option use_in_multizone, which identify, that zone"},{"line_number":152,"context_line":"could be used for creation Loadbalancer in multizone mode."},{"line_number":153,"context_line":"- New option availability_zones for Loadbalancer API, allows to ignore default"},{"line_number":154,"context_line":"multizone settings and create Loadbalancer in specified zones with amphora\u0027s"},{"line_number":155,"context_line":"distribution across specified AZs."},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"c07479a4_1b0871b1","line":153,"in_reply_to":"982558c5_56c7af09","updated":"2026-05-20 15:22:29.000000000","message":"it\u0027s an addition, we cannot really rename/remove parameters from the API.","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"d10fe49fc05fedc1ec464f5b6b592e5ef6282ec8","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"- Availability Zone has new option use_in_multizone, which identify, that zone"},{"line_number":152,"context_line":"could be used for creation Loadbalancer in multizone mode."},{"line_number":153,"context_line":"- New option availability_zones for Loadbalancer API, allows to ignore default"},{"line_number":154,"context_line":"multizone settings and create Loadbalancer in specified zones with amphora\u0027s"},{"line_number":155,"context_line":"distribution across specified AZs."},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fc426014_2b1be9db","line":153,"in_reply_to":"c07479a4_1b0871b1","updated":"2026-05-20 15:45:08.000000000","message":"Acknowledged","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"6b4375cbce0fd4004e3aedeee253dd6131f2c003","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"- Availability Zone has new option use_in_multizone, which identify, that zone"},{"line_number":152,"context_line":"could be used for creation Loadbalancer in multizone mode."},{"line_number":153,"context_line":"- New option availability_zones for Loadbalancer API, allows to ignore default"},{"line_number":154,"context_line":"multizone settings and create Loadbalancer in specified zones with amphora\u0027s"},{"line_number":155,"context_line":"distribution across specified AZs."},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"f94073f7_58f69b98","line":153,"in_reply_to":"fc426014_2b1be9db","updated":"2026-05-20 18:34:49.000000000","message":"yes, it will be new option. As was suggested here: https://review.opendev.org/c/openstack/octavia/+/976100?tab\u003dcomments","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"aa41b896ac4dc27d60f7ba7562e57208bccc5e4d","unresolved":true,"context_lines":[{"line_number":203,"context_line":""},{"line_number":204,"context_line":"- Add multizone support for LB, Availability zones. (Admin part logic)"},{"line_number":205,"context_line":"- Add availability zones parameter support for loadbalancer API and flows."},{"line_number":206,"context_line":"- Add tempest tests"},{"line_number":207,"context_line":"- Update Octavia CLI and OpenstackSDK"},{"line_number":208,"context_line":"- Write Documentation"},{"line_number":209,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f876721_670e587a","line":206,"range":{"start_line":206,"start_character":6,"end_line":206,"end_character":19},"updated":"2026-05-20 14:38:10.000000000","message":"note: tempest runs by default on single node, which means that the devstack deployment has only one AZ (we need at least one compute node per AZ).\n\nOctavia has two-nodes jobs that can run tests with more than one compute node (they\u0027ll need to be adapted to define 2 AZs)","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"6b4375cbce0fd4004e3aedeee253dd6131f2c003","unresolved":false,"context_lines":[{"line_number":203,"context_line":""},{"line_number":204,"context_line":"- Add multizone support for LB, Availability zones. (Admin part logic)"},{"line_number":205,"context_line":"- Add availability zones parameter support for loadbalancer API and flows."},{"line_number":206,"context_line":"- Add tempest tests"},{"line_number":207,"context_line":"- Update Octavia CLI and OpenstackSDK"},{"line_number":208,"context_line":"- Write Documentation"},{"line_number":209,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"e8b86169_c0b384a7","line":206,"range":{"start_line":206,"start_character":6,"end_line":206,"end_character":19},"in_reply_to":"1f876721_670e587a","updated":"2026-05-20 18:34:49.000000000","message":"I will add this note to spec, if you don\u0027t mind. \nunfortunately, I am not enough familiar with such tempest details.","commit_id":"50647cb07bf08767a7b1da6191d431131a2dad7e"}]}