Ahh yes...
So one option is to make webtest be a passthrough to the app servers,
and then have all the actual content creation and storage happen on
the app servers. That'd still require synchronizing content across
multiple servers, but it'd be more manageable and elegant perhaps.
Right now we have a decent setup for handling database-driven
content, but not a great way of managing the tons of static content
that is out there waiting to be made available.
Us infrastructure types can get together at our regular IRC meeting
time and chat about this and other items.
Best,
-- Elliot
On May 24, 2006, at 15:52, Patrick W. Barnes wrote:
On Wednesday 24 May 2006 14:21, Karsten Wade <kwade@xxxxxxxxxx> wrote:
On Thu, 2006-05-18 at 14:55 -0400, Elliot Lee wrote:
On Tue, 16 May 2006, Karsten Wade wrote:
FWIU, there is a load-sharing server in front of webtest.fedora
that is
not mirrored. This is the reason that we cannot get content to
appear
correctly in http://webtest.fedora.redhat.com/docs/.
Can this be fixed? Is there anything I/we can do to help?
Define "mirrored"?
I was hoping Patrick or Tommy would reply, since I am just acting
as a
third-party information sharer.
The LB is passing webtest requests to both of proxy1 and proxy2.
proxy2 holds
the webtest content and configuration. proxy1 is completely
ignorant of the
webtest content. Approximately half of the webtest requests, the
half that
goes to proxy1, fails to return the webtest content. This can be
seen by
visiting a webtest URL, disabling any caching, and repeatedly
refreshing the
page. It is theoretically possible to get things done like this, but
certainly not easy or fun.
--
Patrick "The N-Man" Barnes
nman64@xxxxxxxxx
http://www.n-man.com/
LinkedIn:
http://www.linkedin.com/in/nman64
Have I been helpful? Rate my assistance!
http://rate.affero.net/nman64/
--