|
> No, but I'm sure if you post a specification how you imagine that such
> a server would work, that might help to find volunteers (nonono, this
> is not an offer, but I'm really curious).
sure, that's the easy part.. thanks for volunteering... >:)
Establish https connection to active box. I would imagine the shared IP
resource:443 would be the best way of doing this, but obviously there's
plenty of options here. I don't have a problem with controlled ssl access
to an LVS box.. (restrict ip access via ipchains and you should be ok..)
Functionality / GUI ideas :
- simple clean interface. keep things very simple at first and add
functionality that beta testers ask for. A few features I would imagine are
absolutely critical...
a.) removal / adding in of servers to a vip.
b.) 'syncing' the two boxes. (scp the .cf file to the other box, update
running config on standby).
c.) traffic view - show who's got what connections. Essentially 'ipvsadm
-L' with a toggle box for '-n' functionality.
d.) 'command line' functionality. provide an interface that lets you run
commands to the active node. This should be capable of being disabled for
security reasons.
'Cool' features that most of the commercial boxes don't have :
a.) make a 'network overview' button available so a graphical representation
of your boxes could be displayed. I foresee that this could be extended
into a "graphical trouble indicator" eventually.
b.) log file grepping in the gui. I think DoS/firewall logs would be
logical to include with things like heartbeat logs... et cetera! A button
to "add this log file" would be easy to do.. just make sure the user knows
what permissions she needs to add. Again, this should be configurable due
to security hazards.
|
