|
Well currently just a simple ldirectord.cf
quiescent = no
autoreload = yes
virtual = 1
real = web01:http masq
real = web02:http masq
real = web03:http masq
checktype = negotiate
service = http
virtualhost = "internal.myhost.com"
request = "check.php"
receive = "pass"
scheduler = wlc
protocol = fwm
I do use heartbeat as well. But I won't be for the initial setup in my
new cluster. Just a single box doing LVS. I'm wondering though if it
makes sense now to switch. Having notifications and fallback is the
only thing I'd like.
Of course, Googling "sorry server" and ldirectord didn't point out the obvious:
fallback = ip_address|hostname[:portnumber|sercvicename] [gate|masq|ipip]
the server onto which a webservice is redirected if all real servers
are down. Typically this would be 127.0.0.1 with an emergency page.
emailalert = "emailaddress"
A valid email address for sending alerts about the changed connection
status to any real server defined in the virtual service. This option
requires perl module MailTools to be installed. Automatically tries
to send email using any of the built-in methods. See perldoc
Mail::Mailer for more info on methods.
Duh. I don't remember seeing this before. I guess it already supports
both methods :)
On 11/26/07, Graeme Fowler <graeme@xxxxxxxxxxx> wrote:
> On Mon, 2007-11-26 at 02:26 -0800, mike wrote:
> > is there an easy way to implement the following:
>
> How are you managing your LVS?
>
> Graeme
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>
|
