Re: [Tails-dev] Some research about mirror infrastructure

Hi,

sajolida@??? wrote (30 Jun 2014 15:52:11 GMT) :
> I'm wondering if this added complexity is really worth it for a first
> fix. Could we work on this core HTTP redirection mechanism first (to
> solve the pool size problem) -- with maybe lizard running a duplicate of
> this script -- and work on a more distributed super-mirror mechanism (to
> solve a resiliency problem) later on?

Until now, lizard is managed in a way that's suitable for hosting dev
tools. I'm not sure what it would take to adapt it for hosting
resources meant for end-user consumption (it terms of logging policy
availability, and protecting important bits of our infrastructure
against PHP).

If lizard is a fallback only, what server did you have in mind to run
the primary super-mirror? (If that's boum.org, we should ask them if
they're ready to take the load and responsibility. And when boum.org
is down, there's no way to reconfigure DNS to have the fallback server
take over, so probably we would need to have it in the
round-robin permanently.)

> That would put more work on our side to setup lizard as a fallback, but
> that would save us, for the time being, the work of coordinating,
> verifying, and maintaining this set of outsources super-mirrors.

Indeed.

If the current situation is problematic enough (which is unclear to
me, actually), then why not spend time on a "temporary" hack. Else,
I say we can instead put time into designing a proper
long-term solution.

Cheers,
--
intrigeri