|
We've been working on a perl script that generates some of this
functionality...
Based on a couple of data files which contain information on the
director[s] and various http/https sites hosted on the LVS cluster, it
generates the following:
rc.lvs style script
heartbeat config
mon config
httpd.conf files for each real-server
hosts file for each real-server (required for SSL)
domains.sb (this is used by Cobalt RaQs to generate named files)
script for merging and sorting Apache logs from each real-server
script for adding/removing real-servers from the cluster
In addition we've written a couple of scripts to monitor the state of
the cluster, and sync web content across the cluster from a staging
server (is this what you mean by syncing the machines, I suspect not,
but I wasn't sure what .cf file you meant)
We're approaching a point where we're going to be ready to make this
stuff available, at the moment it's all text based (just cos we prefer
to work that way) but it wouldn't be too difficult to convert them to
CGI...
James
On 20 Jun 2001 12:21:03 -0700, Peter Mueller wrote:
> 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.
--
James Ogley, Unix Systems Administrator, Pinnacle.Net
james.ogley@xxxxxxxxxxxxxx www.pinnacle.co.uk +44 20 8731 3619
Listening for the sound of the coming rain...
***********************************************************************
CONFIDENTIALITY. This e-mail and any attachments are
confidential and may also be privileged. If you are not the
named recipient, please notify the sender immediately and
do not disclose the contents to another person, use it for any
purpose, or store or copy the information in any medium. Any
views expressed in this message are those of the individual
sender, except where the sender specifically states them to
be the views of Pinnacle Insurance Plc.
If you have received this e-mail in error please immediately
notify our Helpdesk on +44 (0) 20 8207 9555.
This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
|
