Project

General

Profile

Bug #78

Outgoing load balancer needs configuration upgrade

Added by Scott Ullrich almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Gateways
Target version:
Start date:
09/05/2009
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

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.

Associated revisions

Revision b5e8ddee (diff)
Added by Scott Ullrich over 9 years ago

Upgrade outgoing load balancing to gateway groups. Ticket #78

History

#1 Updated by Scott Ullrich over 9 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.

#2 Updated by Scott Ullrich over 9 years ago

  • Priority changed from Urgent to High

#3 Updated by Scott Ullrich over 9 years ago

  • Subject changed from RelayD code needs to be finished or removed before 2.0 to Outgoing loadb balancer needs configuration upgrade

#4 Updated by Scott Ullrich over 9 years ago

  • Subject changed from Outgoing loadb balancer needs configuration upgrade to Outgoing load balancer needs configuration upgrade

#5 Updated by Scott Ullrich over 9 years ago

  • Status changed from New to Feedback

Turns out the code was there! needed to change loadbalancer to load_balancer and now it works!

#6 Updated by Chris Buechler over 9 years ago

  • Category set to Gateways
  • Status changed from Feedback to New

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.

#7 Updated by Ermal Luçi over 9 years ago

  • Status changed from New to Feedback

As far as i can see it is being placed in the correct place.
If you see this again please update here.

#8 Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to New
  • Priority changed from High to Low

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.

#9 Updated by Ermal Luçi over 9 years ago

  • Status changed from New to Feedback

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.

#10 Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved

still an issue with monitor IP upgrade code (will open a new ticket) but the rest looks to be fine.

Also available in: Atom PDF