infrastructure November 2016

infrastructure@lists.fedoraproject.org

58 participants
65 discussions

Meeting Agenda Item: Introduction Subham
by Subham Sharma 09 Nov '16

09 Nov '16

IRC Handle: s27 Programming languages familiar with : Python, Java Hi, I am a newbie to programming and to open source and would love to work on "real world" issues and help out as much as I can. I am open to learning new things but would love to start out working in python. Looking forward to an awesome time working with you guys. Regards, Subham

2 1

Getting started docs
by Kevin Fenzi 09 Nov '16

09 Nov '16

Greetings. I've looked over and done some editing on our getting started docs and related wiki pages. Please take a look and see if everything looks more clear and/or you have any suggestions or cleanups: https://fedoraproject.org/w/index.php?title=Infrastructure&diff=prev&oldid=… https://fedoraproject.org/w/index.php?title=Infrastructure/Officers&diff=pr… https://fedoraproject.org/w/index.php?title=Infrastructure/GettingStarted&d… https://fedoraproject.org/w/index.php?title=Infrastructure/Architecture&dif… https://fedoraproject.org/w/index.php?title=Infrastructure_Apprentice&diff=… https://fedoraproject.org/w/index.php?title=Donations&diff=prev&oldid=478911 We have a ton of old pages to archive out, but the ones above I think are the main ones newcomers might hit. Feedback welcome. kevin

2 1

Plan for tomorrow's Fedora Infrastructure meeting - 2016-11-10
by Kevin Fenzi 09 Nov '16

09 Nov '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-11-03 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 -- = Introduction = This shared document is for the next fedora infrastructure meeting. 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 (2016-11-10) #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 25 Final FREEZE now in effect - everyone #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 or 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 on-boarding new folks improvements - kevin / stickster #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. = 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 info 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: = Meeting end stuff = #topic Open Floor #endmeeting

1 0

Triage of fedmsg issues
by Aurelien Bompard 09 Nov '16

09 Nov '16

Hey folks, I'd like to do some triage of the fedmsg issues currently open on Github, then discuss with you what we should prioritize and decide on a roadmap. Triage, first. I haven't had a chance to get to know fedmsg inimately enough so I hope you'll correct me. Here is the list of open issues in reverse chronological order, and the label that I plan to assign to them. Some may be obsolete, I'd love to have your opinion on those. https://github.com/fedora-infra/fedmsg/issues/373 Extract underylying technology stack into a clearly Fedora independent library? -> enhancement, docs https://github.com/fedora-infra/fedmsg/issues/372 fedmsg-logger --json-input can't handle multiline json -> bug, easyfix https://github.com/fedora-infra/fedmsg/issues/371 fedmsg-hub pulls a huge amount of backlog from datagrepper when simply restarted -> enhancement, performance https://github.com/fedora-infra/fedmsg/issues/370 irc bot no messages -> docs https://github.com/fedora-infra/fedmsg/issues/365 Add file-based locking to CRL modification -> bug https://github.com/fedora-infra/fedmsg/issues/339 OS name, release and architecture to meta? -> enhancement, easyfix https://github.com/fedora-infra/fedmsg/issues/320 BadObject when deleting a branch from git repository -> obsolete? https://github.com/fedora-infra/fedmsg/issues/312 encoding discrepancies between php and python -> bug https://github.com/fedora-infra/fedmsg/issues/304 python sample does not work like suggested in docs -> docs https://github.com/fedora-infra/fedmsg/issues/302 fedmsg-relay --daemon ENVAL and flooding logs -> bug https://github.com/fedora-infra/fedmsg/issues/260 seperate colors for the secondary arch builds on irc? -> enhancement https://github.com/fedora-infra/fedmsg/issues/172 Add fedmsg hooks for transifex platform -> enhancement, blocked https://github.com/fedora-infra/fedmsg/issues/159 Add fedmsg-meta-debian to the topics docs -> docs https://github.com/fedora-infra/fedmsg/issues/156 Should BaseProcessor default to None for string-returning methods? -> enhancement, breaks-compat https://github.com/fedora-infra/fedmsg/issues/148 Implement callback to check the state of the socket in fedmsg.tail_messages -> enhancement https://github.com/fedora-infra/fedmsg/issues/137 Askbot messages should distinguish between answer and comment -> enhancement https://github.com/fedora-infra/fedmsg/issues/119 static analysis consumer -> enhancement https://github.com/fedora-infra/fedmsg/issues/114 Add a g+ bot -> enhancement https://github.com/fedora-infra/fedmsg/issues/91 Rename fedmsg to python-fedmsg in rpm-land. -> obsolete? (fedmsg only contains doc and depends on python-* packages) https://github.com/fedora-infra/fedmsg/issues/47 fedmsg.text internationalization -> enhancement I'll go ahead and apply those labels (except the "obsolete" ones) but I'd love to have your thoughts on them and on the general process. Thanks! Aurélien

4 6

Freeze Break: Add F24-Taskotron to the PXE menu on noc01
by Tim Flink 08 Nov '16

08 Nov '16

We're starting to rebuild our dev instance (not under freeze) but I need to install F24 on one of the machines via PXE boot. The patch I would be applying and pushing out to noc01 is attached to this email. +1s? Thanks, Tim

3 3

COPR auto-rebuilds on pagure commits
by Michal Novotny 08 Nov '16

08 Nov '16

Hey, I'd like to announce that we now support package auto-rebuilding on a new commit(s) into a Pagure repository. Apart from having your package repo hosted in Pagure, you just need to enable firing of fedmsg notifications for new commits by clicking a single checkbox in 'Hooks' section...well, then you also need to save this setting and have auto-rebuilding enabled for the copr package but that really is it, I promise :). clime

2 2

Freeze break: [PATCH] increase the badges backlog warning to 7000 to avoid constant alerts
by Kevin Fenzi 07 Nov '16

07 Nov '16

Greetings. This has been alerting a fair bit: Nov 02 08:15:25 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5274 (noc01) Nov 02 08:24:46 <zodbot> ACKNOWLEDGEMENT - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5274 (noc01) http://kevin.id.fedoraproject.org/ Nov 02 18:15:16 <zodbot> RECOVERY - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is OK: OK: fedmsg consumer FedoraBadgesConsumer backlog value is 4440 (noc01) Nov 02 21:17:19 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5715 (noc01) Nov 02 21:27:20 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5440 (noc01) Nov 02 22:07:19 <zodbot> RECOVERY - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is OK: OK: fedmsg consumer FedoraBadgesConsumer backlog value is 4207 (noc01) Nov 03 05:59:23 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5250 (noc01) Nov 03 06:03:17 <zodbot> ACKNOWLEDGEMENT - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5250 (noc01) http://puiterwijk.id.fedoraproject.org/ Nov 03 07:49:19 <zodbot> RECOVERY - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is OK: OK: fedmsg consumer FedoraBadgesConsumer backlog value is 4964 (noc01) Nov 03 08:22:11 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5185 (noc01) Nov 03 11:53:24 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5621 (noc01) Nov 03 12:03:21 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5578 (noc01) Nov 03 13:17:07 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 6395 (noc01) Nov 03 13:17:07 <zodbot> ACKNOWLEDGEMENT - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 6395 (noc01) http://kevin.id.fedoraproject.org/ Nov 03 22:43:19 <zodbot> RECOVERY - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is OK: OK: fedmsg consumer FedoraBadgesConsumer backlog value is 4574 (noc01) Nov 05 22:45:19 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5206 (noc01) Nov 05 22:55:21 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5834 (noc01) Nov 05 23:15:22 <zodbot> RECOVERY - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is OK: OK: fedmsg consumer FedoraBadgesConsumer backlog value is 0 (noc01) Nov 07 15:07:22 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5178 (noc01) Nov 07 15:27:19 <zodbot> PROBLEM - badges-backend01.phx2.fedoraproject.org/Check fedmsg-hub consumers backlog is WARNING: WARNING: fedmsg consumer FedoraBadgesConsumer backlog value is 5392 (noc01) +1s? I would apply the below and run a master -t nagios_client to make sure all clients are updated. From a2c969c4ed4d3f80f9307859807040222b3a4b25 Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Mon, 7 Nov 2016 22:33:02 +0000 Subject: [PATCH] increase the badges backlog warning to 7000 to avoid constant alerts --- roles/nagios/client/templates/check_fedmsg_consumers.cfg.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/nagios/client/templates/check_fedmsg_consumers.cfg.j2 b/roles/nagios/client/templates/check_fedmsg_consumers.cfg.j2 index 2805772..0b4b973 100644 --- a/roles/nagios/client/templates/check_fedmsg_consumers.cfg.j2 +++ b/roles/nagios/client/templates/check_fedmsg_consumers.cfg.j2 @@ -47,7 +47,7 @@ command[check_fedmsg_cbacklog_app]={{libdir}}/nagios/plugins/check_fedmsg_consum command[check_fedmsg_cbacklog_value]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-irc IRCBotConsumer 10 50 command[check_fedmsg_cbacklog_pkgs]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub GenACLsConsumer 10 50 command[check_fedmsg_cbacklog_summershum]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub SummerShumConsumer 100 500 -command[check_fedmsg_cbacklog_badges_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub FedoraBadgesConsumer 5000 10000 +command[check_fedmsg_cbacklog_badges_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub FedoraBadgesConsumer 7000 10000 command[check_fedmsg_cbacklog_notifs_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub FMNConsumer 15000 20000 command[check_fedmsg_cbacklog_bugzilla2fedmsg]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py moksha-hub BugzillaConsumer 10 100 command[check_fedmsg_cbacklog_fedimg_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py fedmsg-hub FedimgConsumer 2000 5000 -- 1.8.3.1

3 2

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by Randy Barlow 07 Nov '16

07 Nov '16

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2016-11-08 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/4671/

1 0

Reboot Bugspad
by Mayank Jha 07 Nov '16

07 Nov '16

Hello folks. I am writing after a long time indeed, more than 2 years or so. The last time I contributed was around the same time. Thanks for letting me still be a part of the Fedora Universe. So, I had been trying to restart on completing what I had started, but things were keeping me from doing it. I am wanting to continue on where I had left <https://github.com/mjnovice/bugspad>. However now when I look back at the project I have some questions which I am searching answers for. 1. Why was the choice of golang in conjunction with redis ? 2. Are we wanting to solve the entire issue tracking problem from scratch, or just replicating all the features which bugzilla already has ? 3. Does this project still hold value ? Will this improve our entire issue tracking eco-system ? 4. The last time I spoke with Kushal, he was suggesting to go with python as it will attract more contributors, but then aren't we undermining the benefits we get from golang ? I would want to do some benchmarking of sorts of whatever language we choose, or library we use before jumping into developing with it. And I would want to attract contributors by making the application awesome, rather than choosing a language/library which is more popular amongst the folks. @Kevin, @Kushal, @Pierre and @all. Wanting your thoughts on this. -- Mayank Jha http://mjnovice.wordpress.com/

2 1

November status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 07 Nov '16

07 Nov '16

You are getting this email because you are in the 'fi-apprentice' group in the fedora account system (or are reading this on the infrastructure list). Feel free to reply just directly to me, or cc the infrastructure list for everyone to see and comment on. https://fedoraproject.org/wiki/Infrastructure_Apprentice At the first of every month(or so), I am going to be sending out an email like this one. I would like feedback on how things are going for you. I'd like to ask for everyone to send me a quick reply with the following data or anything related you can think of that might help us make the apprentice program more useful. 0. Whats your fedora account system login? 1. Have you logged in and used your fi-apprentice membership to look at our machines/setup in the last month? Do you plan to? 2. Has it helped you decide any area you wish to focus on or contribute to more? 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix 4. Do you still wish to be a member of the group? If not (for whatever reason) could you provide any hints to help others down the road? 5. Is there any help or communication or ideas you have that would help you do any of the above? 6. What do you find to be the hardest part of getting involved? Finding things to work on? Getting attention from others to help you? Finding tickets in your interest area? 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? 8. Have you logged into our Gobby instance and read/seen/added to our meeting agenda? https://fedoraproject.org/wiki/Gobby 9. Whats your favorite fall beverage? Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Any folks I do not hear from in the next week will be removed from the group. (Note that it's easy to be readded when you have time or whatever and it's nothing at all personal, we just want to keep the group up to date with active folks). Thanks, and looking forward to your feedback! kevin

22 23

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2016