infrastructure March 2017

infrastructure@lists.fedoraproject.org

48 participants
84 discussions

Fedmsg notifications not work with this options
by Cătălin George Feștilă 16 Mar '17

16 Mar '17

Hi, The Fedmsg not work so I think that will need to be fix. 1. The settings come with options to set Fedora Elections but link is down https://apps.fedoraproject.org/voting/ 2. The http://fedoraplanet.org/ not work with Blog Posts This are just few I don't tested everything . What do you think ?

3 5

Freeze Break Request: increase threads on resultsdb wsgi daemon
by Tim Flink 16 Mar '17

16 Mar '17

Production resultsdb has started having issues in the last 12 hours or so that appear to be associated with increased load (https://phab.qa.fedoraproject.org/T929). As a quick patch to keep things running while we investigate more, I changed the resultsdb config on the machine and want to make the corresponding change in git. +1s? Tim From 7f3ba1b5294fd91ba60e8d4173f0c20af1e34bf2 Mon Sep 17 00:00:00 2001 From: Tim Flink <tflink(a)fedoraproject.org> Date: Wed, 15 Mar 2017 12:44:14 +0000 Subject: [PATCH] bumping wsgi daemon threads to 20 for resultsdb prod --- roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 b/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 index b8d6f3e..99175f7 100644 --- a/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 +++ b/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 @@ -1,4 +1,8 @@ +{% if deployment_type in ['prod'] %} +WSGIDaemonProcess resultsdb user=apache group=apache threads=20 +{% else %} WSGIDaemonProcess resultsdb user=apache group=apache threads=5 +{% endif %} WSGIScriptAlias /{{ resultsdb_endpoint }} /usr/share/resultsdb/resultsdb.wsgi WSGISocketPrefix run/wsgi -- 1.8.3.1

4 6

FBR: PDC update
by Ralph Bean 16 Mar '17

16 Mar '17

Hi all, I'd like to update: - PDC to python-pdc-1.2.0-8.git.30.gacf661f (f25-infra) on pdc-web0* - pdc-updater to pdc-updater-0.5.4-1 (epel7-infra) on pdc-backend0* There are two changes that come with this: - First, there is a new field in the productmd information produced by pungi which PDC doesn't know about. This is causing the import of some composes to break regularly: https://github.com/fedora-infra/pdc-updater/pull/49/files - Second, there is a bugfix to avoid a race condition in the MBS that relies on a new field added in PDC. The original issue is filed here: https://pagure.io/fm-orchestrator/issue/407 It produced this patch to the MBS: https://pagure.io/fm-orchestrator/pull-request/431 Which in turn depends on two patches to PDC and pdc-updater, which are the subject of this FBR: - https://github.com/fedora-modularity/product-definition-center/pull/11 - https://github.com/fedora-infra/pdc-updater/pull/52 Deploying this involves adding a field to the PDC schema with an automated database migration. If I can get two +1s from sysadmin-main, I'll run it in staging first and if anything goes haywire, I'll put the brakes on it until after the freeze is up. -Ralph

3 2

Plan for tomorrow's Fedora Infrastructure meeting - 2017-03-16
by Kevin Fenzi 16 Mar '17

16 Mar '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-03-16 at 18:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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. kevin -- This shared document is for the next fedora infrastructure meeting. = 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 (2017-03-16) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson #topic New folks introductions = 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 Fedora 26 Alpha freeze is on now! - everyone #info Various hosted projects redirects and data so they could migrate - kevin #info A few new jenkins projects - kevin #info Some new tickets marked easyfix for apprentices to look into - kevin #info = 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 = Apprentice office hours = #topic Apprentice Open office hours 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. x3mboy wants to join as apprentice = Learn about some application or gsetup 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.) #topic Learn about: updates syncing scripts - kevin = Meeting end stuff = #topic Open Floor #endmeeting

1 0

Meeting Agenda Item: Introduction Ben Hart
by InvalidPath 15 Mar '17

15 Mar '17

*First off apologies for not following proper protocol* Name is Ben Hart, Montana US. FAS username is: skeer IRC handle is: ForrestalGrim I'm a sysadmin for a company who provides web hosting and services to the state gov. Along with one other admin we support roughly 40 Linux servers that are mostly CentOS, but a couple old Suse boxes mixed in for flavor. I've played with Linux on and off since 2003 but only got real serious in the past two years. I'm a definite Fedora/Red Hat fanboy and am keenly interested in learning and gaining more experience administrating linux servers as well as BASH and Python. I am not certain of where to start but I'd assume if-apprentice but I'll gladly take suggestions from those who know more. Thanks! B Hart

2 3

Freeze Break Request: add sysadmin-releng to rbac-playbook for loopabull
by Kevin Fenzi 14 Mar '17

14 Mar '17

Greetings. Per https://pagure.io/fedora-infrastructure/issue/5893 I'd like to add sysadmin-releng ability to run the loopabull playbook via rbac playbook. Since we are just rolling that service out, loopabull itself should not be frozen, just batcave where the rbac-playbook perms are. Since this is a change in private I'll not include it here, but it's a pretty simple add and I cant think of anything release related that could be broken by it. +1s? kevin

4 3

Freeze Break Request: fix nagios status.dat path
by Kevin Fenzi 14 Mar '17

14 Mar '17

Greetings. I noticed that our weekly script to send a note about which service/hosts were disabled has been failing. It has the wrong path to the status.dat file. Also, noc02 seems to have the wrong path in it's nagios.cfg file. This patch fixes both of those issues. Along with applying this, I would want to run the ansible playbook over noc01/02. +1s? kevin -- From 37de3e82650cbf3e9b651b3ebcf85d12e4a1bca7 Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Mon, 13 Mar 2017 17:16:42 +0000 Subject: [PATCH] fix path to nagios status.dat file for cron script and also on noc02 Signed-off-by: Kevin Fenzi <kevin(a)scrye.com> --- roles/nagios/server/files/check_nagios_notifications.py | 2 +- roles/nagios/server/files/nagios-external/nagios.cfg | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/nagios/server/files/check_nagios_notifications.py b/roles/nagios/server/files/check_nagios_notifications.py index 7e66202..574df43 100755 --- a/roles/nagios/server/files/check_nagios_notifications.py +++ b/roles/nagios/server/files/check_nagios_notifications.py @@ -17,7 +17,7 @@ debug = 0 EMAIL_FROM="nagios(a)fedoraproject.org" EMAIL_TO="sysadmin-noc-members(a)fedoraproject.org" #EMAIL_TO="athmane(a)fedoraproject.org" -nagios_status_file = '/var/log/nagios/status.dat' +nagios_status_file = '/var/spool/nagios/status.dat' class NagiosStatus: def __init__(self, filename): diff --git a/roles/nagios/server/files/nagios-external/nagios.cfg b/roles/nagios/server/files/nagios-external/nagios.cfg index f75acc8..df31a8c 100644 --- a/roles/nagios/server/files/nagios-external/nagios.cfg +++ b/roles/nagios/server/files/nagios-external/nagios.cfg @@ -107,7 +107,7 @@ resource_file=/etc/nagios/private/resource.cfg # The contents of the status file are deleted every time Nagios # restarts. -status_file=/var/log/nagios/status.dat +status_file=/var/spool/nagios/status.dat -- 1.8.3.1

3 2

Interest in joining the group
by InvalidPath 14 Mar '17

14 Mar '17

Afternoon everyone! So since I like to ramble, I'll try to be brief. I love Linux, and Fedora is my distro of choice. I am also a SysAdmin, admittedly 2 decades worth of Windows and only 3 of CentOS/Ubuntu/Fedora. I'm currently employed as a Linux sys admin however I want to learn more and I want to get give to the community and since I can't give funds I want to give my time and possibly experience :) More details: 40 year old dad of 4, professional geek currently living in Montana. I work for Montana Interactive, a sub-company if you will of NIC, Inc. I support over 40 Linux servers in all the environments (prod, test and dev), we host and manage over 300 web services for the state of Montana government. In any case my goal in this email was an introduction of sorts, and to ask the group: Do you guys think I could be of any help? I'm not proficient in developing (although I do want to learn some Python), and I have time but not huge amounts. But I am passionate about FOSS and Fedora and Linux so I want to give what I can. Thanks everyone! Ben

2 2

Meeting Agenda Item: Introduction Fabrizio Pasqualin
by Faber 14 Mar '17

14 Mar '17

Hello everyone! My name is Fabrizio Pasqualin, male, Italian. My FAS username is giardia I'm a GNU/Linux user since 2007. I work as sound engineer, and in my spare time i'm studying for the Linux Professional Institute Certifications. I'd like to join the fi-apprentice group, because it's a good opportunity for me to learn and improve my knowledge about SysAdmin tasks. I regulary attend my local LUG meetings, we use to play with our EC2 instance on aws which i have ssh access to, i feel confortable with classic LAMP server admin tasks; now i started to learn Ansible. I'd like to examine logs and have a look at fedora infrastructure setup and see what can i learn from there. When i feel confortable i will start to look at some easy to fix issues as well. Please suggest anything you want me to look at I will attend the weekly meetings regularly on IRC, my nick is *capitanocrunch*

2 1

FBR: Update pagure01 prod with patched libgit2
by Patrick Uiterwijk 13 Mar '17

13 Mar '17

Hi, We have been having some performance problems with Pagure due to the way libgit2 handles packed vs loose objects in repositories. I have a patch for it to make it prefer packed files over the loose files. This should save a ton of I/O for bigger, more packed repositories. This patch has been live in staging for a very long time now, and I'd like +1s to apply it on production. Basically, it comes down to just a yum update. The build: https://koji.fedoraproject.org/koji/taskinfo?taskID=18365493 Regards, Patrick P.S.: In the meantime, I'm working on an improved patch that should make it perform even better, but that one will take a bit more time to implement.

3 3

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2017