Hi,
Florian Effenberger wrote:
Thanks for this numbers - and just to be precise and understand the
restrictions correctly: the limit is not set by our infrastructure,
but has been agreed with the mirror admins? Means - if we would like
to use more space at the mirrors we would need to ask the mirror
admins (if they gree or not, is out of our control, I'd guess).
the limit is determined by our infrastructure as well as our mirror admins.
In the infrastructure, we need a machine capable of hosting all the
files.
This holds true for snapshots, RCs, finals. l10ntest builds are provided
on a different machine and distributed via a different channels. On one
hand this helps to scale but for those who manage the builds it is
already complicated enough as we heard.
If its volume is limited to 150 GB, no more than 150 GB can be
distributed to the mirrors. However, disk space is cheap nowadays, so
that's not a real issue if we invest some money out of the budget.
If it were that easy mirrors wouldn't complain.
But you are right a limit of 150GB has to be raised to fulfill our
requirements.
The other problem is the space on the mirrors itself. Not many mirrors
can offer so much space for a single project. Even if one or two mirrors
could, that wouldn't be enough for our downloads. We need at least a
dozen mirrors or so capable of hosting 150, 200, 250 ... GB - and that's
the real problem.
I think we will have to take the numbers we have from Marcus and Joost,
be a bit creative with the combination of the installationsets for each
purpose / status and use the help of qatrack to manage the move from
untested to inQA (and even for inQA to approved).
The only chance I see is to ask the extended mirrors (who already agreed
in providing more mirror space than "normal" mirrors). But I doubt we
get lots of them offering us 150+ GB...
We heard some realistic requirements. Maybe we are not too far away from
the fulfillment.
Greetings
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
