)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"975f3ae0ad20e6f9a4eea33695f0847e24f4a390","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"af29b2df_a2d841cb","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"updated":"2026-02-11 07:35:11.000000000","message":"I think the key point will be how to configure it\n\nWe\u0027ve seen similar different proposals, and many different requests for a similar feature\nsome people want to be able to specify a list of AZs when creating a LB (for instance LB1 in az1 \u0026 az2, LB2 in az1 \u0026 az3), some even want to click on the desired AZs in horizon.\n\nI wonder if we can find a way to satisfy all those users.","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"dc2a03156558b8746711394b2acb5f8dcdffde31","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"69874ee1_f845e6e5","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"3221a629_13e9c855","updated":"2026-02-12 13:33:23.000000000","message":"we can discuss it with a wider team first (team meeting, or PTG if you can wait), I would prefer to get other folks\u0027 opinion on it.","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"5581dba700bbfc34c5575fd6881e69026d30034a","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"edd3574d_b5544794","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"69874ee1_f845e6e5","updated":"2026-02-12 13:35:02.000000000","message":"for this kind of changes, we usually ask people to write a spec to discuss the impact on the API, DB, and how it is integrated\n\nfor instance https://review.opendev.org/c/openstack/octavia/+/923571/8","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"026ead57fa46d4848fcbde3bd1f172553075a11e","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"e09fa0d2_3abe3ea0","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"91f6cd75_afb8482d","updated":"2026-02-12 09:53:47.000000000","message":"* if LB1 is in az1 \u0026 az2, only these 2 AZs will be used\n  if LB1 is in az1, az2 \u0026 az3, 2 of the AZs will be used (randomly), in case of failover, the 3rd AZ can be used too\n* so far I have no idea 😄\n\n\u003e several (2 or more) AZs specified\n\ncurrently I think we can only pass one Octavia AZ when creating a LB\nI don\u0027t know the impact of changing this in the API, but it would be easier to control by users.\n\nanother approach could be:\n- replace your use_in_multizone bool with a list of strings (a list of multizone names: mz1,mz2)\n- admin can decide: az1 is in mz1 and mz2, az2 in mz\u003cx\u003e etc...\n- then we need to find a way to pass a multizone name when creating a LB","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"4da418cc4c49a9cb79c07707ef818ee3ba7eb305","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"91f6cd75_afb8482d","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"af29b2df_a2d841cb","updated":"2026-02-11 08:19:29.000000000","message":"Sounds reasonable.\n- Does it means, that: LB1 in az1 \u0026 az2 - will always be in these two zones?\nshould it be able to failover amphora in az3 (if it\u0027s enabled for multizone generally, but not for particular LB) ?\n\n- Is this case with specification list of az via API preferred or I could combine it?\n\nPotentially it could be combined with current approach, like:\nif multizone enabled and not AZ specified - use logic proposed in this PR.\nif multizone enabled and one AZ specified - use old logic for backport combatibility.\nif multizone enabled and several (2 or more) AZs specified - use only these Zones for deploy LBs amphoras and ignore extra available zones.","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"55105a37cdde9a442a98111c74c1e7f5a78add84","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"848088d5_88abec50","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"ca603aa0_7315476b","updated":"2026-05-21 06:09:21.000000000","message":"Done","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"7670e1678afe4f2e95544261c0b7d7daf564be65","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"3221a629_13e9c855","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"e09fa0d2_3abe3ea0","updated":"2026-02-12 13:21:56.000000000","message":"got it. sounds good, I will try to add it and come back with changes.","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"82a90caf2b0ff4dcd8743aec583ead5c34c4892f","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Support deploy amphora in different availability zones"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- Added option to enable multizone deployment in Octavia config"},{"line_number":10,"context_line":"  Enabling this option changes behaviour for creation Amphora in"},{"line_number":11,"context_line":"  availability zones (more detailes below)."},{"line_number":12,"context_line":"- Added attribute for octavia availability zones, which indicates, that"},{"line_number":13,"context_line":"  AZ could be used in multizone deployment."},{"line_number":14,"context_line":"- Added attribute for amphora resource to indicate, which AZ was"},{"line_number":15,"context_line":"  calculated in multizone deployment."},{"line_number":16,"context_line":"- Added validation to create Loadbalancer with multizone enabled flag,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"ca603aa0_7315476b","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":43},"in_reply_to":"edd3574d_b5544794","updated":"2026-05-17 18:42:31.000000000","message":"Proposal is created now: https://review.opendev.org/c/openstack/octavia/+/988883\nHowever I did not add logic for API extra options for LB yet.\nI will try to do it during next week","commit_id":"96e8041dbab59ea3bff519f69589170cad784adb"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"89a6d05da2d89f65f01aea09828f69fa408a8748","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"41391c5b_ac9fde2f","updated":"2026-05-17 14:09:18.000000000","message":"@gthiemon@redhat.com hi, I added proposal referenced this PR.\nI also will try to update in short time this PR, according description in proposal and my last understanding how it works.","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"30b8942ff6bf5fc9e442a6a87c658b56e798e009","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"616eb55a_708c4801","updated":"2026-04-07 11:35:51.000000000","message":"Further to Greg\u0027s comments about specifying the AZ, I have an idea around how it can be done within the current change. We could provide a list of allowed AZs for either the amphora or LB via the API which is then stored in the DB. \n\nWhen deciding which AZ the Amphora will reside in, the allowed AZs list would act as a filter and constrain the selection to only the AZs the user wants. Within that, it is presumably allowed for the Amphora to reside on any AZ the user specified as long as anti-affinity is maintained between Master \u0026 Backup\n\nI\u0027ve provided a few suggestions around how it could work rather than creating another patch. @sergejyit@gmail.com, if you think it\u0027s worth pursuing I could try and propose a code patch into your change to do this?\n\nI like the idea that AZs can be specified as being multizone or not. There may be cases where an admin does not wish to allow an AZ to be included in a multizone setup even if the user tried to create a multizone amphora on that AZ","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"6572bd1af9746122ebc0f69d79540ddcf8e00cf1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"ce40821e_7b5ea192","updated":"2026-03-19 08:18:59.000000000","message":"I\u0027ve thought about this feature:\n\nwhat about adding an \"availability_zones\" attribute to the load balancer API?\n\nUsers would call POST /loadbalancer with\n{\n  \"availability_zones\": [\"az1\", az2\u0027]\n}\n\nwe would keep the existing \"availability_zone\" attribute (a string) for backward compat, so \"availability_zone\": \"az1\" would be the same as \"availability_zones\": [\"az1\"]\n\nit would be nicely integrated with octavia-dashboard, we would just update the choice box to a multi choice box for the AZs.\n\nWDYT about it?","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"4b3127b3e9cd393d58d55d453cd2e5811f41616c","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":9,"id":"efa6d9f8_46548dd9","in_reply_to":"6511fdfd_b662e1fa","updated":"2026-05-13 07:57:03.000000000","message":"Hi, Gregory. Thank you for reminder.\nI actually re-worked this MR, but without API for passing AZ on LB creation.\nAnd put it on pause due to different workloads. I want to prepare solution + proposal during weekend.\nAnd let you know status on the next week. I will be happy some help after it with finalizing/review.","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"7206ecd6e07b4b58654a9e80c9c12e37c65e167d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":9,"id":"f6595e2a_8fcc349b","in_reply_to":"ce40821e_7b5ea192","updated":"2026-03-23 10:39:19.000000000","message":"I think, that it\u0027s possible to do. \nHowever I\u0027d like also to support case, when AZs are not specified.\nFor example you are not familiar with existing zones and don\u0027t want to choose zones - you want to make sure, that zones will be different.","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"5a7e96deab64e867c93223f95d363fa805b3f32e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"601d93f3_756533cd","in_reply_to":"efa6d9f8_46548dd9","updated":"2026-05-27 11:35:36.000000000","message":"proposal: https://review.opendev.org/c/openstack/octavia/+/988883","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"974d8fb7e2e4eb16cbf0f15ecb25a0d0cd41d19b","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":9,"id":"6511fdfd_b662e1fa","in_reply_to":"f6595e2a_8fcc349b","updated":"2026-05-13 07:04:06.000000000","message":"ok so, having the possibility to:\n- explicitly select one or more AZs when creating a LB\n- implicitly create amphorae in AZs configured in \"multizone\" when creating a LB without passing AZs\n\nBTW are you still working on it? I really want to get this feature in the H release cycle, don\u0027t hesitate if you need help to implement the changes.","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"1f843bd930bf832926e2560bad57a6234771bbad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":10,"id":"6a7cd8f3_575d5440","updated":"2026-05-20 16:15:08.000000000","message":"recheck - pip install issue","commit_id":"b3b66756eb19fc2fc0c8f2b0a6e8f9148433516d"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"2cb74fff4d33920d0cc37a302955a3ad884b0e32","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":11,"id":"062ba9ff_724f4669","updated":"2026-05-21 07:52:35.000000000","message":"Hm. I have not idea why functional-py310 is failed, when 3.13 passed.\nand I could not load logs for this failed job. @gthiemon@redhat.com could you please give an advise what to do here?","commit_id":"153f39e2588794363542d13f3373ae84f8c54dec"},{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"985c7024c4b88e1df45911059bdc229798c116e6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":11,"id":"7e79a06e_97c9e51d","updated":"2026-05-25 14:28:10.000000000","message":"recheck - python 310 jobs have been removed","commit_id":"153f39e2588794363542d13f3373ae84f8c54dec"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"bd2ca7901e6a61d997a43c0b7d8f76ca4f6ea6b8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":11,"id":"6d1dfa54_3d384813","in_reply_to":"062ba9ff_724f4669","updated":"2026-05-21 08:32:49.000000000","message":"I\u0027ve just proposed a patch that removes the py310 jobs (3.11 is the minimal supported version)\nI hope it merges today","commit_id":"153f39e2588794363542d13f3373ae84f8c54dec"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"5a7e96deab64e867c93223f95d363fa805b3f32e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":11,"id":"f6b5af8c_859fd18d","in_reply_to":"6d1dfa54_3d384813","updated":"2026-05-27 11:35:36.000000000","message":"Acknowledged","commit_id":"153f39e2588794363542d13f3373ae84f8c54dec"}],"octavia/common/data_models.py":[{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"30b8942ff6bf5fc9e442a6a87c658b56e798e009","unresolved":true,"context_lines":[{"line_number":657,"context_line":"        self.image_id \u003d image_id"},{"line_number":658,"context_line":"        self.compute_flavor \u003d compute_flavor"},{"line_number":659,"context_line":"        self.availability_zone \u003d availability_zone"},{"line_number":660,"context_line":""},{"line_number":661,"context_line":"    def delete(self):"},{"line_number":662,"context_line":"        for amphora in self.load_balancer.amphorae:"},{"line_number":663,"context_line":"            if amphora.id \u003d\u003d self.id:"}],"source_content_type":"text/x-python","patch_set":9,"id":"d5269a32_d4afe31c","line":660,"updated":"2026-04-07 11:35:51.000000000","message":"I think we could add a parameter here called allowed_availability_zones where the user could pass in a list of specific AZs via the API when using multizone","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"55105a37cdde9a442a98111c74c1e7f5a78add84","unresolved":false,"context_lines":[{"line_number":657,"context_line":"        self.image_id \u003d image_id"},{"line_number":658,"context_line":"        self.compute_flavor \u003d compute_flavor"},{"line_number":659,"context_line":"        self.availability_zone \u003d availability_zone"},{"line_number":660,"context_line":""},{"line_number":661,"context_line":"    def delete(self):"},{"line_number":662,"context_line":"        for amphora in self.load_balancer.amphorae:"},{"line_number":663,"context_line":"            if amphora.id \u003d\u003d self.id:"}],"source_content_type":"text/x-python","patch_set":9,"id":"0bbb2020_17dab8cf","line":660,"in_reply_to":"8851a8b2_9037c642","updated":"2026-05-21 06:09:21.000000000","message":"Done","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"82a90caf2b0ff4dcd8743aec583ead5c34c4892f","unresolved":true,"context_lines":[{"line_number":657,"context_line":"        self.image_id \u003d image_id"},{"line_number":658,"context_line":"        self.compute_flavor \u003d compute_flavor"},{"line_number":659,"context_line":"        self.availability_zone \u003d availability_zone"},{"line_number":660,"context_line":""},{"line_number":661,"context_line":"    def delete(self):"},{"line_number":662,"context_line":"        for amphora in self.load_balancer.amphorae:"},{"line_number":663,"context_line":"            if amphora.id \u003d\u003d self.id:"}],"source_content_type":"text/x-python","patch_set":9,"id":"8851a8b2_9037c642","line":660,"in_reply_to":"d5269a32_d4afe31c","updated":"2026-05-17 18:42:31.000000000","message":"sure, @gthiemon@redhat.com mentioned the same.\nI want to combine currently provided approach with API option.\nThe idea is:\n- if not availability_zones option not specified for Lb - we use default logic for choosing AZs marked for miltizone\n- otherwise do the same logic but only on specified list of AZs (this list should be validated before for correctness )","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"}],"octavia/common/exceptions.py":[{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"30b8942ff6bf5fc9e442a6a87c658b56e798e009","unresolved":true,"context_lines":[{"line_number":454,"context_line":"    code \u003d 400"},{"line_number":455,"context_line":""},{"line_number":456,"context_line":""},{"line_number":457,"context_line":"class NotEnoughAvailabilityZonesWithUniqComputeZone(APIException):"},{"line_number":458,"context_line":"    msg \u003d _(\"Multizone deployment is enabled. Loadbalancer creation with \""},{"line_number":459,"context_line":"            \"%(topology)s topology requires at least %(count)s octavia AZ \""},{"line_number":460,"context_line":"            \"marked for using in multizone deployment. Currently enabled \""}],"source_content_type":"text/x-python","patch_set":9,"id":"a3f33130_c5722b91","line":457,"updated":"2026-04-07 11:35:51.000000000","message":"Typo? Should be Unique, not Uniq?","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"82a90caf2b0ff4dcd8743aec583ead5c34c4892f","unresolved":false,"context_lines":[{"line_number":454,"context_line":"    code \u003d 400"},{"line_number":455,"context_line":""},{"line_number":456,"context_line":""},{"line_number":457,"context_line":"class NotEnoughAvailabilityZonesWithUniqComputeZone(APIException):"},{"line_number":458,"context_line":"    msg \u003d _(\"Multizone deployment is enabled. Loadbalancer creation with \""},{"line_number":459,"context_line":"            \"%(topology)s topology requires at least %(count)s octavia AZ \""},{"line_number":460,"context_line":"            \"marked for using in multizone deployment. Currently enabled \""}],"source_content_type":"text/x-python","patch_set":9,"id":"a7878d8f_6ca1ebb2","line":457,"in_reply_to":"a3f33130_c5722b91","updated":"2026-05-17 18:42:31.000000000","message":"fixed","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"}],"octavia/controller/worker/v2/tasks/compute_tasks.py":[{"author":{"_account_id":38562,"name":"Richard Cruise","email":"rcruise@redhat.com","username":"rcruise"},"change_message_id":"30b8942ff6bf5fc9e442a6a87c658b56e798e009","unresolved":true,"context_lines":[{"line_number":211,"context_line":"            self.az_repo.get_availability_zone_name_to_profile_mapping("},{"line_number":212,"context_line":"                db_apis.get_session())"},{"line_number":213,"context_line":"        )"},{"line_number":214,"context_line":"        # handle case, when amphora already has AZ and AZ is enabled"},{"line_number":215,"context_line":"        if previous_amphora_az and previous_amphora_az in az_to_az_profile_map:"},{"line_number":216,"context_line":"            return previous_amphora_az, previous_amphora_az"},{"line_number":217,"context_line":"        compute_zone_to_azs \u003d utils.group_compute_zone_to_azs("}],"source_content_type":"text/x-python","patch_set":9,"id":"04319184_92a3b138","line":214,"updated":"2026-04-07 11:35:51.000000000","message":"So I think at this point you could add a check if the Amphora has allowed_availability_zones set and if so, reduce the az_to_az_profile_map to only the allowed AZs. Then below when the AZ is selected randomly, it will definitely be created within one of the allowed AZs","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"},{"author":{"_account_id":6577,"name":"Sergey Kraynev","email":"sergejyit@gmail.com","username":"skraynev"},"change_message_id":"82a90caf2b0ff4dcd8743aec583ead5c34c4892f","unresolved":false,"context_lines":[{"line_number":211,"context_line":"            self.az_repo.get_availability_zone_name_to_profile_mapping("},{"line_number":212,"context_line":"                db_apis.get_session())"},{"line_number":213,"context_line":"        )"},{"line_number":214,"context_line":"        # handle case, when amphora already has AZ and AZ is enabled"},{"line_number":215,"context_line":"        if previous_amphora_az and previous_amphora_az in az_to_az_profile_map:"},{"line_number":216,"context_line":"            return previous_amphora_az, previous_amphora_az"},{"line_number":217,"context_line":"        compute_zone_to_azs \u003d utils.group_compute_zone_to_azs("}],"source_content_type":"text/x-python","patch_set":9,"id":"d33fc01a_a99f0d8f","line":214,"in_reply_to":"04319184_92a3b138","updated":"2026-05-17 18:42:31.000000000","message":"I removed this complicated logic. Now logic is simplified to way, that AZ will be chosen randomly without extra pre-calculation","commit_id":"ff62fc823e30ba9cdb36b7398b1e839d163608f2"}]}