Hello Emilio,
Some may have already been requested but here are some ideas:
- For L4 farm, being able to see the association when persistence is
enabled. (just like it's possible with TCP farm) - I guess a readable
version of files /proc/net/xt_recent/ should do. Currently I have a
script which display like this:
192.168.68.126.....................................jeudi 22 mai 2014,
08:46:41 (UTC+0200)
192.168.65.174.....................................jeudi 22 mai 2014,
08:36:49 (UTC+0200)
192.168.65.108.....................................mardi 20 mai 2014,
15:13:51 (UTC+0200)
192.168.20.52......................................mardi 20 mai 2014,
17:47:44 (UTC+0200)
192.168.32.46......................................jeudi 22 mai 2014,
07:55:12 (UTC+0200)
But that would be conveniant to have this in the GUI. Beware the
last_seen time in the /proc/net/xt_recent/ files are written in jiffies
and the value a jiffies can be different on each system.
root@VMWZLB003:~# grep ^jiffies /proc/timer_list ; sleep 1 ; grep
^jiffies /proc/timer_list
jiffies: 314132146
jiffies: 314132396
> So on my system there is 250 jiffies per seconds. On the other
cluster node, there are 251 ...
root@VMWZLB004:~# grep ^jiffies /proc/timer_list ; sleep 1 ; grep
^jiffies /proc/timer_list
jiffies: 314213340
jiffies: 314213591
- For all farms: Be able to manually clear an association between client
and server when persistence is enabled.
- For L4 farm: Be able to put a a backend in maintenance mode
- For L4 farm: The rrd graph does not work (But I think you already said
it would be corrected to next version?)
- For all farms: Be able to configure firewall/ACL to restrict access (I
think it was already requested)
- For all farms: Be able to activate some global and/or selective
(ip-port based) tracing/debug. Something like you can have on commercial
product (not only LB) that explains, textualy what the appliance has
seen and what decision was taken. ie:
# received a packet from IP x.x.x.x for y.y.y.y port W
# matching farm "farm name" (or: no farm matched -> packet dropped)
# accepted (or not) due to firewall restrictions
# looking at persistence table: match found (or no match found)
# create a new persistence entry (if no match found previously)
# forward to server ABC on port Q
# and blablabla, you see what I mean :-)
- General: some kind of granular access for the admin gui. RW or RO on
all or selected items.
Thanks
tibz
On 22/05/2014 08:46, Emilio Campos wrote:
Hi Zen Masters, we are working on detect the planning list for the new
version of Zen Load Balancer Community Edition , so suggestions and
wishes are welcome
It is expected a high colaboration by the community for this new release!
Thank you guys!
--
Load balancer distribution - Open Source Project
http://www.zenloadbalancer.com
Distribution list (subscribe):
[email protected]
<mailto:[email protected]>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
