pypi-mirror team mailing list archive

[Daniel Kraft <dk-launchpad@xxxxxx>]

Hi,

> Thanks. The current code looks pretty good to me for going into
> production. There is only one minor thing I would like to see on the
> index pages: the number of packages and the version number of pypimirror
> used for generating the index pages.

done in 1.0.7. There's a footer now. The number of packages is the
number of dirs/files in the mirror path. This means, as there is no
cleanup, the number will differ between new mirrors and old mirrors (due
to the to-be-cleanedup packages).
We should make cleanup working again soon. A wiped package or wiped
releases might also be wiped due to legal reasons...
But this is no showstopper.

> I think it is time to bring the project somehow into production. Things
> we should address:
> 
>  - all public mirror should run the same software version and use the
>    same pypimirror.cfg (except for local settings)

Done: http://pypi.d9t.de/
1.0.7

Idea: should we expose the cfg-file either directly or by a special
.html file in the mirror? That would help to ensure that all mirrors are
configured the same way and to debug errors on new mirrors.
We could also reveal only relevant settings.

>  - all public mirrors should update their server several times day
>    (e.g. mine runs every six hours)

Mine too 4 times a day. We should make sure that not everybody is
updating on 0 */4 * * * ! But I think, 4 times a day is really enough.
We should define a recommended setting.

>  - all public mirrors should be documented on the openplans wiki with
>    hostname+ip, maintainer of server (Name + Email)

Good idea. Done for Andreas' and mine. Feel free to add yours.

>  - openplans must be updated in order to reflect the configuration
> settings that are necessary for using the infrastructure with zc.buildout

Done for buildout. But I can't do it for "only" easy_install. I have no
idea how that would work. Section marked as TODO.

>  - DNS setup for "hiding" all mirrors behind a canonical name. I agree
>    with Volker that this is not a perfect solution but we have no other
>    choice right now since a mirror-selection algorithm belong into
>    setuptools or zc.buildout. We will approach this for phase 2
>    of the project.

Even if we don't update setuptools' code: If a node is down, a second
try might succeed. As long as we provide the list of single nodes, there
will always be a workaround.

Besides that: I'd be happy to host and register the domain names for
free if there's no foundation-like thing for python. Even if there is
and the decision takes too long, I'd register it and transfer it
afterwards. I think we should bring this all up fast.

My proposal:
  package-index.org [net and com are also free]


Daniel