
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) <https://docs.google.com/a/redhat.com/document/d/1NErdN07kSLZQ_ystxsp9-6Fwq_6zhZMF8VxKO3w2oys/edit?usp=sharing> . 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? Thanks, Nadav.

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) <https://docs.google.com/a/redhat.com/document/d/1NErdN07kSLZQ_ystxsp9-6Fwq_6zhZMF8VxKO3w2oys/edit?usp=sharing> .
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/Bouncer
Thanks, 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

On Tue, Oct 06, 2015 at 05:41:48PM +0200, Sandro Bonazzola wrote:
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) <https://docs.google.com/a/redhat.com/document/d/1NErdN07kSLZQ_ystxsp9-6Fwq_6zhZMF8VxKO3w2oys/edit?usp=sharing> .
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.
Failing in the middle could be solved by moving to a 2-step rsync: first all but a file with a timestamp and the last one only the timestamp, but I agree that partial monitoring is better than no monitoring.
You can add bouncer to your list: https://wiki.mozilla.org/Bouncer

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 6 Oct 2015 5:41 pm, "Sandro Bonazzola" <sbonazzo@redhat.com> wrote:
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) <https://docs.google.com/a/redhat.com/document/d/1NErdN07kSLZQ_ystxsp9-6Fwq_6zhZMF8VxKO3w2oys/edit?usp=sharing> .
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/Bouncer
Thanks, 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

--zCKi3GIZzVBPywwA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 10/06, Anton Marchukov wrote:
As I understand it monitors it by creating files at the mirrored directory and checking if it propogates to the mirrors. =20 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 6 Oct 2015 5:41 pm, "Sandro Bonazzola" <sbonazzo@redhat.com> wrote: =20
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(us=
ed by
Fedora). I've put what I gathered so far here(google docs) <https://docs.google.com/a/redhat.com/document/d/1NErdN07kSLZQ_ystxsp9= -6Fwq_6zhZMF8VxKO3w2oys/edit?usp=3Dsharing> .
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 =
As far as I understood the mirmon is exactly that, there's a cron that crea= tes the files, and a perl script that checks the mirrors and generates the stat= us page 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, n= ot maintained, debian infra specific - assuming I found the correct repos= itory)
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/Bouncer
Thanks, Nadav.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboratio= n. See how it works at redhat.com
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --zCKi3GIZzVBPywwA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWE/OnAAoJEEBxx+HSYmnDpaoH/RcKsBwfvpl+sQ9ksGM7tASk 2CIbU0aSD/b/1hzVkj+/1KSqc2k9wq4RMAEx9dJ/b77Z0ocTtaOQnnzFHYxaLsgB N1YN1NCagUUOUNRX4NX/6JRhznImqBPVTVOEuYWU3yFXXUMa8lNfvtKzgjydaGFZ Oc2peRqmUH1GzOWURyFHbiWy7bhjW4DcCsV4Hzt586S6BhHwmVTbLLwh2+p7NAaf MWDQwPlQ70NvV78DpCQUqvGPZlZiznJki0sV442ryJ4HdMTzbB+yFvq1AMUFxf7d hJRH95Qfor4e/uxK92SfGrcSn4kg85jougPahgySffm7zEa/O9mauriCWG36bes= =4uVf -----END PGP SIGNATURE----- --zCKi3GIZzVBPywwA--

We cannot be the first project that wanted to both monitor the mirros and create a mirror list file, I will find it very surprising indeed if CentOS did not have a full solution for that. Fedora's sulution looks more comprehensive though, I wouldn't be surprised if it has as subsystem for managing the joining of new mirrors. I think that it would be a better solution long term. (And don't be afraid of the DB) On 6 October 2015 at 18:54, Anton Marchukov <amarchuk@redhat.com> wrote:
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 6 Oct 2015 5:41 pm, "Sandro Bonazzola" <sbonazzo@redhat.com> wrote:
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/Bouncer
Thanks, 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
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Barak Korren bkorren@redhat.com RHEV-CI Team
participants (6)
-
Anton Marchukov
-
Barak Korren
-
David Caro
-
Ewoud Kohl van Wijngaarden
-
Nadav Goldin
-
Sandro Bonazzola