infrastructure August 2015

infrastructure@lists.fedoraproject.org

41 participants
45 discussions

[release] pagure: 0.1.22
by Pierre-Yves Chibon 07 Aug '15

07 Aug '15

Hi everyone, I just released a new version of pagure: 0.1.22 Here is its changelog: * Fri Aug 07 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.22 - Update to 0.1.22 - Adjust the README to the current state of pagure - Rework how we integrate our custom tags into markdown to avoid the infinite loop we run into once in a while It is currently running in stg and in production, so far no problem :) Thanks, Pierre

1 0

Freeze Break Request - new fedimg release
by Ralph Bean 07 Aug '15

07 Aug '15

We found a bug in fedimg today that is causing all new images to fail to be uploaded to AWS (fedimg is constructing an invalid koji url and so is failing to download the images in the first place). This patch fixes it: https://patch-diff.githubusercontent.com/raw/fedora-infra/fedimg/pull/32.pa… I've cut a new python-fedimg-0.6.2 release and am looking for two +1s to push it out. -Ralph

2 1

Meeting Agenda Item: Introduction Tempanoi
by tempanoi＠openmailbox.org 06 Aug '15

06 Aug '15

Good day: I introduce myself, I've infrastructure projects, I like networks have studied Cisco CCNA, I like the security and my experience in linux is as administrator, little shell programming, Saas cloud service projects with Alcatel Lucent technology. I used linux in mobile telecommunications companies, I made plans for my house: The last one dlna and storage server (fedora server) My interests: Programming, security, and home automation projects (installed on raspberry) and automate homes. My nickname in irc: Tempanoi

1 0

Freeze break request? Pagure update (round 3)
by Pierre-Yves Chibon 06 Aug '15

06 Aug '15

Hi everyone, A few time this week and earlier today, I have received error emails from pagure about markdown going into an infinite loop. Something like: http://fpaste.org/252172/14388640/ Today, it seems to have last for a few minutes since I got 600+ emails for this problem. Restarting apache solved it, until the next hick-up. So I went and rework how we integrate our custom patterns in markdown: https://pagure.io/pagure/pull-request/324 (Note: while I hope this fixes the issue I've seen, since I was never able to replicate it, it's just a hope) That and a change to the README file are the only changes since the last release. With the idea of polishing pagure before flock, I would like to ask your opinion about updating pagure again this week :) Thanks for your time, Pierre

3 2

Plan for tomorrow's Fedora Infrastructure meeting - 2015-08-06
by Kevin Fenzi 05 Aug '15

05 Aug '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-08-06 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 (2015-08-06) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson #topic New folks introductions / Apprentice feedback #topic GSoC student update - kushal = 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 NOTICE: There will be no meeting on 2015-08-13 as many people will be at flock - kevin #info fixed easyfix (had a broken dir from sundries move) - kevin #info moved planet to fedoraplanet.org - kevin/til #info fixed qadevel backups (needed to adjust rdiff-backup ) - kevin #info fixed up rsync on s390 hub - 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 TRAC tickets review - p_klos #topic = 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: add robots.txt to public facing taskotron instances
by Tim Flink 05 Aug '15

05 Aug '15

For some reason, yahoo's bot has been hitting our taskotron instance really hard all of a sudden - slowing it down enough to trigger nagios alerts twice this week. There is a robots.txt served by the buildmaster instance but since that isn't at the webroot in our setup, bots may not read it. I'd like to add a robots.txt to the public facing taskotron instances so that we can avoid this in the future. Rendered content of the robots.txt is at the end of this email. I've already deployed the file to taskotron-dev which can be seen at: http://taskotron-dev.fedoraproject.org/robots.txt Proposed content would be at: http://taskotron.stg.fedoraproject.org/robots.txt http://taskotron.fedoraproject.org/robots.txt Tim User-agent: * Disallow: /taskmaster/waterfall Disallow: /taskmaster/builders Disallow: /taskmaster/changes Disallow: /taskmaster/buildslaves Disallow: /taskmaster/schedulers Disallow: /taskmaster/one_line_per_build Disallow: /taskmaster/grid Disallow: /taskmaster/tgrid Disallow: /taskmaster/json

3 3

[FBR] Pagure configuration update
by Pierre-Yves Chibon 05 Aug '15

05 Aug '15

Hi, I have made the change for stg but since this one touches prod I'd like to have a couple of +1: --- roles/pagure/frontend/templates/pagure.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/pagure/frontend/templates/pagure.cfg b/roles/pagure/frontend/templates/pagure.cfg index c0c7101..a79d697 100644 --- a/roles/pagure/frontend/templates/pagure.cfg +++ b/roles/pagure/frontend/templates/pagure.cfg @@ -48,8 +48,8 @@ DOC_APP_URL = 'https://docs.pagure.org' GIT_URL_SSH = 'ssh://git@stg.pagure.io/' GIT_URL_GIT = 'https://stg.pagure.io/' {% else %} -GIT_URL_SSH = 'git(a)pagure.io' -GIT_URL_GIT = 'https://pagure.io' +GIT_URL_SSH = 'ssh://git@pagure.io/' +GIT_URL_GIT = 'https://pagure.io/' {% endif %} Thanks, Pierre

3 2

Pruning sponsors list
by Paul W. Frields 05 Aug '15

05 Aug '15

Our website includes a sponsor list, e.g.: <https://getfedora.org/en/sponsors> A little digging plus help from Jared Smith showed that Arrival Telecom and Technomonk are no longer sponsoring Fedora service. They each provided DID service back when we ran Fedora Talk. So unless there are objections, I'll trim them from future builds of the website. -- 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

1 1

Freeze break: add rsyncd to s390 hub
by Kevin Fenzi 05 Aug '15

05 Aug '15

This is needed so the content can be synced over to secondary01 and made live to end users. +1s? diff --git a/playbooks/groups/koji-hub.yml b/playbooks/groups/koji-hub.yml index aaccbca..be1843c 100644 --- a/playbooks/groups/koji-hub.yml +++ b/playbooks/groups/koji-hub.yml @@ -41,6 +41,7 @@ - apache - fedmsg/base - koji_hub + - { role: rsyncd, when: inventory_hostname.startswith('s390') } - { role: koji_builder, when: env == "staging" or inventory_hostname.startswith('s390') } - { role: nfs/server, when: env == "staging" } - { role: keepalived, when: env == "production" and inventory_hostname.startswith('koji') } and a new roles/rsyncd/files/rsyncd.conf.s390-koji01.qa.fedoraproject.org file: pid file = /var/run/rsyncd.pid syslog facility = daemon dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.bz2 *.iso use chroot = false transfer logging = false exclude = .snapshot/ .~tmp~/ /.private/ /.private/** **/.nfs* # For distributing applications [log] comment = Server Logs path = /var/log uid = root gid = root read only = yes hosts allow = 10.5.126.13 192.168.1.59 [fedora-s390] comment = Fedora s390 content path = /mnt/koji/tree/ uid = root gid = root read only = yes hosts allow = 10.5.126.27

3 5

Freeze break request? Pagure update (round 2)
by Pierre-Yves Chibon 05 Aug '15

05 Aug '15

Hi everyone, So there has been some changes to pagure that I would like to push forward, here is the detail: - Make the SSH protocol explicit for the SSH URLs (Till Maas) - Improve/Fix/Rework pagure's documentation - Rework the doc server to make it display what's in the repo directly (so you can directly put there the output of your sphinx build, or your rst/md/text files) - Install properly the post-receive hook on the tickets and requests hooks (hotfixed in prod) - Give proper attribution to the pagure logo to Micah Deen in the documentation As you see, nothing major for the main application, but the change to the doc server and doc integration into the main app would be helpful. Thoughts on pushing this forward? Thanks, Pierre

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2015