In MM1, Max Connections isn't used. I would be surprised if it's used in MM2. I never quite figured out how to use that value in a metalink and have it be meaningful. And yum wasn't doing parallel downloads anyhow, so it didn't ever matter. Maybe DNF will do parallel downloads and it should then matter? I don't know enough about DNF to know. -- Matt Domsch Senior Distinguished Engineer & Executive Director Dell | Software Group, Office of the CTO ________________________________________ From: infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx [infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx] on behalf of Chuck Anderson [cra@xxxxxxx] Sent: Friday, April 24, 2015 6:50 PM To: Fedora Infrastructure Subject: Re: Upcoming Mirrormanager 2 production deployment Should this go to the mirror-list rather than just infrastructure? What units is the "Bandwidth" parameter in? How is "Max connections" used? My mirror isn't crawled because it is a private mirror, but I do run the check-in script after every sync. Is there a way to test checking-in to the staging instance? It says last crawled in 2013, and last checked in 2014-12-05. Thanks. On Fri, Apr 24, 2015 at 11:32:21AM -0600, Kevin Fenzi wrote: > Greetings.· > > As you may know we have been working on a new version of mirrormanager, > and we are finally ready to roll it out in production (barring any· > show stoppers).· > > mirrormanager 2 is re-written in flask and has a number of improvements > over mirrormanager 1.· > > We have a set of staging instances setup:· > > https://admin.stg.fedoraproject.org/mirrormanager2/ > > Which is the new flask frontend. The data for mirror admins should· > be pretty much the same. You should be able to login and check your· > mirrors settings (which have been copied from the production instance).· > (Note that any changes made here will not be reflected in production > data) > > and > > https://mirrors.stg.fedoraproject.org/ > > Which is a mirrorlist server using the data from the staging database. > You should be able to use this in place of 'mirrors.fedoraproject.org' > in· yum config and the like.· > > and > > There is also an internal crawler instance, checking mirrors and· > removing out of date ones or readding up to date ones.· > > Source is of course available at:· > https://github.com/fedora-infra/mirrormanager2 > > and bugs or issues can be reported at:· > https://fedorahosted.org/mirrormanager/ > > Please do let us know if you see any problems or issues.· > We will likely be scheduling a short outage next week to roll the new· > version out to production.· > > Thanks,· > > kevin _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
