On Wed, 13 Jul 2016 17:04:41 -0500 Dennis Gilmore <dennis@xxxxxxxx> wrote: > There will need to somewhat of an investment in resources to make it > work right. but I think it is important that we do to be able to do > full end to end testing of unreleased content inthe exact same way as > users will do so. I've been pondering and I wonder if instead of another full mirrormanager we just create a small app or even just a apache config that: * If it gets a request for a rawhide / branched metalink, it just serves up one from the current compose area ( /mnt/koji/composes/whatever ). It would only need 1 mirror in the list (kojipkgs) pointing to the right path. It could create the checksums on the fly even. * If it gets request for anything else it just passes it on to the real mirrors.fedoraproject.org Then we set this up in dns to give the small app/apache as mirrors.fedoraproject.org in qa. Other machines there shouldn't be bothered because we pass on non rawhide/branched requests. Would that work? kevin
Attachment:
pgpYBhqYkOJhu.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
