Next steps to get RPM Fusion running (V2)

[Hans de Goede]

Adrian Reber wrote:
> On Mon, Nov 03, 2008 at 09:14:19AM +0100, Thorsten Leemhuis wrote:
>>>> - the current release files and the mirrormanager use different names 
>>>>  for the repo files; Example:
>>>> release.rpm right now has:
>>>>     [...]?repo=rpmfusion-free-debug-f$releasever[...]
>>>> mirror manager expects:
>>>>     [...]?repo=free-debug-fedora$releasever[...]
>>>> We need to change one of the two (or both).
>>> Mirrormanager uses:
>>> https://hosted.fedoraproject.org/mirrormanager/browser/server/mirrormanager/repomap.py
>>> It can be changed, but I would prefer if I do not have to change it ;-)
>> Okay, then I'd say changing the release packages is the easier way for  
>> everyone.
> 
> thx
> 
>>>> - back a few weeks ago you iirc said that we need to be able to 
>>>> adjust  DNS quickly in case the machine goes down; that's not solved 
>>>> yet
>>> No, it is not. We need a another machine running the mirrorlist which
>>> would then get the necessary data from the main mirrormanager instance.
>>> And in a case of a failure we need someone who can changes the DNS entry
>>> very fast.
>> Do we want to ignore this for now and nevertheless switch to use  
>> mirrormanager? (If we ignore this now I fear that this will never get  
>> fixed...)
> 
> I would say: let's set up a backup mirrorlist server and hope that in an
> emergency we will manage to switch the DNS fast enough.
> 
> All I need is an account on the "backup mirrorlist server" and someone
> who can do some changes to the webserver configuration to get it
> running.
> 

Couldn't we list multiple IP addresses under mirrors.rpmfusion.org? Or isn't 
yum smart enough to try the second address if the first one fails ?

Regards,

Hans