As I understand it monitors it by creating files at the mirrored directory and checking if it propogates to the mirrors.
Good way to check but since we wanted to split r/o and r/w parts in the future I wonder if it would be possible to separate the writing part from the rest of UI so they can be on different VMs?
On Tue, Oct 6, 2015 at 5:18 PM, Nadav Goldin <ngoldin@redhat.com> wrote:Hi,
I've been reviewing 3 solutions suggested for monitoring oVirt's mirror sites: mirmon(used by CentOS), Debian Mirror Checker, MirrorManager(used by Fedora). I've put what I gathered so far here(google docs).
imo, there are 2 main problems:
1. monitoring that the mirrors are up and synced( logs and http access)
2. updating the mirrorlist(../yum-repo/mirrorlist) file automatically when a mirror site is not synced after X amount of time.
so far installing only mirmon, it seems like the simpler tool that can address problem 1 easily, in order to handle problem 2 another script that filters the log file needs to be written.MirrorManager needs further inspection(has many other features which I am not sure if we need?)
and Debian Mirror Checker, i think, is not worth it(incomplete docs, not maintained, debian infra specific - assuming I found the correct repository)what do you think?I'd like to have mirmon running as a first step. it won't help if rsync fails in the middle but at least it will give us an hint of the health of the mirrors.You can add bouncer to your list: https://wiki.mozilla.org/BouncerThanks,Nadav.
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra