On Tue, Oct 08, 2019 at 08:38:18AM -0700, Kevin Fenzi wrote: > On Tue, Oct 08, 2019 at 08:42:13AM +0200, Adrian Reber wrote: > > After the Fedora 31 freeze I would like to introduce this new mirrorlist > > server implementation on the proxies. I already verified that I can run > > this mirrorlist container rootless. This new container can be a drop-in > > replacement for the current container and no infrastructure around it > > needs to be changed. > > > > The main changes to get it into production is to change mirrorlist1.service > > and mirrorlist2.service to include a line "User=mirrormanager" and > > replace the current container name with new container. > > Awesome. > > How about we get this deployed in stg soonish so we can test it out > more. Thanks to smooge's help we were able to switch staging to the new mirrorlist. All changes in ansible are staging only. So you should get almost the same result (modulo randomness) from: https://mirrors.fedoraproject.org/mirrorlist?repo=epel-7&arch=x86_64 https://mirrors.stg.fedoraproject.org/mirrorlist?repo=epel-7&arch=x86_64 My plan was to wait until after the freeze to switch prod to the new setup, but there was also the proposal to switch one production proxy server to the new setup earlier to see if it also works under real load. To test the new setup on one production proxy sounds like a good idea to me, especially if we can try it before the actual Fedora 31 release. If it does not work, we can easily revert to the old setup. If it works, however, I am not sure yet what this would mean. Running only one proxy with the new code and everything else with the current code does not seem like a good idea. So if the test on one production proxy is successful it would mean to switch everything to the new setup during the freeze?? Maybe also not the best idea. I like the idea of trying it in prod, but I am unsure what to do with result of that try. Any further comments about trying this during the freeze? Adrian
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
