infrastructure June 2016

infrastructure@lists.fedoraproject.org

45 participants
52 discussions

(no subject)
by Patrick Uiterwijk 06 Jun '16

06 Jun '16

Hi, This will fix our openshift key sync issues, allowing all -noc people to again update status. Can I get +1s? Patrick

4 4

Coming to you this summer
by Pierre-Yves Chibon 04 Jun '16

04 Jun '16

Dear all, We have a number of milestones due by the end of the summer (flock for some, end of august for the others), I thought it would be nice to try to list and present them. There are four apps that are mainly concerned: Pagure, FAS, python-fedora and fedora-hubs. * Pagure There are three main goals for pagure for this summer: - Support for private git repos (Farhaan Bukhsh) - Pagure/Jenkins integration (Farhaan Bukhsh) - Adjust pagure and crons to have pagure run at pkgs.fp.o (Vivek Anand) The deadline for these is the end of august (the end of GSoC) * FAS The main goal for FAS is: getting FAS3 running in stg, before flock. This is going to be a team effort from: Xavier, Patrick, Szymon and I. * python-fedora As above, the main idea here is to get it adjusted for FAS3 before flock so that eventually at flock we can do a small hackfest on porting apps to FAS3. Regarding FAS3 and python-fedora, the idea is to get FAS3 running in stg asap, next to FAS2, finish/polish things around python-fedora and when that is done, break stg by removing FAS2 and then work on every apps using FAS2 to port them to FAS3. The day we push FAS3 and the day we drop FAS2 will of course be announced so we can start testing FAS3 and then fixing the apps. * Fedora-Hubs The basic idea for hubs is to get a demo running in time for flock. This will also be a team effort together with: devyani7 (GSoC), Szymon (RH Intern), Eric (RH Intern), Radhika (RH Intern), Máirín, Ryan and I. Of course the names listed there do not mean that only those people can work on these projects, as usual everyone is welcome to join one or all of these project, the more the merrier :) Thanks for your attention, Pierre

2 2

Basset now has trac blocking
by Patrick Uiterwijk 02 Jun '16

02 Jun '16

Hi all, Another quick update: as of right now, Basset will also block users cross-trac instance. This is indicated by an internal error saying "Denied service to $username." This will make sure that spambots are even more limited with regards to the amount of spam they can place. If a user complains about this, see the Basset SOP on how to undo this block. Regards, Patrick

1 0

Freeze break request: Basset trac blocking
by Patrick Uiterwijk 02 Jun '16

02 Jun '16

Hi, I have now finished blocking for Trac by Basset. Can I get a freeze break exception to update the following: trac-basset-plugin on hosted03 from 0.2 to 0.7*. basset on basset01 from 0.6 to 0.7. The main changes are: https://pagure.io/basset/c/afd3e1b3793c078eb398d2fa090b4e467bd4a276 and https://pagure.io/basset/c/d951e6abbd191c42568af3949e43c0f8b787c346 *: The jump from 0.2 to 0.7 in the trac plugin is because the trac plugin is now part of the main basset spec file, meaning less over head for me. Regards, Patrick

3 2

Basset update
by Patrick Uiterwijk 01 Jun '16

01 Jun '16

Hi all, Just a quick update that at this moment Basset also handles trac attachments. Next up will be to deploy the trac block plugin and integrate that with Basset. I'll finish that tomorrow, so more FBRs will come in by then. Regards, Patrick

1 0

Freeze break request: Basset trac update 2 of ?, trac attachment support
by Patrick Uiterwijk 01 Jun '16

01 Jun '16

Hi, The next FBR: can I have +1s to update Basset to 0.5-rc1? This includes support for handling Trac attachments: https://pagure.io/basset/c/a27c873b2676b2d02d72aa443234d644fdaa13e1 Regards, Patrick

3 3

Plan for tomorrow's Fedora Infrastructure meeting - 2016-06-02
by Kevin Fenzi 01 Jun '16

01 Jun '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-06-02 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-06-02) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson #topic New folks introductions / Apprentice feedback = 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 We are now in Fedora 24 Final freeze - everyone #info fix_arm_soc.yml playbook ready for use, see it for docs - 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 supybot-gribble fork: https://github.com/ProgVal/Limnoria plans - kevin #topic split notifications from scm-commits to new list? - kevin #topic = Apprentice 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. #topic Apprentice office hours = 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: modularity from a high level - threebean = Meeting end stuff = #topic Open Floor #endmeeting

1 0

Post-action freeze break request: increase basset drive size
by Patrick Uiterwijk 01 Jun '16

01 Jun '16

Can I get +1s for increasing basset01's drive size? Ansible commit: http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=8039a85

3 2

Freeze break request: Basset Trac update 1 of X, trac plugin
by Patrick Uiterwijk 01 Jun '16

01 Jun '16

Hi all, I will be requesting a couple of freeze breaks for Basset in the coming hours/days to add support for Trac attachments, add fields that the spammers decided they could use for spam, and for a Trac blocking plugin that will allow us to make sure that users can actually be blocked at Trac. Right now, I would like +1s for the Trac plugin to submit attachment information to Basset. The only code change is here: https://pagure.io/basset/c/09ed19d46587d5104928d933c394c34698f6959b And the new build here: http://koji.fedoraproject.org/koji/taskinfo?taskID=14340045 Thanks, Patrick

3 2

Freeze break: Make critpath download cronjob silent
by Martin Krizek 01 Jun '16

01 Jun '16

Hi, per request: 18:12 < nirik> tflink: can you make this cron job not send emails: Subject: Cron <root@taskotron-stg01> wget -O /var/lib/taskotron-trigger/critpath_whitelist https://admin.fedoraproject.org/pkgdb/api/critpath?format=json && chown fedmsg:fedmsg /var/lib/taskotron-trigger/critpath_whitelist Patch follows: commit f8852ed89ce6d2dd1c0ab585c3e54c3853378be2 Author: Martin Krizek <mkrizek(a)redhat.com> Date: Wed Jun 1 17:50:22 2016 +0000 Make critpath download cronjob silent diff --git a/roles/taskotron/taskotron-trigger/tasks/main.yml b/roles/taskotron/taskotron-trigger/tasks/main.yml index 04d81ba..7cf40f0 100644 --- a/roles/taskotron/taskotron-trigger/tasks/main.yml +++ b/roles/taskotron/taskotron-trigger/tasks/main.yml @@ -47,7 +47,7 @@ cron: name="download crithpath list" special_time=daily - job="wget -O {{ trigger_critpath_file }} {{ trigger_critpath_url }} && chown fedmsg:fedmsg {{ trigger_critpath_file }}" + job="{ wget -O {{ trigger_critpath_file }} {{ trigger_critpath_url }}; chown fedmsg:fedmsg {{ trigger_critpath_file }}; } >& /dev/null" - name: copy tmpfiles.d for trigger distgit cache template: src=tmpfiles.d.trigger.conf.j2 dest=/etc/tmpfiles.d/trigger.conf owner=root group=root mode=0644 +1? Thanks, Martin

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure June 2016