infrastructure April 2019

infrastructure@lists.fedoraproject.org

36 participants
51 discussions

Heads-up: Deleting fas3_server role from ansible
by Clement Verna 23 Apr '19

23 Apr '19

Hi all, I ll be deleting the fas3_server role from our ansible repository since it is currently not used and we are moving away from FAS. See the file diff below. Please let me know, if for any reason we should keep this role. Thanks Clément --- roles/fas3_server/files/accounts.conf | 31 ---- roles/fas3_server/files/copr.repo | 8 - roles/fas3_server/tasks/main.yml | 55 ------ roles/fas3_server/templates/production.ini | 198 --------------------- 4 files changed, 292 deletions(-) delete mode 100644 roles/fas3_server/files/accounts.conf delete mode 100644 roles/fas3_server/files/copr.repo delete mode 100644 roles/fas3_server/tasks/main.yml delete mode 100644 roles/fas3_server/templates/production.ini

4 6

Heads-up: Deleting graphite role from ansible
by Clement Verna 23 Apr '19

23 Apr '19

Hi all, I ll be deleting the graphite role from our ansible repository since it is currently not used. See the file diff below. Please let me know, if for any reason we should keep this role. Thanks Clément --- .../fedmsg2statsd/files/cabal-install.repo | 7 - .../fedmsg2statsd/files/fedmsg2statsd.service | 15 -- .../graphite/fedmsg2statsd/handlers/main.yml | 3 - roles/graphite/fedmsg2statsd/tasks/main.yml | 57 ----- roles/graphite/grafana/files/grafana.repo | 9 - roles/graphite/grafana/files/grafana.service | 23 -- roles/graphite/grafana/handlers/main.yml | 3 - roles/graphite/grafana/tasks/main.yml | 54 ----- roles/graphite/grafana/templates/grafana.conf | 28 --- roles/graphite/graphite/tasks/main.yml | 48 ---- .../graphite/templates/graphite-web.conf | 45 ---- .../graphite/templates/local_settings.py | 212 ------------------ roles/graphite/statsd/tasks/main.yml | 14 -- 13 files changed, 518 deletions(-) delete mode 100644 roles/graphite/fedmsg2statsd/files/cabal-install.repo delete mode 100644 roles/graphite/fedmsg2statsd/files/fedmsg2statsd.service delete mode 100644 roles/graphite/fedmsg2statsd/handlers/main.yml delete mode 100644 roles/graphite/fedmsg2statsd/tasks/main.yml delete mode 100644 roles/graphite/grafana/files/grafana.repo delete mode 100644 roles/graphite/grafana/files/grafana.service delete mode 100644 roles/graphite/grafana/handlers/main.yml delete mode 100644 roles/graphite/grafana/tasks/main.yml delete mode 100644 roles/graphite/grafana/templates/grafana.conf delete mode 100644 roles/graphite/graphite/tasks/main.yml delete mode 100644 roles/graphite/graphite/templates/graphite-web.conf delete mode 100644 roles/graphite/graphite/templates/local_settings.py delete mode 100644 roles/graphite/statsd/tasks/main.yml

3 3

FBR: Fix the freezelist script
by Clement Verna 18 Apr '19

18 Apr '19

Hi all, I found out that the freezelist script did not work with ansible 2.7.10. Once the script changed to use the new api, it complained about 2 non valid yaml file (error syntax error: found character '\t' that cannot start any token) in the vars. So I replaced the tabs character by spaces. See the attached patch +1s ?

3 4

Meeting Agenda 2019-04-18
by Stephen John Smoogen 17 Apr '19

17 Apr '19

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2019-04-18 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby ) Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2019-04-18) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info Final Freeze Started on 2019-04-16 #info Please do not make changes to unfrozen machines without 2 +1 from sysadmin-main = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info https://fedoraproject.org/wiki/Infrastructure/Oncall #info nirik is on call from 2019-04-11 -> 2019-04-18 #info ????? is on call from 2019-04-18 -> 2019-04-25 #info ????? is on call from 2019-04-25 -> 2019-05-02 #info Summary of last week: (from nirik ) #topic Monitoring discussion #info https://nagios.fedoraproject.org/nagios #info Go over existing out items and fix #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket https://pagure.io/fedora-infrastructure/issue/7704 Go thru each ticket one by one #topic Priorities for next week? #info please put tickets or projects needing to be focused on here ===== Put all topics for discussion under here ===== = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor -- Stephen J Smoogen.

1 0

FBR: Switch docs.fp.o over to openshift-built
by Patrick Uiterwijk 17 Apr '19

17 Apr '19

Hi, Can I get +1s for the patch underneath? This will switch from /srv/web/docs (synced from externally built docs sources) to /srv/docs (mount point for doc build outputs built in openshift). This is tested in staging, and the contents in the new location have been confirmed. Regards, Patrick diff --git a/roles/rsyncd/files/rsyncd.conf.sundries b/roles/rsyncd/files/rsyncd.conf.sundries index f6fe92e4f..8cf5cd222 100644 --- a/roles/rsyncd/files/rsyncd.conf.sundries +++ b/roles/rsyncd/files/rsyncd.conf.sundries @@ -24,7 +24,7 @@ hosts allow = 10.5.126.0/255.255.255.0 192.168.0.0/255.255.0.0 10.5.128.0/255.25 [docs] comment = Docs Site -path = /srv/web/docs +path = /srv/docs uid = root gid = root read only = yes

4 3

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

17 Apr '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-04-18 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

Add knowledge of branch freezes to the Release model
by Sebastian Wojciechowski 16 Apr '19

16 Apr '19

Dear all, I would like to start discussion about "How to express information about release freeze to Bodhi". This question is relelated to Bodhi issue https://github.com/fedora-infra/bodhi/issues/1563 The initial plan was to just add some argument to cli "bodhi releases create/edit", something like: >> bodhi releases edit --name F29 --frozen true) but I would like to consider other options, if any, before I start working on solution. Sebastian Wojciechowski

3 2

[PATCH] copr: ensure the newest python-srpm-macros is on builders
by Pavel Raiskup 16 Apr '19

16 Apr '19

Resolves: rhbz#1700028 --- roles/copr/backend/files/provision/provision_builder_tasks.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/copr/backend/files/provision/provision_builder_tasks.yml b/roles/copr/backend/files/provision/provision_builder_tasks.yml index c04a2b349..9d2d6d983 100644 --- a/roles/copr/backend/files/provision/provision_builder_tasks.yml +++ b/roles/copr/backend/files/provision/provision_builder_tasks.yml @@ -37,7 +37,6 @@ - scl-utils-build - ethtool - expect - - python-srpm-macros - name: enable copr and copr-dev repos in staging command: dnf copr -y enable {{ item }} @@ -64,6 +63,7 @@ - rpkg - nosync - distribution-gpg-keys + - python-srpm-macros - name: put updated mock configs into /etc/mock copy: src=files/mock/ dest=/etc/mock -- 2.20.1

1 0

[PATCH] copr: shut down broken ssh connection to builder after 3x60s
by Pavel Raiskup 16 Apr '19

16 Apr '19

--- roles/copr/backend/files/ssh_config | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/copr/backend/files/ssh_config b/roles/copr/backend/files/ssh_config index 302851e10..cd19dd196 100644 --- a/roles/copr/backend/files/ssh_config +++ b/roles/copr/backend/files/ssh_config @@ -2,3 +2,4 @@ Host * IdentityFile ~/.ssh/id_rsa StrictHostKeyChecking no UserKnownHostsFile /dev/null + ServerAliveInterval 60 -- 2.20.1

1 0

pagure -> bugzilla sync script 'tiger team'
by Kevin Fenzi 16 Apr '19

16 Apr '19

Greetings, In triaging ticket last week, we noticed there are several related to the pagure to bugzilla sync script. This script runs once a day (at 18utc) and syncs the point of contact/watchers/committers/etc to bugzilla components. Here's a meta ticket for issues: https://pagure.io/fedora-infrastructure/issue/7690 That lists the other 4 tickets outstanding on it. The script is in our ansible repo: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/distgi… In addition to the 4 tickets theree's a number of other issues with the script: * It fires of a query for every single package/container/module against fedora-scm-requests to see if there's an override for it. We should bundle this information up somehow, or move the overrides to a better place or do something to end those 25,000 queries. * Some folks wanted to add the 'packager' group to their package, with the idea being that they wanted anyone in packager group to be able to push changes. This "works", but the script then tries to mail devel(a)lists.fedoraproject.org as the 'address' for 'packager'. It would be nice to filter this out on a configurable set of groups. * We have a small number of things we don't manage in the script: the distribution component, the various spins components, basically anything thats not a package/module/container/rpm. It would be nice to manage those from the script too so we had a nice place to create/remove them. Anyhow, given all these issues, I thought it would be interesting to try and get a small team together sometime next week and attack re-doing this script. I'd be happpy to help from the sysadmin side of things, but I would love to get a few python savvy folks involved. Any takers? Of course anyone is welcome to look at the script and provide patches/ideas. Please add them to the above 'meta' ticket. :) Thanks! kevin

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure April 2019