LVS/Piranha in RH 8.0 or 7.3 components and steps
"Sumesh" <[email protected]>
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <[email protected]> |
Hi Peter, Sebastien,
I am little bit confused now, about where the problem lies.
First of all, if any one could give straight forward steps for implementing
Load balancing cluster with Apache since you are witnessed it is running.
I am afraid the How-to docs creates confusion to new users.Please summarize
the steps to implement in RedHat Errata kernel 7.3 +Piranha+Apache and RedHat 8.0+
Piranha+Apache.If not both, kindly give me any one of it.Please specify the locations from where
I could download the components used in your working setup.
Expecting the help at your earliest convenience as time is short for me.
Thanks a million for your great support !!!
Sumesh
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of pb
Sent: Wednesday, April 23, 2003 10:27 PM
To: [email protected]
Subject: Re: LVS in RedHat 8.0 - required components
> I wouldn't suggest using your rc.lvs because of
> several points :
> * it uses ipvsadm whereas it shouldn't (it piranha's
> role)
> * it mixes virtual server commands, filtering
> commands, routing commands
> * it starts daemons which do have initscripts
Right, one could do it in initscripts or with the rc
script (and the initscripts disabled). Matter of
choice. Works both ways. The rc.lvs script puts it all
together and gives you an overview of all that is
needed to make it work. Using ipvsadm for setting up
the NAT routing table works well, and Piranha later
adjusts the NAT table. I like seeing the table
present before piranha, so I can see how Piranha
affects it.
> Form my point of view:
> * everything related to iptables should be moved to
> /etc/sysconfig/iptables and the iptables service
> should be activated
> * sysctl variables should be set in /etc/sysctl.conf
> only
> * no ipvsadm stuff, piranha will manage it by
> itself, just activate the
> pulse service
> * piranha-gui is also a service, activate it
The rc.lvs script puts in altogether into one place,
one script, so it is easy to understand, esp. for
beginners to Piranha. Pre-setting the NAT table with
ipvsadm is matter of choice for me. It has worked
very well for me in real life for over a year.
> > Also, if you're users are using http to get to a
> LOGIN webpage, you
> > also have to consider adding persistance = 900 to
> your lvs.cf for
> > http service, but that is another story.
>
> This is based on the assumption that session
> tracking is real server
> bound, which is obviously and fortunately not always
> true. Just think DB
> or file sharing.
It is true in that we have had an issue with webmail
login, and setting persistance = 900 fixed it. What
can I say? Real life situation, real fix.
> > Since you are starting "lvs" daemon by executing
> the "pulse" daemon
> > (which is also true in my rc.lvs script)
>
> It's not ! The uncommented line is :
> /usr/sbin/lvs --configfile=/etc/sysconfig/ha/lvs.cf
The PIRANHA daemon does start the lvs daemon which
starts the nanny daemons. The example rc.lvs script
has options which can be commented or uncommented (the
script even says so):
# Run lvs mannually or uncomment. This will also spawn
nanny daemons.
# Or let pulse daemon start lvs and nanny and
networking, and comment
# out the lvs statement.
# /usr/sbin/pulse
# /usr/sbin/pulse --forceactive
/usr/sbin/lvs --configfile=/etc/sysconfig/ha/lvs.cf
Peter
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
_______________________________________________
Piranha-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/piranha-list