ubicloud/spec/prog/ai
Furkan Sahin fb7252a638 Update load balancer node according to specific stack state
We start using the stack information while configuring load balancing.
This way, if the ipv4 stack is up on a node while the ipv6 is down, it
keeps getting the traffic for ipv4 but not for ipv6.

More importantly, we are fixing a sneaky bug here. Previously, using
uniq on load_balancer.active_vm_ports collapsed multiple
load_balancer_vm_ports that shared the same load_balancer_port. This
caused traffic to be routed to only one node instead of multiple.
In some cases, it could even select the active VM’s own port, resulting
in an empty neighbor set and a total routing failure. The uniq property
was added to avoid an undeterministic bug which we solve here by sorting
on the stack column.
2025-11-10 15:20:15 +01:00
..
inference_endpoint_nexus_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00
inference_endpoint_replica_nexus_spec.rb Update load balancer node according to specific stack state 2025-11-10 15:20:15 +01:00
inference_router_nexus_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00
inference_router_replica_nexus_spec.rb Update load balancer node according to specific stack state 2025-11-10 15:20:15 +01:00
inference_router_target_nexus_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00