infrastructure December 2016

infrastructure@lists.fedoraproject.org

48 participants
42 discussions

EPEL-only packages
by Aurelien Bompard 13 Dec '16

13 Dec '16

Hey people, I'm in a situation that I don't think is covered by the guidelines. Here's the thing: RHEL/CentOS ships some python packages in their Python 2 version, but not for Python 3 since RHEL/CentOS does not ship Python 3. Let's take the example of python-zope-interface. I need the python3 version, so I thought I'd adapt the existing python-zope-interface package we have to only build the Python 3 version in EPEL. Then Kevin told me that this was a bad idea because koji (I think it was koji?) works on source packages, and won't like having two python-zope-interface packages, one from RHEL/CentOS and one from EPEL. So I built a python3-zope-interface package that only builds the Python3 version. It got accepted, it builds fine, but now I realize that I don't want this package to be built for Rawhide, since Rawhide already has the Python 3 version of Zope Interface (built from the main package, as usual). I removed the spec file from the master branch in git and put a README explaining all that, but I wonder if our release engineering process will like that. Do I need a special exception, as we have for orphan packages, so it does not error out? I don't know if I have been clear, if not please ask me to rephrase. Thanks for your insight! Aurélien

2 1

Weekly Koji Infra Tag Report
by Nobody 11 Dec '16

11 Dec '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

1 0

Plan for tomorrow's Fedora Infrastructure Meeting 2016-12-08
by Stephen John Smoogen 07 Dec '16

07 Dec '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-12-08 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. ---------------------------- = 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-12-01) #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 kevin and patrick in PHX2 #info lots of hardware problems being dealt with #info copr down for 12+ hours due to unknown issue #info new buildvmhosts installed #info osbs being redeployed. #info FLAG DAY FOR KERBEROS CHANGEOVER NEXT WEEK = 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 FLAG DAY https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… = 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. = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

fedorahosted.org migration - Trac to Github Wiki tool available
by Grant Gainey 06 Dec '16

06 Dec '16

Hey folks, We're working on getting fedorahosted.org/spacewalk/wiki moved over to Github, because that's where our code lives. One of the requirements we have, is to move our existing large-ish Trac wiki, and all 8 years of its history, over to github, and transform it from Trac markup to Markdown markup. While there are a couple of attempts at this out on the web, they're generally only concerned with most-recent-version, and have a variety of limitations. So I pulled together some python to automate as much of the process as I could manage in a few days. Since I expect there are other Trac wikis out there that are in the same boat, I figured y'all might want to take a look at the tool I threw together: https://github.com/ggainey/tracwiki2githubwiki You can see its output in my clone of the spacewalk project: https://github.com/ggainey/spacewalk/wiki/WikiStart (Note: That content will disappear and reappear occasionally, as I blow it away and regenerate it while testing) I am certain this code needs...help (among other things, programming in Python, Java, PL/SQL, and Perl on a daily basis means my coding-style kinda sucks, and is def. not very Python-y) However, it does a reasonably good job, and I hope it'll be useful to some of the other folk still managing their migration Elsewhere. If/when/as you find problems with the tool, feel free to open an Issue on github. Thanks, and enjoy, G (PS - If you want to hear me babble about it in a quick demo for my team, this link should be public: https://bluejeans.com/s/BFO9@/ Requires Flash, alas ) -- Grant Gainey Principal Software Engineer, Red Hat Satellite

2 1

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

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by Randy Barlow 05 Dec '16

05 Dec '16

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2016-12-06 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

Weekly Koji Infra Tag Report
by Nobody 04 Dec '16

04 Dec '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 Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- libphutil, f23-infra tflink arcanist, f23-infra tflink phabricator f23-infra tflink phabricator-extension-ipsilonauth f23-infra tflink libphutil f23-infra tflink arcanist f23-infra tflink f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin phabricator-extension-oauth f24-infra tflink python-twill f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-skin-fedora f24-infra puiterwijk mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk phabricator f24-infra tflink mediawiki-Lockdown f24-infra kevin libphutil f24-infra tflink arcanist f24-infra tflink mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- fas f25-infra kevin libphutil, f25-infra tflink arcanist, f25-infra tflink phabricator f25-infra tflink phabricator-extension-ipsilonauth f25-infra tflink libphutil f25-infra tflink arcanist f25-infra tflink

1 0

[release] pagure: 2.10.1
by Pierre-Yves Chibon 04 Dec '16

04 Dec '16

Good Morning everyone, I just cut a small bug-fix release of pagure: 2.10.1. Here is its changelog: * Sun Dec 04 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.1-1 - Update to 2.10.1 - Clean up the JS code in the settings page (Lubomír Sedlář) - Fix the URLs in the `My Issues` and `My Pull-request` pages I hope to push it to prod, either later today or tomorrow morning. Happy hacking! Pierre

1 0

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] pagure: 2.10
by Pierre-Yves Chibon 02 Dec '16

02 Dec '16

Good Morning everyone, I just cut a new release of pagure: 2.10. Here is the corresponding changelog: * Fri Dec 02 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10-1 - Update to 2.10 - Updating language on not found page (Brian (bex) Exelbierd) - Add a view for open pull requests and issues (Jeremy Cline) - Issue 1540 - New meta-data custom field type of "link" (Mark Reynolds) - Fix overflow issue with comment preview and pre (Ryan Lerch) - Issue 1549 - Add "updated_on" to Issues and make it queryable (Mark Reynolds) - Drop UPLOAD_FOLDER in favor of UPLOAD_FOLDER_URL - Make the group_name be of max 255 characters - Bug - Update documentation to match the default EMAIL_SEND value (Michael Watters) - Change - Fix grammar in UI messages around enabling/deactivating git hooks (Michael Watters) - Allow resetting the priorities of a project - Several fixes and enhancements around the activity calendarheatmap - Add quick_replies field to project (Lubomír Sedlář) - Fix blaming files containing non-ascii characters (Jeremy Cline and I) - Include regular contributors when checking if user is watching a project - List subscribers on the issue pages (Mark Renyolds and I) Admins of pagure instances, do watch for the configuration change regarding the UPLOAD_FOLDER/UPLOAD_FOLDER_URL. Thanks to all the contributors who helped making this release! This is currently only running in stg, I will update prod either this week-end or on Monday. This may take a while since I'll have to load from disk all the activity logs. Happy hacking! Pierre

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2016