infrastructure November 2016

infrastructure@lists.fedoraproject.org

58 participants
65 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2016