Added by Scott Ullrich about 15 years ago. Updated over 14 years ago.
0%
Description
Just tested upgrade outgoing and incoming load balancing from 1.2 -> 2.0.
It appears the only thing that needs upgrade code is outgoing load balancing.
Updated by Scott Ullrich almost 15 years ago
What appears to be left: upgrading configuration from 1.2 -> relayd
Bill mentioned one more area that might just be nuked before 2.0 but I am having trouble remembering it ATM.
Updated by Scott Ullrich almost 15 years ago
Updated by Scott Ullrich almost 15 years ago
Updated by Scott Ullrich almost 15 years ago
Updated by Scott Ullrich almost 15 years ago
Turns out the code was there! needed to change loadbalancer to load_balancer and now it works!
Updated by Chris Buechler almost 15 years ago
This has at least one issue still. On config upgrade, the monitor IP is added to the interface configuration, where it needs to be under the appropriate gateway_item instead, as monitor IPs are associated with gateways, not interfaces. The gateways page doesn't use the imported monitor IP since it's not in the right place in the config.
Updated by Ermal Luçi almost 15 years ago
As far as i can see it is being placed in the correct place.
If you see this again please update here.
Updated by Chris Buechler almost 15 years ago
The monitor IPs are still added to the interface rather than the gateway_item, which is wrong.
Low priority for the immediate future though, as it only affects upgrades.
Updated by Ermal Luçi almost 15 years ago
monitor ips can reside even in the interfaces.
For dynamic gateways that is the place where they get stored but even the ones used for gateway_items can read the monitor ip from the interfaces.
Updated by Chris Buechler over 14 years ago
still an issue with monitor IP upgrade code (will open a new ticket) but the rest looks to be fine.