|
Hi everyone.
I'm looking at LVS as a cost effective way to have high uptime and
scalability. I'm going to start out with a simple setup of 1 load
balancer and 2 real servers. I've tried to read as much of the LVS
documentation as I can without actually having the servers already to
try stuff out on. My brain can only hold so much raw info without
frying. Hopefully I can get my servers soon and start unloading some of
this info by testing things out. But before I order my servers I want to
make sure this is going to work for me. There are some questions that I
have that I wasn't able to answer by reading the docs.
One thing I'm very confused about is how to set up Apache when using
LVS. We host multiple websites with IP based hosting (not name based
because SSL only works with IP based) so each hostname that we host has
its own IP address. Since the real servers will have real IPs of
192.168.1.2 and 192.168.1.3, how will I set up my apache.conf? Should
apache.conf still be set up as if it was the main IP for the domain, or
should it use its new internal IP? What about for multiple domains and
multiple IPs? Do you understand what I'm confused about? Because trying
to explain my confusion just causes more confusion for me. :)
What problems will I run into when trying to run a mail server on both
of the real servers? Should I forward pop3/smtp ports to just one server
instead trying to load balance it? Should I be concerned about this?
I already know I'm going to run into trouble with MySQL since I do a lot
of updates and inserts on the tables. I think my solution with this is
going to be to rewrite all of my php scripts to use just one server as
the master and the other will act as the slave and receive the updates
through mysql's own replication features.
I'd like to be able to access all of the real servers independently from
the internet for administration purposes. So I'm going to buy servers
with dual network cards and have one of the network cards plugged into
the hub/lan and one of them accessing the internet. I don't assume there
will be any problems with this as the public IP is only going to be used
for SSH access and I won't be using it for apache.
Anyway, I think that covers most of the issues that are bugging me.
Thanks for any comments/advice anyone can give me.
- Doug
|
