Re: [FBR 0/1] Enable new mirrorlist server on proxy14

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



proxy14 is now running the new rust based mirrorlist server using
rootless containers (running as the mirrormanager user).

So far both containers are happily answering requests and it seems to
work.

Manual testing showed correct results and now we are waiting if anyone
complains about it.

Problems could be wrong results, so people could report being redirected
to the wrong mirrors. Another problem could be related to missing
replies or timeouts, so maybe something like no replies at all. Maybe
during restarts/reloads of the used data.

So far we have not heard any bug reports. Let's hope it keeps on
working.

Memory consumption seems to be less (around 500MB less) and hardly any
CPU required. So far this seems to be an improvement.

The plan is now to keep it running like this until the freeze is over
and see how it handles the actual release traffic. Then decide if we
switch everything to the new code-base.

		Adrian

On Wed, Oct 16, 2019 at 10:50:08AM +0200, Adrian Reber wrote:
> This is a freeze break request to enable the new mirrorlist server on
> proxy14 as discussed on the mailing list.
> 
> I hope my conditionals are correct for the Ansible and Jinja2 files.
> 
> If this freeze break request gets accepted someone needs to run the
> playbook against proxy14.
> 
> Before running the playbook, proxy14 should be removed from DNS to make
> sure, that the old mirrorlist containers are correctly stopped and
> deleted and that the new mirrorlist containers are correctly running.
> 
> 
> Adrian Reber (1):
>   Enable new mirrorlist server on proxy14
> 
>  roles/mirrormanager/backend/files/backend.cron            | 8 +++++---
>  .../backend/templates/sync_pkl_to_mirrorlists.sh          | 2 +-
>  roles/mirrormanager/mirrorlist_proxy/tasks/main.yml       | 2 +-
>  .../mirrorlist_proxy/templates/mirrorlist.service.j2      | 4 ++--
>  4 files changed, 9 insertions(+), 7 deletions(-)
> 
> -- 
> 2.23.0
_______________________________________________
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




[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux