infrastructure March 2019

infrastructure@lists.fedoraproject.org

40 participants
97 discussions

"FBR: To update python3-productmd on compose-x86-01.phx2.fp.o"
by Mohan Boddu 20 Mar '19

20 Mar '19

The recent RC compose failed due to: ValueError: Image: Field 'type' has invalid value: vmdk Support for vmdk was added in python3-productmd-1.21-1.fc29 version. Once updated, this issue should be fixed. Thanks.

3 4

FBR: Add nfs-server/remove ipv6-test
by Stephen John Smoogen 20 Mar '19

20 Mar '19

This will bring 45drives box ready for testing and will remove ipv6-test from ansible. I will need to run the noc.yml after this to remove ipv6-test from nagios. -- Stephen J Smoogen.

3 2

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 20 Mar '19

20 Mar '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-03-21 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Fedora 30 Beta Release Readiness meeting
by Ben Cotton 20 Mar '19

20 Mar '19

Dear all, Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30 Beta Release Readiness meeting. This meeting will be held on Thursday, 2018-03-21 at 19:00 UTC. We will meet to make sure we are coordinated and ready for the Beta release of Fedora 30. Please note that this meeting will be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may receive this message several times in order to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information, see https://fedoraproject.org/wiki/Release_Readiness_Meetings. View the meeting on Fedocal: https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/21/#m9492 -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

1 1

Request for comments: mediawiki-FedoraBadges direct db query
by Rick Elrod 20 Mar '19

20 Mar '19

Hi all, Tahrir is slow, and the endpoint that mediawiki-FedoraBadges uses to get its badge count and badge assertion data from takes about 35 seconds per request. As a result, if a user enables both badge count and badge images on a user page, the two requests combined take well over a minute. This results in mediawiki often bombing the request and rendering an ugly error in place of badges. We get tickets/support requests on this occasionally as well: - https://pagure.io/fedora-infrastructure/issue/7650 Some quick testing shows that the queries I care about for the mediawiki-FedoraBadges plugin take about 70ms to run (in prod). Incurring a 35 second penalty for that seems *crazy* to me. As an alternative, I'd like to propose making a tahrir-readonly user, and modifying the mediawiki-FedoraBadges plugin to query the badges database directly. I played around and got it working in staging, the process was something like: - Create tahrir-readonly postgres user - Grant it readonly perms on the tahrir tables, and connect and usage perms. - Modify the mw plugin - Install php-pgsql on wiki01.stg so it can actually connect After that it seems to work fine. I triggered a cache purge of all wiki pages on stg as well (but on prod, I'd probably just let the cache naturally expire). Pages with badges load almost instantly now (granted the stg data is way less than prod, but still). I'm looking for comments because I don't know if there's anything security-wise I'm overlooking in doing this. At a quick glance, it seems fine -- the new pg user is readonly and very few people have access to LocalSettings.php where the connect info would be stored. But I might well be missing something and want to be safe. Thoughts? Rick

4 5

FBR: Greenwave increase gunicorn worker timeout
by Clement Verna 20 Mar '19

20 Mar '19

Hi all, So after setting higher timeout to the openshift route, it seems that now we are hitting gunicorn worker default timeout (30s). The following patch increase this value. diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml b/roles/openshift-apps/greenwave/templates/buildconfig.yml index 7bb5420ba..e293809b8 100644 --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml @@ -30,6 +30,7 @@ spec: # Become non-root again USER 1001 + ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8 --timeout 330 --graceful-timeout 300 --bind 0.0.0.0:8080 --access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app strategy: type: Docker dockerStrategy: -- 2.20.1 +1s ? Thanks

4 4

[FBR ] releng-compose: Just have compose-x86-01 get the default group values for mem and cpus
by kevin＠scrye.com 19 Mar '19

19 Mar '19

From: Kevin Fenzi <kevin(a)scrye.com> In recent months/years, pungi has started to use more and more memory when gathering package sets. So, give it enough memory to avoid the OOM killer killing composes. Signed-off-by: Kevin Fenzi <kevin(a)scrye.com> --- inventory/host_vars/compose-x86-01.phx2.fedoraproject.org | 2 -- 1 file changed, 2 deletions(-) diff --git a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org index 3fa776c..181e3ee 100644 --- a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org +++ b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org @@ -12,8 +12,6 @@ ks_repo: http://10.5.126.23/pub/fedora/linux/releases/28/Server/x86_64/os/ virt_install_command: "{{ virt_install_command_two_nic }}" lvm_size: 30000 -mem_size: 16384 -num_cpus: 8 volgroup: /dev/vg_guests eth0_ip: 10.5.125.41 -- 1.8.3.1

3 2

FBR: Increase the openshift route timeout for greenwave
by Clement Verna 19 Mar '19

19 Mar '19

Hi all, After doing some investigation on bodhi requests to greenwave I found that the requests are hitting a default 30 seconds timeout from the openshift route (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). I would like to increase this timeout to 330 seconds, greenwave will timeout after 300 seconds. For this the following command needs to be run : oc project greenwave oc annotate route greenwave-web --overwrite haproxy.router.openshift.io/timeout=330s oc annotate route web-pretty --overwrite haproxy.router.openshift.io/timeout=330s I ll be looking at how we can add this into ansible. +1s ?

4 6

FBR: make iot.fp.o live
by Rick Elrod 19 Mar '19

19 Mar '19

This has been in stg for a while, and I have been asked to make it live. This FBR is for permission to commit this and run the proxy playbook on all proxies. Rick commit fe044fc717517d01211e1995ff9778b7b7906fe4 Author: Rick Elrod <relrod(a)redhat.com> Date: Tue Mar 19 16:59:54 2019 +0000 [fedora-web/iot] make it live Signed-off-by: Rick Elrod <relrod(a)redhat.com> diff --git a/playbooks/include/proxies-fedora-web.yml b/playbooks/include/proxies-fedora-web.yml index 526ba27..7532950 100644 --- a/playbooks/include/proxies-fedora-web.yml +++ b/playbooks/include/proxies-fedora-web.yml @@ -42,7 +42,6 @@ website: arm.fedoraproject.org - role: fedora-web/iot website: iot.fedoraproject.org - when: env == "staging" - role: fedora-web/registry website: registry.fedoraproject.org - role: fedora-web/ostree diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml index df22e22..352fdde 100644 --- a/playbooks/include/proxies-websites.yml +++ b/playbooks/include/proxies-websites.yml @@ -226,7 +226,6 @@ - iot.stg.fedoraproject.org sslonly: true cert_name: "{{wildcard_cert_name}}" - when: env == "staging" - role: httpd/website site_name: budget.fedoraproject.org diff --git a/roles/fedora-web/build/files/syncStatic.sh b/roles/fedora-web/build/files/syncStatic.sh index 8c5d622..7a541a9 100644 --- a/roles/fedora-web/build/files/syncStatic.sh +++ b/roles/fedora-web/build/files/syncStatic.sh @@ -71,3 +71,4 @@ build fedoracommunity.org build fudcon.fedoraproject.org build start.fedoraproject.org build fedoraproject.org +build iot.fedoraproject.org

3 2

work_mem check for nagios client
by Michal Novotny 19 Mar '19

19 Mar '19

Hello, I've noticed there is no work_mem check https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/nagios… that would test that working memory is inside allowed limits. I've recently made the work_mem check but specific just to COPR: https://clime.cz/0001-copr-fe-working-memory-monitoring.patch. It raises a warning when working memory usage is higher than 80% and criticial if it is higher than 90%. Would it be worth to place this check alongside others in https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/nagios… so that it can be used for any host? Thank you clime

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2019