rek2 at binaryfreedom
Nov 8, 2007, 8:45 AM
Post #5 of 5
(252 views)
Permalink
|
>
> That's because, in the best traditions of Open Source solutions, there
> is no "one way" to do this. I'll recommend one thing, Joe might
> recommend another, Horms another, Nigel another, etc etc (names not
> changed to protect the guilty!)
>
>
of course I been using Free software since 1995(slackware)
>
> How about you put down a set of specifications and/or criteria to help
> us help you?
>
>
This is fair,
> The question you've asked is vague, to say the least. Do you want:
>
you are right, sorry I think I try cheap out on words because my first
language is Spanish.
is there a Spanish list? ;-)
> * Multiple redundant directors (load balancers)?
>
yes load balance is one of the things I will like to get out of this.
and if is redundant better or at least ready to add one later so it is.
> * Separate webservers, or run them on the director(s)?
>
3+ apache servers each on his own server(so 3 servers)
> * A NAS/SAN or clustered FS, or something more simple?
>
something more simple to start.. they only need to pull data from a
mysql db,
and the mysql will be doing replication..
> * To make your MySQL server highly available?
>
replication is working for me in other setups like this ok so far..
> * The whole shebang to be in one location, or spread around?
>
one location for now.
> Do you "own" (ie. have allocated to you) specific IP space that you
> control, or will you be using space on another provider's network?
>
we will have 3 ip's to play with one I was planning for the LVS front,
in the back I was looking into using the MASQ option to have a small lan
inside
I can setup openvpn on the LVS box to have straight access to those in
that lan behind LVS..
> There's a bazillion questions I could ask, but I won't. Simply asking
> for a recommendation for a vague concept (which is what you gave) isn't
> going to turn out any hard results, I'm afraid.
>
>
sorry :-)
> I'd also suggest that you get some conceptual practice in your lab/test
> network by following the basics in the HOWTO until you've got some
> rudimentary experience of LVS in practice. Until then, we're likely to
> use terminology you may not understand.
>
I am doing this, and don't worry about terminology..
basically I just need to know something like:
the howto will work for you, but add this solution... or this howto is
for simple setups..
use this other howto someone wrote and this is his homepage.. etc..
> Please don't be offended: it's easier for us to help you if you ask
> specific questions :)
>
No offense, you are right.
Chris F.
|
