November 2016 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

Post Freeze break request: resize pagure01's drive
by Patrick Uiterwijk 15 Dec '16

15 Dec '16

Hi, Since Pagure's virtual drive was almost full, and it already has blocked git pushes more than once, I decided to add 10GB to it so it won't cause any problems for now. Note that there's also no nagios monitoring seemingly for this. That seems important to fix. Can I get post-FBR +1s for: - http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=a6a525a - Following https://infrastructure.fedoraproject.org/infra/docs/guestdisk.rst Thanks, Patrick

4 6

Cert penning, Certs and related
by Kevin Fenzi 14 Dec '16

14 Dec '16

Greetings. We have a request ( https://pagure.io/fedora-infrastructure/issue/5372 ) to setup ssl cert pinning for ostree deliverables. It's also been a long wishlist item to have that for rpm deliverables too. Unfortunately there's a bunch of moving parts here that we need to sort out before we can move this forward. First some background/info: * kojipkgs.fedoraproject.org currently uses a valid digisign cert. It needs this because browsers download from it directly, our builders download from it directly, etc. * pkgs/koji currently use certs signed by the Fedora Koji CA (which expires in 2024). This is currently needed by koji to do builds and the upload cgi for lookaside. * We are hoping to deploy soon a pair of freeipa servers in production that get information from fas and allow us to issue kerberos tickets. koji can already authenticate via this method. * There's an outstanding ticket about having a verified way to get source: https://pagure.io/fedora-infrastructure/issue/2324 Questions we need to figure out: * Are we going to retire/replace the koji CA? My thought was yes, but I think Dennis wasn't on board with this. Can anyone who wants to save it speak up? :) * The upload cgi would need to auth with kerberos and sigul would need to auth with kerberos for this to work. * If we are not completely retiring the koji CA, are we replacing it? * Is ostree going to stay distributed at kojipkgs ? Or is it going to move somewhere else? we should figure out the final place for it before we go setting up cert pinning. * The simple way to do pinning is for the application(s) to include a hard coded list of valid certs. I guess this would require changes in librepo and somewhere in ostree? * The complex way to do pinning would be to setup https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning For this we would need to get backup keys for our cert(s) that are used for this and setup webservers to send the right headers. This would also need (more complex) changes in librepo and/or somewhere in ostree. This would also optionally get us reports of violations. Thoughts? Comments? kevin

6 28

FAS3 meetup recap 2016-Oct-18
by Paul W. Frields 06 Dec '16

06 Dec '16

Attendees: Xavier Lamien, Patrick Uiterwijk, Pierre-Yves Chibon, Paul Frields Agenda: Determine what remains to be done on FAS3 to get a new instance for testing followed by production deployment * * * * Features needing forward-porting: -> Basset -> IPA Sync -> python-fedora * Token support required for Hubs support * How to integrate with Ipsilon? - From FAS3 side, need a way to request token from Ipsilon and get it back into FAS3 * Cross-app authentication -> hubs to FAS, fedocal, pkgdb, bodhi... * Flock dead-line was F25-beta freeze (which we're past) * At Flock, FAS2 issue --> dropped FAS3 data until we can get security audit of FAS3 * Also need update to db-migration script -- new license agreement function * Convert this away from mechanism we used in FAS2 * This gives us a way to know which agreement(s) users agreed to, and/or prompt them accordingly * AGREED: Convert current FPCA agreement into FAS3 * Build clean Ansible playbook for FAS3 with a true role, but perhaps do this as a github.com/fedora-infra/fas3-ansible (or other repo e.g. Pagure) * Is there a method for getting client certificates in FAS3? Yes. Go to settings page for this. The certificate is no longer tied to the whole app, but rather per-group. * So for Koji this would be tied to @packager group. * Further, you can also optionally require SSH key for a group PROPOSED: Merge FAS3.0 to development branch when we switch over, since we still have FAS2 elsewhere supybot-fedora also has a fas3 branch which should be ready Timezone handling... AGREED: keep things postgresql-only, storing TZ for the moment. We will add an issue to backlog to handle this down the road to make FAS3 more db-agnostic ACTIONS: * Security audit (already started, using latest git code) --> ETA unknown, will have it soon * Meet to discuss FAS internals --> ETA: 2016-Oct-20, 0800 UTC (10:00 Paris/Amsterdam) * Update db-migration script for CLA handling --> ETA: 2016-Oct-25 * Integration with Ipsilon --> ETA: 2016-Nov-01 * FAS3 in staging --> ETA: 2016-Nov-01 * Update python-fedora --> ETA: 2016-Nov-08? * and deprecate functions where needed * Port all the apps using it (but that's for later) * Make this a major version update * Target for production: 2016-Dec-01? * If we don't make this, slip to early January LATER (for separate followup, not FAS3 blocking) * Updating all flask based apps * kill off flask-fas-openid? <-- happy Patrick -- will break most of our flask app :( * Patrick: would like to make it just use flask-openid transparently without anyone noticing :-) * ouch, we will need to line up changes here then -> plan for later?1 * agreed, I moved this to its own task since it's not (IIUC) strictly required for FAS3 to be deployed -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

2 1

Torrent trackers intermittent error issue
by Michael Simms 03 Dec '16

03 Dec '16

Hello, I keep getting intermittent torrent tracker errors (Tracker gave an error: "Tracker gave HTTP response code 0 (No Response)") in Transmission for some (not all) Fedora torrents. It is never the same ones if I start a new Transmission session. Typically the PC is powered down over night. The torrents are not stalling out when this error happens, they continue to seed. Eventually Transmission manages to get hold of the peer list and the error message goes. So it seems the torrent tracker host server itself is not responding in a timely manner and causing these errors. Additionally I would like to know if there are any backup trackers I can add to the configuration for the Fedora torrents? Also, since I have active seeding connections I believe it isn't down to a firewall issue or Transmission configuration problem. Any clues though? My TDF LibreOffice torrents do not exhibit the same behaviour.

2 2

[release] anitya-0.10.1
by Jeremy Cline 30 Nov '16

30 Nov '16

Hey everyone, Yesterday I released a new version of Anitya, 0.10.1. Many thanks to those who contributed to this release! Changes ======= 0.10.1 (Nov. 29, 2016) ---------------------- * Fix an issue where the version prefix was not being stripped (Issue #372) * Fix an issue where logs were not viewable to some users (Issue #367) * Update anitya's mail_logging to be compatible with old and new psutil (Issue #368) * Improve Anitya's error reporting via email (Issue #368) * Report the reason fetching a URL failed for the folder backend (Issue #338) * Add a timeout to HTTP requests Anitya makes to ensure it does not wait indefinitely (Issue #377) * Fix an issue where prefixes could be stripped further than intended (Issue #381) * Add page titles to the HTML templates (Issue #371) * Switch from processes to threads in the Anitya cron job to avoid sharing network sockets for HTTP requests across processes (Issue #335) -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

koschei-backend reinstall as Fedora 25
by Mikolaj Izdebski 29 Nov '16

29 Nov '16

Hello, I would like to reinstall koschei-backend as Fedora 25 (currently it's deployed on Fedora 24). This should hopefully fix Nagios warnings about high swap usage. Could someone help me with the following two tasks? 1. Create kickstart kvm-fedora-25-koschei as a copy of kvm-fedora-24, with updated repos and doubled size of swap partition? For security reasons I'm not attaching updated kickstart, but here's a "sed" patch instead: sed -e s/24/25/g -e s/2048/4096/ kvm-fedora-24 >kvm-fedora-25-koschei Alternatively, like Kevin suggested, a generic kvm-fedora-25 could be created with 4 GB of swap. 2. Terminate koschei-backend01.stg VM on virthost11 so that I can recreate it with Ansible? Thanks, -- Mikolaj Izdebski

2 2

Weekly Koji Infra Tag Report
by Nobody 28 Nov '16

28 Nov '16

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra (no matching packages) epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- freeipa-ktutils epel7-infra puiterwijk glusterfs epel7-infra kevin python-robosignatory epel7-infra puiterwijk pdc-updater epel7-infra ralph blockerbugs epel7-infra tflink mirrormanager2 epel7-infra puiterwijk f23-infra (no matching packages) f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin python-twill f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk mediawiki-skin-fedora f24-infra puiterwijk mediawiki-Lockdown f24-infra kevin mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra (no matching packages)

1 0

Weekly Koji Infra Tag Report
by Nobody 28 Nov '16

28 Nov '16

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra (no matching packages) epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- freeipa-ktutils epel7-infra puiterwijk glusterfs epel7-infra kevin python-robosignatory epel7-infra puiterwijk pdc-updater epel7-infra ralph blockerbugs epel7-infra tflink mirrormanager2 epel7-infra puiterwijk f23-infra (no matching packages) f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin python-twill f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk mediawiki-skin-fedora f24-infra puiterwijk mediawiki-Lockdown f24-infra kevin mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra (no matching packages)

1 0

Planned Outage: Cloud Environment - 2016-12-01 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-12-01 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-12-01 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Cloud Environment - *.fedorainfracloud.org Unaffected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5581 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: General Services Environment - 2016-11-30 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-30 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-30 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Unaffected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: 2016-11-29 21:00 UTC Build Environment
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-29 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-29 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ Unaffected Services: BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5579 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: Staging Environment - 2016-11-28 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-28 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-28 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Unaffected Services: BFO - https://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Torrent trackers intermittent error issue
by Michael Simms 28 Nov '16

28 Nov '16

Hello, I keep getting intermittent torrent tracker errors (Tracker gave an error: "Tracker gave HTTP response code 0 (No Response)") in Transmission for some (not all) Fedora torrents. It is never the same ones if I start a new Transmission session. Typically the PC is powered down over night. The torrents are not stalling out when this error happens, they continue to seed. Eventually Transmission manages to get hold of the peer list and the error message goes. So it seems the torrent tracker host server itself is not responding in a timely manner and causing these errors. Additionally I would like to know if there are any backup trackers I can add to the configuration for the Fedora torrents? Also, since I have active seeding connections I believe it isn't down to a firewall issue or Transmission configuration problem. Any clues though? My TDF LibreOffice torrents do not exhibit the same behaviour.

1 0

Meeting Agenda Item: Introduction Davide Olivieri
by daleko＠yahoo.com 28 Nov '16

28 Nov '16

Hello everyone, My name is Davide and I am writing from Poland. I would like to join the Fedora infrastructure team to learn new things and contribute to the distribution. I have some experience in dealing with production servers as I'm currently working as an application support/maintenance engineer for a solution for security financing running on RedHat. In the past I worked in similar roles for enterprise backup/restore and cryptography solutions (Backup Exec and PGP). For about half a year I also worked in a data center mainly dealing with alerts incoming from monitoring tools. I hold a RHCSA certification (license 160-036-125), I am familiar with perl 5 and bash and occasionally package software with RPM for personal use. I would be happy to perform any task but I am really interested in acquiring knowledge on the following stuff: * Fedora services and ecosystem * Ansible * OS deployment* Work with file servers* Advanced configuration of http servers (Apache already gave me some headaches) * Enhance servers security As of now the time I could dedicate to Fedora is about 4/5 hours per week.I have a home server used as KVM hyper-visor that I could use for testing out things. My registered nick on freenode is daleko, I hope to hear from any of you. Thank you! Cheers,Davide

2 1

Nagios and epylog now Kerberos-based
by Patrick Uiterwijk 24 Nov '16

24 Nov '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Just thought I'd also drop this to the infra list, but as of today, Nagios and Epylog are using Kerberos for authentication. This means that as long as you have a ticket for @FEDORAPROJECT.ORG, logging in to Nagios and Epylog should be automatic. For instructions on how to use the Infrastructure Kerberos services, please see [1]. [1]: https://fedoraproject.org/wiki/Infrastructure_kerberos_authentication Regards, Patrick Uiterwijk -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYN2DkAAoJEIZXmA2atR5QmGYP/RR05WdqqJ+jstQ6lucZnMxb omylfx/0aQ/FHo5vC56eLy4tJhz26asscs6mn5AiTsURaxoxwZoXiWIyH3MVhKzv fs+xOrIS1FgUfXCu/D2CKg8VTDu/80p7sLMw20l4rdW/Uopnur+AlUarssN7xu3/ vcqniv6anoxbt/wkyEEsMbPtTzfpCZcuJc4zyG065ROB/6XRb0fRlIJvAQTOwdfn 4V6BGsSQchQ76SLQtox+B335YpASYcQtkJIPzZNmacDJ/6hDucY5IaiYSWNIlLQM g61CAa6J3K4yJp92T0G8N7bGTys9q2cbvd+iVljSOrXuswds8uWm/Lh61DSCvZkT tNvnJ48iALvWKbBxs7+B0ZqO1pGGTiVCZ9du+VVMubRP2t0Y/rCbOSHTn4vsP456 bIK5K5UCLdW1pVaNnFl03gDIlCW/cB4KKOU5RLEi+P8+q3FipXkjtzVrw/fTE5hA m9A4ZFJoQas5Jchi3YGzyuW7Rm0/RT/34LqCTw2H3WtMzoAnxUGSQyuhC6p38HED thM36dL66H/XVg6yLB930eGvmzAgnDJ3bvJ19y/zXmUWVY2M47kI9IuWqtNMKbTt pfngCmu1M/UwGXyVjQzfaeB5V3QVhw3Cyvub2NcAoWdO1LiAy0D1XvqWK5gbM9mr aNVGmYtM4t/JoZm7FbAf =whW7 -----END PGP SIGNATURE-----

1 0

Fedora 25 Final freeze now in effect
by Kevin Fenzi 23 Nov '16

23 Nov '16

Greetings. we are now in the infrastructure freeze leading up to the Fedora 25 Final release. This is a final freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 25 when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2016-11-15. (or later if Beta slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

Freeze break request: refine the filterlist stuff (make it an imagelist using productmd)
by Adam Williamson 22 Nov '16

22 Nov '16

The main problem here is the 'archive' filterlist is still pretty big, over 20MiB. I don't want to push the fedfind changes out to the public until it's smaller. With this change the imagelist files are all tiny, under 250KiB. pr #26 is an alternative to this which just extends the exclusion list of the previous approach, but nirik says he prefers this approach. From 5b7169688a1732f49ff0bb6320fa34e641b363de Mon Sep 17 00:00:00 2001 From: Adam Williamson <awilliam(a)redhat.com> Date: Mon, 21 Nov 2016 19:36:49 -0800 Subject: [PATCH] turn 'filterlist' into 'imagelist', using productmd This adopts https://pagure.io/quick-fedora-mirror/pull-request/27 and adapts to it, so we get `imagelist` files rather than `filterlist` files (see recent commits for this). The rationale is more fully explained in that PR (and in PR #26 also) - on further inspection it turns out that we have to filter out an awful lot of extensions to create small filterlists for all three modules, and I'm worried that other file extensions may appear in the future and cause the filterlists to suddenly get bigger again. Instead, we have create-filelist use the productmd constant that defines valid image formats, and only include files that match those formats in the list. The downside of this approach is we have to ensure productmd on all the systems that run `create-filelist` is kept up to date if the list of valid image formats changes. --- files/scripts/create-filelist | 15 ++++++++------- files/scripts/update-fullfiletimelist | 26 +++++++++++++------------- playbooks/groups/secondary.yml | 1 + roles/bodhi2/backend/tasks/main.yml | 1 + roles/releng/tasks/main.yml | 1 + 5 files changed, 24 insertions(+), 20 deletions(-) diff --git a/files/scripts/create-filelist b/files/scripts/create-filelist index e485efb..0beaced 100755 --- a/files/scripts/create-filelist +++ b/files/scripts/create-filelist @@ -12,6 +12,7 @@ import argparse import hashlib import os import sys +from productmd.images import SUPPORTED_IMAGE_FORMATS from scandir import scandir @@ -58,8 +59,8 @@ def parseopts(): null = open(os.devnull, 'w') p = argparse.ArgumentParser( description='Generate a list of files and times, suitable for consumption by quick-fedora-mirror, ' - 'and a much smaller list with packages, Device Tree boot files, HTML files, pictures ' - 'and directories filtered out, for consumption by fedfind.') + 'and a much smaller list of only files that match one of the productmd supported ' + 'image types, for use by fedfind.') p.add_argument('-c', '--checksum', action='store_true', help='Include checksums of all repomd.xml files in the file list.') p.add_argument('-C', '--checksum-file', action='append', dest='checksum_files', @@ -75,8 +76,8 @@ def parseopts(): help='Filename of the file list with times (default: stdout).') p.add_argument('-f', '--filelist', type=argparse.FileType('w'), default=null, help='Filename of the file list without times (default: no plain file list is generated).') - p.add_argument('-F', '--filterlist', type=argparse.FileType('w'), default=null, - help='Filename of the filtered file list for fedfind (default: not generated).') + p.add_argument('-i', '--imagelist', type=argparse.FileType('w'), default=null, + help='Filename of the image file list for fedfind (default: not generated).') opts = p.parse_args() @@ -112,9 +113,9 @@ def main(): # opts.filelist.write(entry.path + '\n') print(entry.path, file=opts.filelist) # write to filtered list if appropriate - skips = ('.rpm', '.drpm', '.dtb', '.html', '.png', '.jpg') - if not any(entry.path.endswith(skip) for skip in skips) and not (entry.is_dir()): - print(entry.path, file=opts.filterlist) + imgs = ['.{0}'.format(form) for form in SUPPORTED_IMAGE_FORMATS] + if any(entry.path.endswith(img) for img in imgs): + print(entry.path, file=opts.imagelist) if entry.name in opts.checksum_files: checksums[entry.path[2:]] = True info = entry.stat(follow_symlinks=False) diff --git a/files/scripts/update-fullfiletimelist b/files/scripts/update-fullfiletimelist index f6c225a..c0439da 100755 --- a/files/scripts/update-fullfiletimelist +++ b/files/scripts/update-fullfiletimelist @@ -25,7 +25,7 @@ CREATE=/usr/local/bin/create-filelist # context. FILELIST=fullfilelist TIMELIST='fullfiletimelist-$mod' -FILTERLIST='filterlist-$mod' +IMAGELIST='imagelist-$mod' usage () { echo @@ -108,12 +108,12 @@ cd $tmpd for mod in $MODS; do currentfl=$TOPD/$mod/${FILELIST/'$mod'/$mod} currenttl=$TOPD/$mod/${TIMELIST/'$mod'/$mod} - currentsl=$TOPD/$mod/${FILTERLIST/'$mod'/$mod} + currentil=$TOPD/$mod/${IMAGELIST/'$mod'/$mod} flname=$(basename $currentfl) tlname=$(basename $currenttl) - slname=$(basename $currentsl) + ilname=$(basename $currentil) - $CREATE -c -s -d $TOPD/$mod -f $flname -t $tlname -F $slname + $CREATE -c -s -d $TOPD/$mod -f $flname -t $tlname -i $ilname # If a file list exists and doesn't differ from what we just generated, # delete the latter. @@ -123,8 +123,8 @@ cd $tmpd if [[ -f $currenttl ]] && diff -q $currenttl $tlname > /dev/null; then rm -f $tlname fi - if [[ -f $currentsl ]] && diff -q $currentsl $slname > /dev/null; then - rm -f $slname + if [[ -f $currentil ]] && diff -q $currentil $ilname > /dev/null; then + rm -f $ilname fi done @@ -134,13 +134,13 @@ cd $tmpd for mod in $MODS; do currentfl=$TOPD/$mod/${FILELIST/'$mod'/$mod} currenttl=$TOPD/$mod/${TIMELIST/'$mod'/$mod} - currentsl=$TOPD/$mod/${FILTERLIST/'$mod'/$mod} + currentil=$TOPD/$mod/${IMAGELIST/'$mod'/$mod} flname=$(basename $currentfl) fldir=$(dirname $currentfl) tlname=$(basename $currenttl) tldir=$(dirname $currenttl) - slname=$(basename $currentsl) - sldir=$(dirname $currentsl) + ilname=$(basename $currentil) + ildir=$(dirname $currentil) if [[ -f $flname ]]; then tmpf=$(mktemp -p $fldir $flname.XXXXXXXXXX) @@ -154,11 +154,11 @@ cd $tmpd chmod 644 $tmpf mv $tmpf $currenttl fi - if [[ -f $slname ]]; then - tmpf=$(mktemp -p $sldir $slname.XXXXXXXXXX) - cp -p $slname $tmpf + if [[ -f $ilname ]]; then + tmpf=$(mktemp -p $ildir $ilname.XXXXXXXXXX) + cp -p $ilname $tmpf chmod 644 $tmpf - mv $tmpf $currentsl + mv $tmpf $currentil fi done diff --git a/playbooks/groups/secondary.yml b/playbooks/groups/secondary.yml index e4a49a8..1d6f545 100644 --- a/playbooks/groups/secondary.yml +++ b/playbooks/groups/secondary.yml @@ -58,6 +58,7 @@ - createrepo - koji - python-scandir + - python2-productmd - name: add create-filelist script from quick-fedora-mirror copy: src="{{ files }}/scripts/create-filelist" dest=/usr/local/bin/create-filelist mode=0755 diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml index 08105b5..674b03a 100644 --- a/roles/bodhi2/backend/tasks/main.yml +++ b/roles/bodhi2/backend/tasks/main.yml @@ -24,6 +24,7 @@ - sigul - python-alembic - python-scandir + - python2-productmd tags: - packages - bodhi diff --git a/roles/releng/tasks/main.yml b/roles/releng/tasks/main.yml index d02fbea..f85ebd2 100644 --- a/roles/releng/tasks/main.yml +++ b/roles/releng/tasks/main.yml @@ -117,6 +117,7 @@ - pungi - compose-utils - python-scandir + - python2-productmd when: ansible_distribution_major_version|int > 21 # add sigul to secondary arch compose boxes -- 2.10.2 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

3 3

Freeze break request: fix f24 references in f25-updates-testing atomic updates
by Kevin Fenzi 21 Nov '16

21 Nov '16

From f55c6f20bc5676f62a50535dbe5c1d1eb74aae4b Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Mon, 21 Nov 2016 16:42:19 +0000 Subject: [PATCH] fix fedora-25-updates-testing to have correct f25 references for bodhi atomic updates composing --- roles/bodhi2/backend/templates/atomic-config.py.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/bodhi2/backend/templates/atomic-config.py.j2 b/roles/bodhi2/backend/templates/atomic-config.py.j2 index 7a10d92..99e3977 100644 --- a/roles/bodhi2/backend/templates/atomic-config.py.j2 +++ b/roles/bodhi2/backend/templates/atomic-config.py.j2 @@ -45,7 +45,7 @@ config = dict( 'treefile': { 'include': 'fedora-atomic-docker-host.json', 'ref': 'fedora-atomic/25/x86_64/testing/docker-host', - 'repos': ['fedora-24', 'fedora-24-updates', 'updates-testing'], + 'repos': ['fedora-25', 'fedora-25-updates', 'updates-testing'], 'packages': [], }, -- 1.8.3.1

3 2

FBR: apply patch to bodhi-backend03
by Patrick Uiterwijk 20 Nov '16

20 Nov '16

Hi, Can I get +1s for applying the patch at [1] to bodhi-backend03? This should fix the SSL problem that occurs during mashing. [1]: https://github.com/fedora-infra/bodhi/pull/1122 Regards, Patrick

3 2

freeze break request: filtered file lists
by Adam Williamson 18 Nov '16

18 Nov '16

This commit should give us new 'filterlist' files alongside the 'fullfilelist' and 'fullfiletimelist' files in the /fedora , /archive and /alt folders on the mirrors. The contents of this file are the same as 'fullfilelist', but with all directories, packages (.rpm or .drpm files) and device tree boot files (.dtb files) removed. This gives a massively smaller list which, right now, will be useful for fedfind (it can parse these lists instead of rsync scraping) and may possibly be useful for other things in future, I guess. It would be nice to have this now as this all came out of the work around improving generation of the mediawriter 'available images' JSON file: we want to use fedfind to generate that, but the rsync scraping is pretty heavy for something that'll run quite frequently. This should improve things quite a bit (especially as I've written fedfind to cache the files and only re-download them if the Last-Modified header changes). I have the fedfind changes all written and tested (I tested against the fullfilelist files). From 3f61df2f2879c23a7e44271527facce99bc92286 Mon Sep 17 00:00:00 2001 From: Adam Williamson <awilliam(a)redhat.com> Date: Fri, 18 Nov 2016 16:34:38 -0800 Subject: [PATCH] Generate filtered file lists for fedfind to use This adds `filterlist` files alongside the `fullfilelist` and `fullfiletimelist` files. These are much, much shorter lists which skip the entries for packages, ARM device tree boot files and directories. They are intended for consumption by fedfind, so it can stop using rync scraping to discover the image files it looks for. To enable this, we update to a newer version of `create-filelist` from upstream `quick-fedora-mirror` and make `update-fullfiletimelist` create the filterlist files as well. We also delete a couple of old copies of `create-filelist`; nirik made the two roles that use it share a common copy a few months back, but missed deleting the copy each role had in its `files` directory. --- files/scripts/create-filelist | 10 ++++++++- files/scripts/update-fullfiletimelist | 19 ++++++++++++++-- roles/bodhi2/backend/files/create-filelist | 36 ------------------------------ roles/releng/files/create-filelist | 36 ------------------------------ 4 files changed, 26 insertions(+), 75 deletions(-) delete mode 100644 roles/bodhi2/backend/files/create-filelist delete mode 100644 roles/releng/files/create-filelist diff --git a/files/scripts/create-filelist b/files/scripts/create-filelist index eeba9d0..8fc3367 100755 --- a/files/scripts/create-filelist +++ b/files/scripts/create-filelist @@ -57,7 +57,9 @@ def recursedir(path='.', skip=[], alwaysskip=['.~tmp~']): def parseopts(): null = open(os.devnull, 'w') p = argparse.ArgumentParser( - description='Generate a list of files and times, suitable for consumption by quick-fedora-mirror.') + description='Generate a list of files and times, suitable for consumption by quick-fedora-mirror, ' + 'and a much smaller list with packages, Device Tree boot files, HTML files and ' + 'directories filtered out, for consumption by fedfind.') p.add_argument('-c', '--checksum', action='store_true', help='Include checksums of all repomd.xml files in the file list.') p.add_argument('-C', '--checksum-file', action='append', dest='checksum_files', @@ -73,6 +75,8 @@ def parseopts(): help='Filename of the file list with times (default: stdout).') p.add_argument('-f', '--filelist', type=argparse.FileType('w'), default=null, help='Filename of the file list without times (default: no plain file list is generated).') + p.add_argument('-F', '--filterlist', type=argparse.FileType('w'), default=null, + help='Filename of the filtered file list for fedfind (default: not generated).') opts = p.parse_args() @@ -107,6 +111,10 @@ def main(): for entry in recursedir(skip=opts.skip_files): # opts.filelist.write(entry.path + '\n') print(entry.path, file=opts.filelist) + # write to filtered list if appropriate + skips = ('.rpm', '.drpm', '.dtb', '.html') + if not any(entry.path.endswith(skip) for skip in skips) and not (entry.is_dir()): + print(entry.path, file=opts.filterlist) if entry.name in opts.checksum_files: checksums[entry.path[2:]] = True info = entry.stat(follow_symlinks=False) diff --git a/files/scripts/update-fullfiletimelist b/files/scripts/update-fullfiletimelist index 016ca8e..e70fadc 100755 --- a/files/scripts/update-fullfiletimelist +++ b/files/scripts/update-fullfiletimelist @@ -25,6 +25,7 @@ CREATE=/usr/local/bin/create-filelist # context. FILELIST=fullfilelist TIMELIST='fullfiletimelist-$mod' +FILTERLIST=filterlist usage () { echo @@ -107,12 +108,14 @@ cd $tmpd for mod in $MODS; do currentfl=$TOPD/$mod/${FILELIST/'$mod'/$mod} currenttl=$TOPD/$mod/${TIMELIST/'$mod'/$mod} + currentsl=$TOPD/$mod/${FILTERLIST/'$mod'/$mod} flname=$(basename $currentfl) tlname=$(basename $currenttl) + slname=$(basename $currentsl) - $CREATE -c -s -d $TOPD/$mod -f $flname -t $tlname + $CREATE -c -s -d $TOPD/$mod -f $flname -t $tlname -F $slname - # If a file list exsts and doesn't differ from what we just generated, + # If a file list exists and doesn't differ from what we just generated, # delete the latter. if [[ -f $currentfl ]] && diff -q $currentfl $flname > /dev/null; then rm -f $flname @@ -120,6 +123,9 @@ cd $tmpd if [[ -f $currenttl ]] && diff -q $currenttl $tlname > /dev/null; then rm -f $tlname fi + if [[ -f $currentsl ]] && diff -q $currentsl $slname > /dev/null; then + rm -f $slname + fi done # Now we have the new file lists but in a temporary directory which @@ -128,10 +134,13 @@ cd $tmpd for mod in $MODS; do currentfl=$TOPD/$mod/${FILELIST/'$mod'/$mod} currenttl=$TOPD/$mod/${TIMELIST/'$mod'/$mod} + currentsl=$TOPD/$mod/${FILTERLIST/'$mod'/$mod} flname=$(basename $currentfl) fldir=$(dirname $currentfl) tlname=$(basename $currenttl) tldir=$(dirname $currenttl) + slname=$(basename $currentsl) + sldir=$(dirname $currentsl) if [[ -f $flname ]]; then tmpf=$(mktemp -p $fldir $flname.XXXXXXXXXX) @@ -145,6 +154,12 @@ cd $tmpd chmod 644 $tmpf mv $tmpf $currenttl fi + if [[ -f $slname ]]; then + tmpf=$(mktemp -p $sldir $slname.XXXXXXXXXX) + cp -p $slname $tmpf + chmod 644 $tmpf + mv $tmpf $currentsl + fi done ) 9>$LOCKFILE diff --git a/roles/bodhi2/backend/files/create-filelist b/roles/bodhi2/backend/files/create-filelist deleted file mode 100644 index d95000e..0000000 --- a/roles/bodhi2/backend/files/create-filelist +++ /dev/null @@ -1,36 +0,0 @@ -#!/usr/bin/python - -# A simple script to generate a file list in a format easily consumable by a -# shell script. - -# Originally written by Jason Tibbitts <tibbs(a)math.uh.edu> in 2016. -# Donated to the public domain. If you require a statement of license, please -# consider this work to be licensed as "CC0 Universal", any version you choose. - - -from scandir import scandir - - -def get_ftype(entry): - """Return a simple indicator of the file type.""" - if entry.is_symlink(): - return 'l' - if entry.is_dir(): - return 'd' - return 'f' - - -def recursedir(path): - """Just like scandir, but recursively.""" - for entry in scandir(path): - if entry.is_dir(follow_symlinks=False): - for rentry in recursedir(entry.path): - yield rentry - yield entry - - -for entry in recursedir('.'): - info = entry.stat(follow_symlinks=False) - modtime = max(info.st_mtime, info.st_ctime) - ftype = get_ftype(entry) - print('{} {} {}'.format(modtime, ftype, entry.path[2:])) diff --git a/roles/releng/files/create-filelist b/roles/releng/files/create-filelist deleted file mode 100644 index d95000e..0000000 --- a/roles/releng/files/create-filelist +++ /dev/null @@ -1,36 +0,0 @@ -#!/usr/bin/python - -# A simple script to generate a file list in a format easily consumable by a -# shell script. - -# Originally written by Jason Tibbitts <tibbs(a)math.uh.edu> in 2016. -# Donated to the public domain. If you require a statement of license, please -# consider this work to be licensed as "CC0 Universal", any version you choose. - - -from scandir import scandir - - -def get_ftype(entry): - """Return a simple indicator of the file type.""" - if entry.is_symlink(): - return 'l' - if entry.is_dir(): - return 'd' - return 'f' - - -def recursedir(path): - """Just like scandir, but recursively.""" - for entry in scandir(path): - if entry.is_dir(follow_symlinks=False): - for rentry in recursedir(entry.path): - yield rentry - yield entry - - -for entry in recursedir('.'): - info = entry.stat(follow_symlinks=False) - modtime = max(info.st_mtime, info.st_ctime) - ftype = get_ftype(entry) - print('{} {} {}'.format(modtime, ftype, entry.path[2:])) -- 2.10.2 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 3

[PATCH] update the pre release policy for f26
by Dennis Gilmore 18 Nov '16

18 Nov '16

From: Dennis Gilmore <ausil(a)fedoraproject.org> Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org> --- roles/bodhi2/base/templates/production.ini.j2 | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 index a172e25..7864938 100644 --- a/roles/bodhi2/base/templates/production.ini.j2 +++ b/roles/bodhi2/base/templates/production.ini.j2 @@ -10,16 +10,16 @@ filter-with = proxy-prefix # Release status # pre-beta enforces the 'Pre Beta' policy defined here: # https://fedoraproject.org/wiki/Updates_Policy -f25.status = pre_beta +f26.status = pre_beta -f25.post_beta.mandatory_days_in_testing = 7 -f25.post_beta.critpath.num_admin_approvals = 0 -f25.post_beta.critpath.min_karma = 2 -f25.post_beta.critpath.stable_after_days_without_negative_karma = 14 +f26.post_beta.mandatory_days_in_testing = 7 +f26.post_beta.critpath.num_admin_approvals = 0 +f26.post_beta.critpath.min_karma = 2 +f26.post_beta.critpath.stable_after_days_without_negative_karma = 14 -f25.pre_beta.mandatory_days_in_testing = 3 -f25.pre_beta.critpath.num_admin_approvals = 0 -f25.pre_beta.critpath.min_karma = 1 +f26.pre_beta.mandatory_days_in_testing = 3 +f26.pre_beta.critpath.num_admin_approvals = 0 +f26.pre_beta.critpath.min_karma = 1 ## ## Atomic OSTree support -- 1.8.3.1

3 3

freeze break request: Undo fedfind/releases.json stuff
by Ricky Elrod 18 Nov '16

18 Nov '16

It is a static part of the websites build for now. commit 61902d81d3d2ece72c9fffcef38fb7b28b9b9055 Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Fri Nov 18 18:20:15 2016 +0000 undo these for now Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/fedora-web/build/files/syncStatic.stg.sh b/roles/fedora-web/build/files/syncStatic.stg.sh index 0ad6072..ac9313b 100644 --- a/roles/fedora-web/build/files/syncStatic.stg.sh +++ b/roles/fedora-web/build/files/syncStatic.stg.sh @@ -54,13 +54,6 @@ build arm.fedoraproject.org build getfedora.org build alt.fedoraproject.org -# Temporary: Build releases.json here and copy it over. -# This will eventually move to a daily cron. -cd getfedora.org -make json-releases -rsync -qa --delete-after --delay-updates out/releases.json /srv/web/getfedora.org/ -cd .. - pushd mirrors.fedoraproject.org > /dev/null rsync -qa --delete-after --delay-updates . /srv/web/mirrors.fedoraproject.org/ popd > /dev/null diff --git a/roles/fedora-web/build/tasks/main.yml b/roles/fedora-web/build/tasks/main.yml index 903f341..4fc92e6 100644 --- a/roles/fedora-web/build/tasks/main.yml +++ b/roles/fedora-web/build/tasks/main.yml @@ -2,7 +2,6 @@ yum: pkg={{ item }} state=present with_items: - babel - - fedfind - git - python-feedparser - python-genshi

1 0

[release] pagure: 2.9
by Pierre-Yves Chibon 18 Nov '16

18 Nov '16

Good Morning everyone, I just cut a new release of pagure: 2.9. This is a fairly large release, see the changelog: * Fri Nov 18 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.9-1 - Update to 2.9 - Fix redirecting after updating an issue on a project with namespace (Vivek Anand) - Remove take button from Closed Issues (Rahul Bajaj) - Show the open date/time on issues as we do for PR (Rahul Bajaj) - When rendering markdown file use the same code path as when rendering comments - Add documentation for using Markdown in Pagure (Justing W. Flory) - Fix the behavior of the Cancel button on PR page (Rahul Bajaj) - Be tolerant to markdown processing error - Let the notifications render correctly when added by the SSE server - Fix the URL for pull request on the list of branches of a fork (Rahul Bajaj) - Adjust the markdown processor to have 1 regex for all cross-project links - Remove unsued variables (Farhaan Bukhsh) - Hide the title of private tickets when linking to them in markdown - Show user activity in pagure on the user's page - Add the possibility to subscribe to issues - Do not cache the session in pagure-ci (as we did for pagure-webhook) - Fix rendering raw file when the sha1 provided is one of a blob - Include project's custom fields in the JSON representation of a project - Include the issue's custom fields values in the JSON representation of an issue - Include the list of close_status and the milestones in the JSON of a project - Improve documentation related to unit-tests (Rahul Bajaj) - Use `project.fullname` in X-Pagure-Project header (Adam Williamson) - Figure a way to properly support WTF_CSRF_TIME_LIMIT on older version of flask-wtf - When updating an issue, if the form does not validate, say so to the user - Fix the total number of pages when there are no PR/issues/repo (vibhcool) - Fix forking a repo with a namespace - Include the namespace in the message returned in pagure.lib.new_project - Move the metadata-ery area in PR to under the comments tab (Ryan Lerch) - Update setup instructions in the README.rst (alunux) - Support namespaced projects when reading json data (clime) - When uploading a file in a new issue, propagate the namespace info - Ensure our avatar works with non-ascii email addresses - Downgrade to emoji 1.3.1, we loose some of the newer emojis we get back preview and reasonable size (Clément Verna) - Fix sending notifications email containing non-ascii characters - Fix using the proper URL in email notifications (Adam Williamson) - Move the Clear and Cancel buttons to the right hand side of the comment box - Fix spelling in the PR page (Vibhor Verma) - Support loading custom fields from JSON when loading issues from git (Vivek Anand) - Fix handling namespaced project in the SSE server (Adam Williamson) - Add a pylintrc configuration file to help with code standards (Adam Williamson) - Add go-import meta tag allowing go projects to be hosted on pagure (Patrick Uiterwijk) - Fix index overflow when opening remote pull-request (Mark Reynolds) - Add SSE support for custom fields - Add a git blame view - Allow emptying a file when doing online editing - Only let admins edit the dependency tree of issues - Fix some spelling errors (Adam Williamson) - Add SHA256 signature to webhooks notifications (Patrick Uiterwijk) - Multiple fixes in the API documentation and output To highlight a few: - We now present the user's activity on their page using the now well-know calendar heatmap - X-pagure-project in the email headers now contains the full name of the project (ie fork/username/projectname) instead of just the project name, so beware if you are relying on this field for your email filtering - We should no longer have the issue with disappearing comments \ó/ Thanks to everyone who contributed on this release, there was quite a few people involved :) I will not be online next week, so this release is currently running only in stg and will remain there at least until November 28th (at which point we may very well be ready for a 2.9.1). As usual testers are welcomed. Happy hacking! Pierre

1 0

[freeze break request] add fedfind for websites build, enable json-releases build in stg
by Ricky Elrod 17 Nov '16

17 Nov '16

I'd like to: - Add the fedfind dep for the websites build on sundries - Enable the json-releases build task in syncStatic for stg - Run the sundries playbook Commits for the first two tasks follow: commit d892719a2395cd34d1e3c7e979899461e74e941b Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Thu Nov 10 19:37:58 2016 +0000 add new fedfind dep for websites - needed for release json Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/fedora-web/build/tasks/main.yml b/roles/fedora-web/build/tasks/main.yml index 4fc92e6..903f341 100644 --- a/roles/fedora-web/build/tasks/main.yml +++ b/roles/fedora-web/build/tasks/main.yml @@ -2,6 +2,7 @@ yum: pkg={{ item }} state=present with_items: - babel + - fedfind - git - python-feedparser - python-genshi commit 053c0d75d9a4ca6a01a1ab41185a5fb6fc7e481b Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Thu Nov 10 19:48:52 2016 +0000 build releases.json in stg Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/fedora-web/build/files/syncStatic.stg.sh b/roles/fedora-web/build/files/syncStatic.stg.sh index ef2446d..c62036c 100644 --- a/roles/fedora-web/build/files/syncStatic.stg.sh +++ b/roles/fedora-web/build/files/syncStatic.stg.sh @@ -53,6 +53,13 @@ build labs.fedoraproject.org build arm.fedoraproject.org build getfedora.org +# Temporary: Build releases.json here and copy it over. +# This will eventually move to a daily cron. +cd getfedora.org +make json-releases +rsync -qa --delete-after --delay-updates out/releases.json /srv/web/getfedora.org/ +cd .. + /usr/bin/git clean -q -fdx || exit 1 /usr/bin/git reset -q --hard || exit 1 /usr/bin/git checkout -q alt-rewrite || exit 1

3 2

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

16 Nov '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-11-17 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-17) #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 still in effect - everyone #info more pagure migrations happening - everyone #info Next week is thanksgiving holiday in US. 24th/25th holidays - everyone #info NO meeting next week due to holiday - everyone #info Patrick and Kevin will be out at the PHX2 datacenter 2016-12-05 to 09 - kevin and patrick #info Holidays in december coming up as well. #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 meeetbot status - kevin/abompard #topic plans for december/january - kevin = 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

Memory on koschei-backend01.phx2
by Mikolaj Izdebski 16 Nov '16

16 Nov '16

Michael Simacek pointed out that koschei-backend01.phx2 has 20 GB of physical memory, while Ansible inventory vars specify only 4 GB. Does anyone know where this difference comes from? Did anyone increase VM settings without committing them to Ansible git repo? If so, what was the reason? -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk

3 4

Meeting Agenda Item: Introduction Bradley
by Bradley Sharpe 16 Nov '16

16 Nov '16

IRC: threenodedev Not sure what skills to list here. I’ve been working on computer systems (including Linux) for about 20+ years. I have built physical servers, networks and systems for this time. I have had the pleasure of setting up OpenStack on physical hardware, configuring AWS via Ansible and (unfortunately) doing a lot of Windows system administration. So… I’ve had at least a smattering of the following technologies: Nagios, Ansible, AWS, OpenStack, Linux(various distros), Ruby, Python, Javascript, networking (cisco mostly). What I’d like to learn is to get better at Python and system infrastructure design (and monitoring). Mostly I’m excited to contribute to the Fedora team. Cheers, Bradley

2 1

CSI variarables added to blockerbugs
by Dmitry Saunin 16 Nov '16

16 Nov '16

Hi all! Please take o look on my first patch to group_vars.

2 3

Freeze Break Request: Remove Dell-fx- from various playbook files.
by Stephen John Smoogen 14 Nov '16

14 Nov '16

--- inventory/builders | 24 ++++++++++++------------ inventory/hardware | 8 ++++---- playbooks/groups/virthost.yml | 2 +- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/inventory/builders b/inventory/builders index 3f1a2e2..a4bc857 100644 --- a/inventory/builders +++ b/inventory/builders @@ -115,22 +115,22 @@ buildhw-11.phx2.fedoraproject.org buildhw-12.phx2.fedoraproject.org [dell-fx-build] -dell-fx01-01.phx2.fedoraproject.org -dell-fx01-02.phx2.fedoraproject.org -dell-fx01-03.phx2.fedoraproject.org -dell-fx01-04.phx2.fedoraproject.org +# dell-fx01-01.phx2.fedoraproject.org +# dell-fx01-02.phx2.fedoraproject.org +# dell-fx01-03.phx2.fedoraproject.org +# dell-fx01-04.phx2.fedoraproject.org # dell-fx01-05.phx2.fedoraproject.org # dell-fx01-06.phx2.fedoraproject.org # dell-fx01-07.phx2.fedoraproject.org # dell-fx01-08.phx2.fedoraproject.org -dell-fx02-01.phx2.fedoraproject.org -dell-fx02-02.phx2.fedoraproject.org -dell-fx02-03.phx2.fedoraproject.org -dell-fx02-04.phx2.fedoraproject.org -dell-fx02-05.phx2.fedoraproject.org -dell-fx02-06.phx2.fedoraproject.org -dell-fx02-07.phx2.fedoraproject.org -dell-fx02-08.phx2.fedoraproject.org +# dell-fx02-01.phx2.fedoraproject.org +# dell-fx02-02.phx2.fedoraproject.org +# dell-fx02-03.phx2.fedoraproject.org +# dell-fx02-04.phx2.fedoraproject.org +# dell-fx02-05.phx2.fedoraproject.org +# dell-fx02-06.phx2.fedoraproject.org +# dell-fx02-07.phx2.fedoraproject.org +# dell-fx02-08.phx2.fedoraproject.org [buildppc] buildppc-01.phx2.fedoraproject.org diff --git a/inventory/hardware b/inventory/hardware index 02bcb2d..c0afa9d 100644 --- a/inventory/hardware +++ b/inventory/hardware @@ -39,10 +39,10 @@ dell-fx01-01.phx2.fedoraproject.org dell-fx01-02.phx2.fedoraproject.org dell-fx01-03.phx2.fedoraproject.org dell-fx01-04.phx2.fedoraproject.org -# dell-fx01-05.phx2.fedoraproject.org -# dell-fx01-06.phx2.fedoraproject.org -# dell-fx01-07.phx2.fedoraproject.org -# dell-fx01-08.phx2.fedoraproject.org +dell-fx01-05.phx2.fedoraproject.org +dell-fx01-06.phx2.fedoraproject.org +dell-fx01-07.phx2.fedoraproject.org +dell-fx01-08.phx2.fedoraproject.org dell-fx02-01.phx2.fedoraproject.org dell-fx02-02.phx2.fedoraproject.org dell-fx02-03.phx2.fedoraproject.org diff --git a/playbooks/groups/virthost.yml b/playbooks/groups/virthost.yml index a5e593f..2a1d3fb 100644 --- a/playbooks/groups/virthost.yml +++ b/playbooks/groups/virthost.yml @@ -3,7 +3,7 @@ # NOTE: most of these vars_path come from group_vars/backup_server or from hostvars - name: make virthost server system - hosts: virthost:bvirthost:buildvmhost:dell-fx-build:virthost-comm:colo-virt:!inter… + hosts: virthost:bvirthost:buildvmhost:virthost-comm:colo-virt:!internetx01.fedorap… user: root gather_facts: True -- 1.8.3.1 -- Stephen J Smoogen.

3 3

FBR: enable aarch64 for EPEL-7 in bodhi
by Peter Robinson 14 Nov '16

14 Nov '16

Hi, I'd like to enable aarch64 for EPEL-7, I was going to wait until post F-25 GA but given we've slipped I'd like to get approval for FBR. The change in mash configs for bodhi is as below. Peter diff --git a/roles/bodhi2/backend/files/epel7-testing.mash b/roles/bodhi2/backend/files/epel7-testing.mash index 24d5b48..dd29d3e 100644 --- a/roles/bodhi2/backend/files/epel7-testing.mash +++ b/roles/bodhi2/backend/files/epel7-testing.mash @@ -13,6 +13,6 @@ keys = 352C64E5 use_repoview = False repoviewurl = http://download.fedoraproject.org/pub/epel/testing/7/%(arch)s/ repoviewtitle = "Fedora EPEL Testing 7 - %(arch)s" -arches = x86_64 ppc64 ppc64le +arches = x86_64 ppc64 ppc64le aarch64 hash_packages = True delta = False diff --git a/roles/bodhi2/backend/files/epel7.mash b/roles/bodhi2/backend/files/epel7.mash index 19f53b4..391ae45 100644 --- a/roles/bodhi2/backend/files/epel7.mash +++ b/roles/bodhi2/backend/files/epel7.mash @@ -13,6 +13,6 @@ keys = 352C64E5 use_repoview = False repoviewurl = http://download.fedoraproject.org/pub/epel/7/%(arch)s/ repoviewtitle = "Fedora EPEL 7 - %(arch)s" -arches = x86_64 ppc64 ppc64le +arches = x86_64 ppc64 ppc64le aarch64 hash_packages = True delta = False

5 8

[release] pagure-importer : 1.2.3
by Clement Verna 14 Nov '16

14 Nov '16

Hi all, A new release of pagure-importer is available from COPR (https://copr.fedorainfracloud.org/coprs/cverna/pagure-importer/) And it contains the following PR : 1.2.3 ======= - need to install RPMs as root form copr, so use sudo (Matthew Miller) - separate milestone and tags, better tags pre-processing (Vivek Anand) - custom fields for fedorahosted tickets (Vivek Anand) - Fix #68 'list' object has no attribute 'username' on pgimport github (Michal Novotný) - Get more than one attachment per comment (Clement Verna) - Add Documentation to turn off Fedmsg hook and code refactor (Clement Verna) - Strip trailling / (Patrick Uiterwijk) Cheers, Clement

1 0

[freeze break] Add alt.fedoraproject.org to production's syncTranslation script
by Robert Mayr 14 Nov '16

14 Nov '16

We are going to release a new website, which is running in staging now, but for production I need to add this website to the syncTranslation.py script in order to pull translations also to sundries01. Diff is the following: diff --git a/roles/fedora-web/build/files/syncTranslations.sh b/roles/fedora-web/build/files/syncTranslations.sh index 63976b9..d8467e3 100644 --- a/roles/fedora-web/build/files/syncTranslations.sh +++ b/roles/fedora-web/build/files/syncTranslations.sh @@ -3,7 +3,8 @@ # It pulls every resources. PO_DIR=/var/tmp/po_dir -SITES="boot.fedoraproject.org \ +SITES="alt.fedoraproject.org \ + boot.fedoraproject.org \ fedoracommunity.org \ fedorahosted.org \ fedoraproject.org \ Thank you. -- Robert Mayr (robyduck)

4 3

Freeze Break Request: Fix koji hub for rawhide clients
by Patrick Uiterwijk 12 Nov '16

12 Nov '16

Can I get any +1s? Explanation is in the commit message. commit 934cbf8d70d52a7819ae4af575f04bdf70cdcd0c Author: Patrick Uiterwijk <puiterwijk(a)redhat.com> Date: Fri Nov 11 23:38:41 2016 +0000 Fix koji client cert authentication with OpenSSL 1.1.0 Turns out that renegotiation is broken in OpenSSL 1.1.0, so we allow clients to send their certificates (but not require them) from the very first connection on, so that they don't have to renegotiate. Signed-off-by: Patrick Uiterwijk <puiterwijk(a)redhat.com> diff --git a/roles/koji_hub/templates/kojihub.conf.j2 b/roles/koji_hub/templates/kojihub.conf.j2 index 01e6f1b..f39ee34 100644 --- a/roles/koji_hub/templates/kojihub.conf.j2 +++ b/roles/koji_hub/templates/kojihub.conf.j2 @@ -24,6 +24,7 @@ Alias /kojifiles "/mnt/koji/" </Directory> {% endif %} +SSLVerifyClient optional <Location /kojihub/ssllogin> SSLVerifyClient require SSLVerifyDepth 10

4 3

Freeze break request: add www.getfedora.org to proxies
by Kevin Fenzi 11 Nov '16

11 Nov '16

Greetings. Someone reported in https://pagure.io/fedora-infrastructure/issue/5562 that www.getfedora.org doesn't resolve. I've since added it to DNS, but we need to also tell proxies to treat it as a server alias. Note, we have a redirect so if someone goes to http://www.getfedora.org or http://www.getfedora.com or http://getfedora.com it will redirect them to https://getfedora.org, but that doesn't help if they go to the https versions of those. I don't think there's much we can do there without getting certs for each of these silly combos, which I am against. In any case this fixes the http case and is simple enough: diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml index c567987..7d47039 100644 --- a/playbooks/include/proxies-websites.yml +++ b/playbooks/include/proxies-websites.yml @@ -133,6 +133,7 @@ - www.projectofedora.org - www.getfedora.com - getfedora.com + - www.getfedora.org - fedoraplayground.org - fedoraplayground.com +1s? kevin

3 2

Freeze break request: adjust #fedora-ask fedmsg irc bot messages
by Kevin Fenzi 11 Nov '16

11 Nov '16

From 1aa7b1de0793aa5844c405097ca10474cb93a39a Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Fri, 11 Nov 2016 15:08:11 +0000 Subject: [PATCH] Adjust fedora-ask fedmsg irc bot to only show 2 topics. https://pagure.io/fedora-infrastructure/issue/5538 --- roles/fedmsg/irc/templates/ircbot.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/fedmsg/irc/templates/ircbot.py b/roles/fedmsg/irc/templates/ircbot.py index a5e7ad1..c3097b0 100644 --- a/roles/fedmsg/irc/templates/ircbot.py +++ b/roles/fedmsg/irc/templates/ircbot.py @@ -175,7 +175,7 @@ config = dict( channel='fedora-ask', # Only show AskFedora messages filters=dict( - topic=['^((?!askbot).)*$'], + topic=['^((?!(askbot.post.edit|askbot.flag_offensive.add)).)*$'], ), ), -- 1.8.3.1

3 2

FAS group gitmirroradmin unneeded
by Matt Domsch 10 Nov '16

10 Nov '16

I believe this group is no longer used, and can be deleted. It was to grant access to the git tree for MM1 when hosted in fedorahosted. Thanks, Matt [image: Inline image 1]

2 1

[release] fedmsg: 0.18.0
by Ralph Bean 10 Nov '16

10 Nov '16

Hi all, I've cut a new release of fedmsg upstream and will be packaging it for Fedora and EPEL. There's nothing in this release that needs to be rolled out in the infra environment imminently. This email is just to let you know that the release if available for when we next do mass updates. 0.18.0 ------ Pull Requests - (@ralphbean) #374, Cascade IRC connections. https://github.com/fedora-infra/fedmsg/pull/374 - (@ralphbean) #375, Kill the status page... https://github.com/fedora-infra/fedmsg/pull/375 - (@ncoghlan) #377, Make intro less Fedora specific https://github.com/fedora-infra/fedmsg/pull/377 - (@ralphbean) #380, Get fedmsg-hub working on STOMP. https://github.com/fedora-infra/fedmsg/pull/380 - (@jeremycline) #382, Turn testing Python 2.6 in Travis on https://github.com/fedora-infra/fedmsg/pull/382 - (@jeremycline) #381, Raise the resource limit on open files for fedmsg-hub https://github.com/fedora-infra/fedmsg/pull/381 - (@mprahl) #388, Return earlier when validate_signatures is turned off https://github.com/fedora-infra/fedmsg/pull/388 - (@ralphbean) #387, Document turning off validation for other busses. https://github.com/fedora-infra/fedmsg/pull/387 - (@asdil12) #386, Add SSL support to irc bot https://github.com/fedora-infra/fedmsg/pull/386 - (@tvieira) #385, Updating dependencies on documentation https://github.com/fedora-infra/fedmsg/pull/385 Commits - 55d4ecdd5 Cascade IRC connections. https://github.com/fedora-infra/fedmsg/commit/55d4ecdd5 - ce5a19b25 Add some logging. https://github.com/fedora-infra/fedmsg/commit/ce5a19b25 - 917ad58fc Make sure we don't do this forever... https://github.com/fedora-infra/fedmsg/commit/917ad58fc - b9ab4ffb6 Wait 5 seconds instead of 1. https://github.com/fedora-infra/fedmsg/commit/b9ab4ffb6 - e02633917 Kill the status page... it is old and hard to maintain. https://github.com/fedora-infra/fedmsg/commit/e02633917 - fb5190e24 Make intro less Fedora specific (#1) https://github.com/fedora-infra/fedmsg/commit/fb5190e24 - 10c0398a5 Add missing space https://github.com/fedora-infra/fedmsg/commit/10c0398a5 - d8b41ef35 Local and hosted test unification https://github.com/fedora-infra/fedmsg/commit/d8b41ef35 - 11a812feb Drop the support for Python 2.6 https://github.com/fedora-infra/fedmsg/commit/11a812feb - 37c5d2f8e Add support for Python 3.5 https://github.com/fedora-infra/fedmsg/commit/37c5d2f8e - f9d3bd74c Allow configuration for fedmsg-hub to listen to STOMP or AMQP instead of just zmq. https://github.com/fedora-infra/fedmsg/commit/f9d3bd74c - 8e5e9d1b6 fedmsg.core modifications for STOMP/AMQP hand-off. https://github.com/fedora-infra/fedmsg/commit/8e5e9d1b6 - 3714777cc Some config comments about STOMP usage. https://github.com/fedora-infra/fedmsg/commit/3714777cc - 7888c538e Massage STOMP messages into a more compatible format. https://github.com/fedora-infra/fedmsg/commit/7888c538e - 2f8b4024f Let the ircbot handle weird topics (like from STOMP). https://github.com/fedora-infra/fedmsg/commit/2f8b4024f - fa24f8c77 Add doc on enabling STOMP support. https://github.com/fedora-infra/fedmsg/commit/fa24f8c77 - 3c593e266 Be more precise in this comment. https://github.com/fedora-infra/fedmsg/commit/3c593e266 - 5df1e4831 Copy this docstring to the actual docs. https://github.com/fedora-infra/fedmsg/commit/5df1e4831 - 91594886c Use something more clear than .isalpha. https://github.com/fedora-infra/fedmsg/commit/91594886c - fdee6e458 Turn testing Python 2.6 in Travis on https://github.com/fedora-infra/fedmsg/commit/fdee6e458 - 439383ab7 Revert "Drop the support for Python 2.6" https://github.com/fedora-infra/fedmsg/commit/439383ab7 - bd452112f Update pip before starting the Travis tests https://github.com/fedora-infra/fedmsg/commit/bd452112f - 3651cfcdf Raise the resource limit on open files for fedmsg-hub https://github.com/fedora-infra/fedmsg/commit/3651cfcdf - 004a2fc9c Updating dependencies on documentation https://github.com/fedora-infra/fedmsg/commit/004a2fc9c - 8072a84e4 Fixing typo on library name https://github.com/fedora-infra/fedmsg/commit/8072a84e4 - 7cbc517a9 Add SSL support to ircbot https://github.com/fedora-infra/fedmsg/commit/7cbc517a9 - 69e382716 Document turning off validation for other busses. https://github.com/fedora-infra/fedmsg/commit/69e382716 - 0e1189c6a Return earlier when validate_signatures is turned off https://github.com/fedora-infra/fedmsg/commit/0e1189c6a

1 0

Help requested to join fi-apprentice
by Yisu Peng 10 Nov '16

10 Nov '16

Hi everyone, I'm a newbie to fedora group. My FAS username is "yisupeng". I've been following the 'Getting started' wiki page and look forward to join the infrastructure group. I'm a Master student in Computer Science and I'm experienced in C/C++, bash, python, etc. I'd worked as a system administrator managing a lot of virtual machines that were used as compiling platforms. The systems used were CentOS. We also used the Jenkins as our CI platform. This link contains some other information. https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… Thanks for reading. Yisu Peng

3 3

Meeting Agenda Item: Introduction Oliver
by oliver guss 09 Nov '16

09 Nov '16

IRC Handle (fd92) Programming languages Python, C++ and PHP. Hi, I am new to open source and would be happy to help out in any way i can. I am very eager to learn new things, Python is where I am strongest and where I would like to start out. I would appreciate directions on where to start and I look forward to working with you. Regards, Oliver

2 1

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

November status update for Fedora Infrastructure Apprentices
by Tammy Miller 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? tammyb 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? No. Still having a hard time setting up 2. Has it helped you decide any area you wish to focus on or contribute to more? No 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? No 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? Yes, please. 5. Is there any help or communication or ideas you have that would help you do any of the above? Not at this moment. 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? Finding tickets to work on. 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? Not recently. 8. Have you logged into our Gobby instance and read/seen/added to our meeting agenda? https://fedoraproject.org/wiki/Gobby Not recently, but I have in the past. 9. Whats your favorite Halloween food? https://en.wikipedia.org/wiki/Halloween#Food None Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Nothing yet, sir. 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 _______________________________________________ infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org<mailto:infrastructure@lists.fedoraproject.org> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org<mailto:infrastructure-leave@lists.fedoraproject.org>

2 1

Looking for a mentor
by Subham Sharma 07 Nov '16

07 Nov '16

Hi as I am a newbie into open source and programming in general, would anyone like to be my mentor and help through this process. Someone who is proficient in Python would be highly appreciated. Thank you. BR, Subham On Nov 6, 2016 1:47 PM, "Subham Sharma" <sam271994(a)gmail.com> wrote: 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

5 4

Queries around the Network Architecture that Fedora uses.
by Mayank Jha 06 Nov '16

06 Nov '16

I was going through this, https://fedoraproject.org/wiki/Infrastructure/Architecture. Had some questions around the same. The questions may sound a bit noobish, but anyhow am throwing it up. 1. HAProxy load balances the requests among the various app servers, but the configuration on which HAProxy runs, are those dynamically changing, or they are manually updated through some bash scripts, whenever there is a need to ? 2. Also before making the choices of HAProxy, Apache and Varnish were there any discussions related to why the choice is being made. Are those discussion docs public ? -- Mayank Jha http://mjnovice.wordpress.com/

2 1

[FBR] Bump upload size limitation in pagure
by Pierre-Yves Chibon 04 Nov '16

04 Nov '16

Good Morning Everyone, The design folks have asked if we could bump the maximum size allowed when uploading content to pagure. It is currently of 4MB and they are asking if we could bump it to 50MB. ref: https://pagure.io/fedora-infrastructure/issue/5555 It is a simple configuration change that looks like this: diff --git a/ roles/pagure/frontend/templates/pagure.cfg b/ roles/pagure/frontend/templates/pagure.cfg index 227813d..eb3ed92 100644 --- a/ roles/pagure/frontend/templates/pagure.cfg +++ b/ roles/pagure/frontend/templates/pagure.cfg @@ -143,7 +143,7 @@ ITEM_PER_PAGE = 50 ### Maximum size of the uploaded content # Used to limit the size of file attached to a ticket for example -MAX_CONTENT_LENGTH = 4 * 1024 * 1024 # 4 megabytes +MAX_CONTENT_LENGTH = 50 * 1024 * 1024 # 4 megabytes ### Lenght for short commits ids or file hex SHORT_LENGTH = 7 I would like to ask if I can apply this change, deploy it and restart apache on pagure01. Thoughts? Thanks, Pierre

3 2

Migrating license agreement from FAS2 to FAS3
by Pierre-Yves Chibon 03 Nov '16

03 Nov '16

Good Morning Everyone, This morning I started looking at migration our license agreements from FAS2 to FAS3. We currently have 8 CLAs in FAS2: - cla_dell - cla_done - cla_ibm - cla_fedora - cla_redhat - cla_click - cla_intel - cla_fpca For the moment, in the migration script I created a dummy license agreement: `cla_fpca` and migrated all the people member of the `cla_fpca` group in FAS2 as having signed that new license agreement. The question I have is basically: do we want to migrate all 8 CLAs by creating their respective LAs in FAS3 and migrating their members or are we only interested in the FPCA group these days? Thoughts? Thanks, Pierre

4 4

[PATCH] update owner-sync-pkgdb to support the docker namespace
by Dennis Gilmore 03 Nov '16

03 Nov '16

From: Dennis Gilmore <ausil(a)fedoraproject.org> update the script to sync from pkgdb to koji and enable it via a cronjob Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org> --- roles/bodhi2/backend/tasks/main.yml | 8 ++++++++ roles/bodhi2/backend/templates/owner-sync-pkgdb.j2 | 19 ++++++++++++------- 2 files changed, 20 insertions(+), 7 deletions(-) diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml index 421c16f..4fa662e 100644 --- a/roles/bodhi2/backend/tasks/main.yml +++ b/roles/bodhi2/backend/tasks/main.yml @@ -188,6 +188,14 @@ cron_file=update-koji-owner-fedora when: inventory_hostname.startswith('bodhi-backend03') and env == "production" tags: + + - name: sync packages from pkgdb2 to koji fedor (docker) + cron: name="owner-sync-fedora" minute="7,17,27,37,47,57" user="root" + job="/usr/local/bin/owner-sync-pkgdb f24-docker;/usr/local/bin/owner-sync-pkgdb f25-docker;/usr/local/bin/owner-sync-pkgdb f26-docker" + cron_file=update-koji-owner-fedora-docker + when: inventory_hostname.startswith('bodhi-backend03') and env == "production" + tags: + - bodhi - bodhi # # cron job that syncs updates to master mirror diff --git a/roles/bodhi2/backend/templates/owner-sync-pkgdb.j2 b/roles/bodhi2/backend/templates/owner-sync-pkgdb.j2 index 38ea282..3423aca 100755 --- a/roles/bodhi2/backend/templates/owner-sync-pkgdb.j2 +++ b/roles/bodhi2/backend/templates/owner-sync-pkgdb.j2 @@ -80,12 +80,17 @@ if __name__ == '__main__': print "ERROR: no tag specified!\n" usage() - if tag.startswith('epel'): - version = tag.split('epel')[1] - elif tag.startswith('f'): - version = tag.split('f')[1] + if 'docker' in tag: + namespace='docker' + version = tag.split('-')[0].split('f')[1] else: - version = tag.split('-')[1][:-1] + namespace='rpms' + if tag.startswith('epel'): + version = tag.split('epel')[1] + elif tag.startswith('f'): + version = tag.split('f')[1] + else: + version = tag.split('-')[1][:-1] data = requests.get(urljoin(BASEURL, 'api/collections'), verify=VERIFY).json() branch_names = set() @@ -109,7 +114,7 @@ if __name__ == '__main__': if version == rawhide: reponame = 'master' else: - reponame = tag + reponame = tag.split('-')[0] {% if env == 'staging' %} arches = ["primary"] {% else %} @@ -120,7 +125,7 @@ if __name__ == '__main__': sys.exit(1) data = requests.get(urljoin(BASEURL, 'api/vcs?format=json'), verify=VERIFY).json() - acls = data['rpms'] + acls = data[namespace] pkgs = {} for pkg_name in acls: try: -- 1.8.3.1

3 4

How to move Fedora Badges from Trac
by Justin W. Flory 03 Nov '16

03 Nov '16

Hello all, I'm sending this out on a few different mailing lists, but it's something that will require participation and effort from a few different groups. I filed a ticket in the Fedora Infrastructure Pagure about migrating from Trac for Fedora Badges. This is picking up from an earlier discussion that Zach Villers (aikidouke) started on the mailing lists a couple months ago. In the ticket, I've tried to summarize the major pain points for migrating this Trac. A comprehensive overview can be found there. https://pagure.io/fedora-infrastructure/issue/5553 I would like to ask anyone who is involved with Fedora Badges, past or present, to please review this ticket and offer feedback to the issues raised in the ticket. I think of all the Tracs on FedoraHosted, this will be the most complex one to migrate because we have a lot of other components dependent on Trac or the FedoraHosted domain. It's important to start this discussion early than late. Even if you're not involved with Fedora Badges but might have ideas or advice on some of the problems raised here, your feedback would also be welcome! Thanks all. -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

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

02 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-03) #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 infra-docs git hooks fixed up - patrick #info ansible updated to 2.2.0.0 on batcave01 - kevin #info November apprentice nag out, all apprentices please answer - 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 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 more outreach / improving onboarding - stickster / kevin #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

Freeze break request: re-enable running rpmlint/rpmgrill in taskotron-prod
by Martin Krizek 02 Nov '16

02 Nov '16

Hi, just before freeze break started we accidentally mis-configured taskotron-trigger not to run rpmlint/rpmgrill. The following patch fixes that: diff --git a/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 b/roles/taskotron/taskotron index c9fb122..b0a6d00 100644 --- a/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 +++ b/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 @@ -4,6 +4,10 @@ do: - {tasks: [rpmlint, rpmgrill, python-versions]} - {discover: {repo: '{{ trigger_distgit_repo_url }}/rpms-checks/${name}.git', branch: "${distgit_bra +{% else %} +- when: {message_type: KojiBuildPackageCompleted} + do: + - {tasks: [rpmlint, rpmgrill]} {% endif %} - when: {message_type: KojiBuildDockerCompleted} do: +/-1? Thanks, Martin

3 2

Warn secondary arch folks about change involving: ExclusiveArch or ExcludesArch
by Pierre-Yves Chibon 02 Nov '16

02 Nov '16

Good Morning, Rel-eng has been wanting a got hook that would notify the people involved with secondary arches about changes made to packages involving ExclusiveArch or ExcludesArch. I took a stab at this hook today and I would like to offer the result for review. So with this email is an ansible patch adding the hook and installing it in our repos. Things that needs to be tweaked: - Where to send the email? - Turn off debug after we confirmed it works - Currently I install the script as a file not a template, so the URL to point to commits in CGIT will be the same in prod and in stg. Comments and thoughts more than welcome :) Pierre

4 10

fedorahosted sunset: need export of spacewalk Trac db
by Grant Gainey 02 Nov '16

02 Nov '16

Hey folks, The last thing spacewalk needs to move off of fedorahosted is our Trac wiki. Can someone give me a pointer to how to get a copy/export of the current state of the wiki so we can start testing the move-to-github process? I'm assuming (but don't know for sure) that we're using the default SQLite db. Thanks, Grant Gainey -- Grant Gainey Principal Software Engineer, Red Hat Satellite

3 5

PROPOSAL: employ a variant of upstream dist-git package into FedoraInfra
by Michal Novotny 01 Nov '16

01 Nov '16

Hey, I'd like to propose employment of an upstream dist-git package for deploying pkgs machines. This is the package I have in mind: https://github.com/release-engineering/dist-git. This package contains scripts and selinux policy for dist-git files. Note however that I would like to make this package as compatible with the infra dist-git as possible and that amounts to great deal of changes (main one being usage of /srv/ to store repositories and tarballs). I have forked the original repo into https://github.com/clime/dist-git and will continue development from there. The changes are going to be major so the main code-base could be e.g. here https://pagure.io/group/Fedora-Infra in the end. So far I have been testing only one use-case based on https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Impo… . I will collect all the other use-cases and ideally write a suite of regression tests based on that. I know pkgs.fedoraproject.org is somehow related to pagure but I need to additionally investigate this. I would like to hear the tribe now. Thank you clime

5 6

[release] tahrir-api: 0.8.1
by Sayan Chowdhury 01 Nov '16

01 Nov '16

0.8.1 ----- Pull Requests - (@sayanchowdhury) #40, Fix the version of SQLAlchemy which broke while doing the release https://github.com/fedora-infra/tahrir-api/pull/40 Commits - 210aa79ae Fix the version of SQLAlchemy which broke while doing the release https://github.com/fedora-infra/tahrir-api/commit/210aa79ae

1 0

Self Introduction: Saurabh Badhwar
by Saurabh badhwae 01 Nov '16

01 Nov '16

1 0

Ticket #5156 Write SOP for fedora-tagger
by carlo 01 Nov '16

01 Nov '16

Hi everybody, I have written the SOP for the fedora-tagger, since I don't have yet commit right to the infra-docs repository I can't update it myself. Therefore I have been suggest to send this email containing the doc itself. Special thanks to pingou for the guidance, it's my first contribution to the fedora project. Regards Carlo.

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2016