)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13686,"name":"Frode Nordahl","email":"fnordahl@ubuntu.com","username":"fnordahl"},"change_message_id":"eecc47dd74cf484e8a8638e034e2a93de6c0baaa","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"bdc070a0_22bfb8dd","updated":"2023-03-07 09:15:55.000000000","message":"Thank you for this proposal. Do I understand you correctly that you intention is to replace Neutron\u0027s use of the OVN LRP Gateway_Chassis column with the OVN LRP HA_Chassis_Group column and associated tables?\n\nIf that is the case, why would this change be introduced as a separate `ovn_l3_scheduler`?\n\nRegardless of using the Gateway_Chassis or HA_Chassis_Group mechanism to implement HA, the end user would still have opinions about how the load is spread across the chassis in the cloud?\n\nWould it be more appropriate to introduce a new configuration option which decides whether the Gateway_Chassis or HA_Chassis_Group mechanism should be used, and teach the existing scheduler classes to deal with both?\n\nThe existing `sync_ha_chassis_group` method appears to be hard coded to a chance-like scheduler ref: https://github.com/openstack/neutron/blob/2d2881d31f7d444b654dbb602fdae426e68bf286/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#L509-L515","commit_id":"a96dba653a97f1628490c3a1b36e19795b6035ff"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"bea1c7059ed3f6607dc1d95487e2fc3068d08e58","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"4dc0ac49_f8ec5eef","in_reply_to":"bdc070a0_22bfb8dd","updated":"2024-02-09 09:18:09.000000000","message":"I don\u0027t think so. Both are scheduler methods and OVN has both methods to schedule the LRPs among the GW chassis. The L3 scheduler should be aware of it and have an independent scheduler.","commit_id":"a96dba653a97f1628490c3a1b36e19795b6035ff"}],"neutron/services/ovn_l3/plugin.py":[{"author":{"_account_id":34340,"name":"shanyunfan33","display_name":"shanyunfan","email":"shanyunfan@inspur.com","username":"shanyunfan","status":"working"},"change_message_id":"cccf58cac8d28fc13a8160d38556525929e16d15","unresolved":true,"context_lines":[{"line_number":407,"context_line":"                    pass"},{"line_number":408,"context_line":"            return ports_impacted"},{"line_number":409,"context_line":""},{"line_number":410,"context_line":"        def lrp_from_ha_chassi_group():"},{"line_number":411,"context_line":"            pass"},{"line_number":412,"context_line":""},{"line_number":413,"context_line":"        # GW ports and its physnets."}],"source_content_type":"text/x-python","patch_set":8,"id":"2cf75848_4712c974","line":410,"updated":"2023-03-27 09:31:01.000000000","message":"Spelling errors, should it be lrp_from_ha_chassis_group?","commit_id":"19dd6258f8185e93be70e10b4691413a594da1f9"}]}