[Catalog-sig] PyPI down again...

Tarek Ziadé ziade.tarek at gmail.com
Sun Jun 13 17:26:47 CEST 2010

On Sun, Jun 13, 2010 at 3:11 PM, M.-A. Lemburg <mal at egenix.com> wrote:
> We've had some private discussions about this, so I'm just
> going to summarize...
> The idea here is not to override the mirror PEP ideas,
> but to use the existing PyPI installation and put the
> content needed for the most widely distributed package tool
> (currently setuptools and zc.buildout) on a content
> delivery network (CDN) in order to have it highly available
> on a managed edge network.

I think it overlaps a bit the PEP goal, which is to set up a network of mirrors,
and have them listed in the PyPI DNS so clients can switch from one mirror
to another.(and even do geoloc!)

Right now we already have "unofficial mirrors" and the idea of the PEP
would be to list them officially at PyPI and to have them collect the
stats so we cant count download hits.

> Amazon Cloudfront is such a CDN and has Python interfaces,
> hence the idea to use Cloudfront.
> I asked for volunteers, because I didn't know enough about
> Amazon Cloudfront to write up a proposal and don't have
> the cycles available to implement such a setup myself.
> In the meantime, I've done some research and now know
> enough to write a proposal for the PSF board to consider.
> If the board thinks it's a good idea, we'll need to
> pursue finding volunteers to implement it.

Well maybe this is the best path to follow right now, as it will be done faster,
without having to interact with much people to set it up, so it's a quick win.

But it will probably kill the mirroring protocol idea from the PEP in
the process,
which I think is superior in the long term since it provides a
standardized ground
for the community to set up mirrors independently from pypi.python.org.

Tarek Ziadé | http://ziade.org

More information about the Catalog-SIG mailing list