Adrian Reber wrote:
On Mon, Nov 03, 2008 at 09:06:20AM +0100, Oliver Falk wrote:
>>> - 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.
> Why not having a second mirrormanager running on another machine and
> have in DNS 2 A records?
I just tested it and it works. I had two entries in DNS; one pointing to
a not existing host and another to an existing. Depending on the answer
from the DNS yum first connects to the existing host and everything just
works. If it connects to the non existing host it times out and then
goes to the existing host. I am surprised that it works.
Great. Trying is better than guessing, right? :-)
If we do that, some users might get a short timeout using yum, but
it
seems like it should work.
That's fine.
The important thing is then to keep the data the same on both hosts,
which should be possible if the cronjobs updating the mirrorlist are
updated at roughly the same time.
Or the main server just triggers the job on the other server... A simple
xinetd-based service would do I think...
So if everybody is okay with it I would then say let's run the
second
mirrorlist instance at Oliver's server...
That's fine for me, just let me know what you need.
-of