[NTLUG:Discuss] Web-server Farm - Networking Question
Chris Cox
cjcox at acm.org
Thu Jan 3 22:24:02 CST 2008
David Simmons wrote:
>
>> There are ways of handling web of course, but many protocols
>> don't really care about the name so much as the IP, and since
>> they would all have the same IP, most services couldn't be
>> made to be 'specific' to one VM or another.
>
> well......actually it can....grin
>
> Through a bunch of
> research, it appears that using 'mod_proxy' on Apache (with some
> mod_rewrite) rules would work. You have the host OS run a httpd
> session (with mod_proxy) - then it will do the redirects (based on host
> name) to the individual - private IP VMs....using mod_rewrite for the
> reverse lookups.
>
> Maybe that's what you're saying by 'there are
> ways of handling web'.....which is really the issue. Figured I could
> do ssh on different ports, etc.
Yes... well sort of. I mean you don't have to have mod_proxy, it's
more or less built into Apache to allow you to associate different roots
with different names (virtual hosting). We do it at work all the time
to handle "historical" stuff. Then you don't have to have more than
one VM... if all you're interested in is web. But as you said, you
can frontend it I suppose so that there is a real VM out there (purpose
unknown to me though).
I guess without knowing completely what you are wanting to accomplish
it's difficult to suggest a solution (?).
>
> In the end....a call for more
> IP address really seemed to be the most painless and direct.
Definitely. Just not always an option.
More information about the Discuss
mailing list