Love the idea. Please describe how to hook up applications to receive such notifications. I'd love to have MirrorManager's update-master-directory-list cronjob listen for such instead. -- Matt Domsch Technology Strategist Dell | Office of the CTO ________________________________________ From: infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx [infrastructure-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Kamil Paral [kparal@xxxxxxxxxx] Sent: Monday, September 10, 2012 7:56 AM To: infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Subject: announcing repository updates over Fedora Message Bus I wonder, is it possible for Fedora Infrastructure team to implement announcements of new repository pushes over Fedora Message Bus[1]? By new repository pushes I mean updates to 'fedora', 'updates' and 'updates-testing' repositories for all Fedora releases as well as updates to 'branched' and 'rawhide' trees. The benefits of this solution: 1. Mirrors that download from dl.fp.o could start syncing very soon after an update is pushed (after a random timeout to decrease the load). 2. Those mirrors wouldn't have to periodically query the server for updates. 3. The duration when those mirrors are outdated would be shorter. I can just guess about other people, but in our office I believe the message bus would help a lot. Currently we query the master server every 4 hours for updates. That presents a lot of bandwidth/IO load on both sides. Using the message bug there would be no useless queries. Also it would help us stay up-to-date more often that we currently are (if 'branched' is updated an hour after our last query, there are 3 hours wasted until we run rsync again). This solution could be extended in the future to all Fedora public mirrors, so that they could announce using our message bus when they have finished syncing and users that sync from that particular mirror would know when to start downloading from it. (E.g. if I use mirrors1.kernel.org to sync my private mirror, I would wait for their announcement on our message bus). What do you think? [1] join #fedora-fedmsg and stay there for a while, if you don't know what message bus is _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
