infrastructure May 2015

infrastructure@lists.fedoraproject.org

55 participants
80 discussions

Plan for tomorrow's Fedora Infrastructure meeting (2015-05-28)
by Kevin Fenzi 27 May '15

27 May '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-05-21 at 18:00 UTC in #fedora-meeting on the freenode network. This week we are continuing to try something new. 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 this morning 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-05-28) #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 Fedora 22 RELEASED! - everyone #info we are out of f22 freeze. Next stop f23 alpha - kevin #info Fedora Hubs brainstorming session last week went well. Next steps are to vet prototype and design. - ralph #link https://github.com/ralphbean/fedora-hubs-prototype#a-picture-is-worth #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 Taiga update and packaging policy question - ralph #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: Openvpn in Fedora infrastructure - kevin = Meeting end stuff = #topic Open Floor #endmeeting

1 0

joining fedora from Croatia
by Ivan (gmail) 27 May '15

27 May '15

Hello everyone. My name is Ivan. I live in Croatia. I want to expand the fedora community that we Croatian people contribute to the community. First of all would like to thank friends from the Hungarian that I met at DORS / CLUC in Zagreb; Zoltan hoppar, Zacharias Mitzelos and Gergely Rakosi I am happy that I was accepted into the community. Please if you could direct me further All the best to everyone. May the source be with you

4 5

Fedora 22 Final Freeze now in effect
by Kevin Fenzi 27 May '15

27 May '15

Greetings. we are now in the infrastructure freeze leading up to the Fedora 22 Final release. This is a final release freeze. This means that hosts that are marked as freezing should not have any changes made to them except as part of a freeze break request (see below) We do this to make sure that our infrastructure is stable to allow for building/composing/testing and distributing Fedora 22. This freeze will end 1 day after Fedora 22 is released. (Currently scheduled for 2015-05-26) Freeze breaks should be sent to this list, clearly describing the planned change and include patches (if applicable). Freeze breaks should not be applied until they have gotten at least 2 +1's from members of sysadmin-main and/or releng groups. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone http://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory Thanks, kevin

1 1

Meeting Agenda Item: Sergio gonzalez
by sergio gonzalez 27 May '15

27 May '15

Hello my name is sergio gonzalez and i'm live in argentina, mi irc is:hackendemoniado I'm a student of engineering in systems, and I want to collaborate scheduled and reporting bugs, want to learn about the steps to report bugs and how to find them if you need more information just write me an email

2 2

Meeting Agenda Item: Introduction Bruno
by Bruno Miguel Queiros 27 May '15

27 May '15

Hello guys My name is Bruno, i'm from Portugal (timezone UTC) and my IRC handle on freenode.net is lnxslck. I work as a Linux System Administrator for the past 6 years, and have been working with Linux for 15 years or so, (my first distro was RedHat 5 i believe). I would like to help the infrastructure team, mostly on server issues like load balancing, high availability, increasing speed on http connections or to the databases, but i would also like to help wherever i feel comfortable, security issues, translations, etc. I'm already helping on AskFedoraProject forum, and i want to start small with 2 to 4 hours a week (just to begin with) on volunteering. I'm expecting to increase those hours, as i feel more comfortable within the tasks and the project itself. I'm also looking for a sponsor, so if you got the patience i would love a hand. Thanks and sorry for the long email. Best regards Bruno

2 2

[release] pagure: 0.1.8
by Pierre-Yves Chibon 27 May '15

27 May '15

Good morning everyone, I just cut and pushed a new version of pagure: 0.1.8 Here is its changelog: * Wed May 27 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.8-1 - Update 0.1.8 - Add the possibility to do Asynchronous in-line comment posting (Patrick Uiterwijk) - Handle the situation where the branch asked is not found in the git repo - Handle the situation where we cannot find a desired commit - Do not display a value in the settings page if there are none - Rework the pull-request view to move the list of commits into a tab - Make email sending optional (Patrick Uiterwijk) Patrick's work will make reviewing PR much easier and smooth :) Pierre

1 0

[freeze break request] Another attempt at fixing collectd on proxies/apache boxes
by Ricky Elrod 26 May '15

26 May '15

SELinux is blocking collectd from connecting to apache on localhost. Also our config was missing an Instance tag, which seems to be required, at least on the rhel7 version of collectd-apache. I'd like to have this working so we have apache graphs of the release tomorrow. +1's? -Ricky commit 9b3821d1b99df9719e63cdecdb11647966e0635e Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Mon May 25 19:28:08 2015 +0000 Toggle sebool and fix missing Instance tag to collectd-apache working Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/collectd/base/files/apache.conf b/roles/collectd/base/files/apache.conf index dacd82a..441da4c 100644 --- a/roles/collectd/base/files/apache.conf +++ b/roles/collectd/base/files/apache.conf @@ -1,6 +1,8 @@ LoadPlugin apache <Plugin apache> + <Instance "apache"> URL "http://localhost/apache-status?auto" + </Instance> </Plugin> diff --git a/roles/collectd/base/tasks/main.yml b/roles/collectd/base/tasks/main.yml index 210e7d9..697c8cb 100644 --- a/roles/collectd/base/tasks/main.yml +++ b/roles/collectd/base/tasks/main.yml @@ -56,6 +56,14 @@ - restart collectd when: collectd_apache is defined +- name: Let collectd talk to apache over tcp + seboolean: name=collectd_tcp_network_connect state=yes persistent=yes + tags: + - collectd + ignore_errors: True + notify: + - restart collectd + when: collectd_apache is defined # Three tasks for handling our (two) custom selinux modules. - name: ensure a directory exists for our custom selinux module

3 2

[freeze break request] Add ResolveInterval option to collectd clients
by Ricky Elrod 26 May '15

26 May '15

By default collectd's Network module won't attempt to re-resolve hostnames if it fails for some reason (e.g. network not being available when it's first started). However there's a fairly recently added option called ResolveInterval which will force it to re-resolve after N seconds if it fails. The example in the collectd repo uses 4 hours (14400 seconds) so I used that, but we could probably bump it down a bit if we wanted. Patch follows. commit 34138a9e598a4fad54380ef692d70c71d7e08e41 Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Mon May 25 03:33:34 2015 +0000 [collectd/base] re-resolve dns lookup after a few hours if it fails see: https://github.com/collectd/collectd/pull/732 Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/collectd/base/files/network-client.conf b/roles/collectd/base/files/network-client.conf index a6bd125..53f74b7 100644 --- a/roles/collectd/base/files/network-client.conf +++ b/roles/collectd/base/files/network-client.conf @@ -2,4 +2,5 @@ LoadPlugin network <Plugin "network"> Server "log01" + ResolveInterval 14400 </Plugin>

3 3

[freeze break request] make collectd_apache a default of the apache role.
by Ricky Elrod 25 May '15

25 May '15

We have a lot of app servers where collectd_apache isn't set (presumably people just forgot to set it). So we haven't been graphing apache metrics for those app servers. :( I'd like to propose just making it a default of the apache role. I tested this on wiki01.stg in 8f182ff510fef867fb1febd7afb51e263251760b and 74ad22a53d1230633b2bb284bcea3e494c018f59, with success. Patch follows. commit 71031420b5713aae175a1761a4db932b08bdf0b9 Author: Ricky Elrod <codeblock(a)fedoraproject.org> Date: Mon May 25 04:22:52 2015 +0000 Test defining collectd_apache in the apache role. Signed-off-by: Ricky Elrod <codeblock(a)fedoraproject.org> diff --git a/roles/apache/defaults/main.yml b/roles/apache/defaults/main.yml new file mode 100644 index 0000000..372da7b --- /dev/null +++ b/roles/apache/defaults/main.yml @@ -0,0 +1,2 @@ +--- +collectd_apache: true

3 2

[Piotr.Maluty@grupaonet.pl: New public mirror Fedora PL.]
by Adrian Reber 25 May '15

25 May '15

There is a fix missing, I think for varnish, to make the mirrormanager flask application work without a '/' at the end. Would be good if this could be added. I changed the MirrorManager instructions in the wiki to point to the correct URL to avoid troubles like this. Adrian ----- Forwarded message from Maluty Piotr <Piotr.Maluty(a)grupaonet.pl> ----- Date: Mon, 25 May 2015 18:08:38 +0200 From: Maluty Piotr <Piotr.Maluty(a)grupaonet.pl> To: "'mirror-admin(a)fedoraproject.org'" <mirror-admin(a)fedoraproject.org> Subject: New public mirror Fedora PL. Hi, I run mirror Fedora in Poland. HTTP: http://mirror.onet.pl/pub/mirrors/fedora/linux/ FTP: ftp://mirror.onet.pl/pub/mirrors/fedora/linux/ RSYNC: rsync://mirror.onet.pl/pub/mirrors/fedora/ Sync schedule: 4 times/day Bandwidth: 10Gb/s Location: Poland Sponsor: Grupa Onet.pl S.A. Sponsor URL: http://www.onet.pl/ IP : 213.180.139.200, 2a02:c10:2170:4::bebe Email contact: piotr.maluty(a)grupaonet.pl<mailto:piotr.maluty@grupaonet.pl>. follow instructions and get an error. Not Found The requested URL /mirrormanager was not found on this server. Apache/2.2.15 (Red Hat) Server at localhost Port 6081 Pozdrawiam Piotr Maluty Administrator Systemow Grupa Onet.pl SA ul. Bobrzynskiego 12 E 30-348 Krakow tel.: +48 600 206 065 _______________________________________________ Mirror-admin mailing list Mirror-admin(a)fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/mirror-admin ----- End forwarded message -----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure May 2015