Re: FBR: Set resultsdb wsgi to normal values

2017-03-17 Thread Stephen John Smoogen
Thank you for the patch. This needs to be 'fixed' later to use the wsgi_* variables that other services use. On 17 March 2017 at 21:13, Patrick Uiterwijk wrote: > Hi, > > Can I get retroactive +1s for the patch? > This drops the number of threads and processes down to normal limits: > having 200

FBR: Set resultsdb wsgi to normal values

2017-03-17 Thread Patrick Uiterwijk
Hi, Can I get retroactive +1s for the patch? This drops the number of threads and processes down to normal limits: having 200 * 20 + 100 * 10 = 5000 threads for wsgi is... not going to work. Patrick commit 66172d7738bbee3749520b025a24b8930e5fd2c0 Author: Patrick Uiterwijk Date: Sat Mar 18 0

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Stephen John Smoogen
Are the files also moved to the correct template directory or are they there already? If they are there already +1 On 17 March 2017 at 20:07, Patrick Uiterwijk wrote: > Turns out I'll need a follow-up... > > Can I get +!s to also apply the following to make this actually work? > > Moved roles/ani

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Kevin Fenzi
+1 sorry for not noticing that on the first patch. ;( kevin signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le.

Re: Freeze break: set pagure serveradmin

2017-03-17 Thread Stephen John Smoogen
+1 On 17 March 2017 at 15:56, Kevin Fenzi wrote: > This is a simple little tweak that fixes pagure saying: > > "Contact root@localhost" when it emits a 500 error. > > This would fix ticket: > https://pagure.io/fedora-infrastructure/issue/5906 > > +1s? > > kevin > -- > diff --git a/roles/pagure/fr

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Stephen John Smoogen
+1 here On 17 March 2017 at 19:33, Kevin Fenzi wrote: > +1 here. Please do. > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > --

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Patrick Uiterwijk
Turns out I'll need a follow-up... Can I get +!s to also apply the following to make this actually work? Moved roles/anitya/frontend/files/0_releasemonitoring.conf -> roles/anitya/frontend/templates/0_releasemonitoring.conf Moved roles/piwik/files/piwik-httpd.conf -> roles/piwik/templates/piwik-h

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Kevin Fenzi
+1 here. Please do. kevin signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Peter Robinson
On Fri, Mar 17, 2017 at 11:29 PM, Patrick Uiterwijk wrote: > Hi, > > Turns out that these three services were not yet using our global > secure cipher set. > This means that they have the Apache defaults, which are quite > insecure (RC4 and no FS). > Can I please get +1s to apply the underneath pa

Re: Freeze break: set pagure serveradmin

2017-03-17 Thread Patrick Uiterwijk
On Fri, Mar 17, 2017 at 8:10 PM, Pierre-Yves Chibon wrote: > On Fri, Mar 17, 2017 at 01:56:50PM -0600, Kevin Fenzi wrote: >> This is a simple little tweak that fixes pagure saying: >> >> "Contact root@localhost" when it emits a 500 error. >> >> This would fix ticket: >> https://pagure.io/fedora-in

FBR: Update Pagure, Anitya and Piwik to use secure cipher set

2017-03-17 Thread Patrick Uiterwijk
Hi, Turns out that these three services were not yet using our global secure cipher set. This means that they have the Apache defaults, which are quite insecure (RC4 and no FS). Can I please get +1s to apply the underneath patch? Patrick commit 55183057fc95109df5d6b50258918c59c7930674 Author: P

Re: Freeze break: set pagure serveradmin

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 01:56:50PM -0600, Kevin Fenzi wrote: > This is a simple little tweak that fixes pagure saying: > > "Contact root@localhost" when it emits a 500 error. > > This would fix ticket: > https://pagure.io/fedora-infrastructure/issue/5906 > > +1s? Cool +1 for me :) Pierre >

Freeze break: set pagure serveradmin

2017-03-17 Thread Kevin Fenzi
This is a simple little tweak that fixes pagure saying: "Contact root@localhost" when it emits a 500 error. This would fix ticket: https://pagure.io/fedora-infrastructure/issue/5906 +1s? kevin -- diff --git a/roles/pagure/frontend/templates/0_pagure.conf b/roles/pagure/frontend/templates/0_pa

Re: FBR: Bodhi should stop sending error emails on success, and should start sending error emails on error

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 12:36:37PM -0600, Kevin Fenzi wrote: > Thanks for the details... > > I am still +1 to updating this, as I think it's better that we have the > known/current version in use rather than some "might be hotfixed" > version. Same here, even if that makes rolling back harder (

Re: SOP for Package Review

2017-03-17 Thread Kevin Fenzi
On Fri, 2017-03-17 at 04:56 -0600, InvalidPath wrote: > I'm going to attempt to write this, Im looking for any info anyone > currently has: > > hosting nodes? > backend db? > application names? > > Anything at all would be appreciated. This is a script that runs on sundries01 (and sundries01.stg

Re: Best practice for 3rd party playbook

2017-03-17 Thread Kevin Fenzi
On Fri, 2017-03-17 at 09:47 +0100, Miroslav Suchý wrote: > Hi, > I am in process in writing playbook for retrace.fedoraproject.org > > ABRT team created: > https://github.com/abrt/ansible-role-retrace-server > > Which we can use. I just wonder what is best practise for using such 3rd > party rol

Re: FBR: Bodhi should stop sending error emails on success, and should start sending error emails on error

2017-03-17 Thread Kevin Fenzi
Thanks for the details... I am still +1 to updating this, as I think it's better that we have the known/current version in use rather than some "might be hotfixed" version. kevin signature.asc Description: This is a digitally signed message part ___

Re: FBR: Bodhi should stop sending error emails on success, and should start sending error emails on error

2017-03-17 Thread Randy Barlow
I just remembered that I had never upgraded production to version 2017.0: https://github.com/fedora-infra/fedmsg-atomic-composer/releases/tag/2017.0 This means that if I install 2017.1 (which has the 1-char diff I asked for an FBR on) it will also be installing those changes. FWIW, most of those

Re: Freeze Break Request: increase threads for resultsdb_frontend wsgi daemon

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 10:26:47AM -0600, Tim Flink wrote: > Production resultsdb_frontend is also really slow and I'd like to > bump it's resources at the same time I bump resultsdb from the > other FBR. > > +1s? +1 Pierre > > From 9757a01edfe14a2455f523d0ac7cb8cfb4e92f8e Mon Sep 17 00:00:00

Re: Freeze Break Request: increase threads for resultsdb_frontend wsgi daemon

2017-03-17 Thread Kevin Fenzi
+1 kevin signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: increase threads for resultsdb wsgi daemon

2017-03-17 Thread Kevin Fenzi
+1 kevin signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Freeze Break Request: increase threads for resultsdb_frontend wsgi daemon

2017-03-17 Thread Tim Flink
Production resultsdb_frontend is also really slow and I'd like to bump it's resources at the same time I bump resultsdb from the other FBR. +1s? Tim From 9757a01edfe14a2455f523d0ac7cb8cfb4e92f8e Mon Sep 17 00:00:00 2001 From: Tim Flink Date: Fri, 17 Mar 2017 16:23:12 + Subject: [PATCH 2/2]

Re: Freeze Break Request: increase threads for resultsdb wsgi daemon

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 09:41:02AM -0600, Tim Flink wrote: > Production resultsdb is still really slow and we're still seeing the > occasional error on result posting so I'd like to bump the resources > allocated to the wsgi app again. I wonder if this doesn't saturate the server at one point I'm

Freeze Break Request: increase threads for resultsdb wsgi daemon

2017-03-17 Thread Tim Flink
Production resultsdb is still really slow and we're still seeing the occasional error on result posting so I'd like to bump the resources allocated to the wsgi app again. +1s? Tim From 3d45155959cbdcde39c1a98a584a100b590761db Mon Sep 17 00:00:00 2001 From: Tim Flink Date: Fri, 17 Mar 2017 15:33

Re: SOP for Package Review

2017-03-17 Thread Aurelie Deromedis
Hi Ben, I've found the Fedora link below in one of my searches: https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Package_Revie w_Process Cheers, Aurelie On Fri, 2017-03-17 at 04:56 -0600, InvalidPath wrote: > I'm going to attempt to write this, Im looking for any info anyone > current

Re: Freeze Break Request: enable package-specific tasks for Taskotron production

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 08:37:19AM -0600, Tim Flink wrote: > On Fri, 17 Mar 2017 09:37:07 +0100 > Pierre-Yves Chibon wrote: > > > On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote: > > > This has been pending for a long time and now that the bureaucratic > > > stuff has been figured out a

Re: Freeze Break Request: enable package-specific tasks for Taskotron production

2017-03-17 Thread Tim Flink
On Fri, 17 Mar 2017 09:37:07 +0100 Pierre-Yves Chibon wrote: > On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote: > > This has been pending for a long time and now that the bureaucratic > > stuff has been figured out and our dev/stg instances are running > > well, we'd like to enable pack

Re: FBR: Fix koji monitoring from noc02

2017-03-17 Thread Tim Flink
On Fri, 17 Mar 2017 13:28:31 + Patrick Uiterwijk wrote: > Hi all, > > So, our noc02 monitoring of Koji build targets broke because the > modularity stuff pushed rawhide to the second page :). > Can I get +1s to start testing for "infra" instead, which should match > $release-infra and such?

Re: FBR: Fix koji monitoring from noc02

2017-03-17 Thread Kevin Fenzi
+1 kevin signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Fix koji monitoring from noc02

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 01:28:31PM +, Patrick Uiterwijk wrote: > Hi all, > > So, our noc02 monitoring of Koji build targets broke because the > modularity stuff pushed rawhide to the second page :). > Can I get +1s to start testing for "infra" instead, which should match > $release-infra and s

Re: 503 Responses From 8.43.85.67

2017-03-17 Thread Stephen John Smoogen
This was being worked on and fixed with Patrick at 0800 UTC On 17 March 2017 at 03:09, Jonathan Steffan wrote: > Team, > > The community has been experiencing issues with the FPO infrastructure > intermittently. I believe I've found the destination causing the issue: > > $ curl -vso /dev/null --

FBR: Fix koji monitoring from noc02

2017-03-17 Thread Patrick Uiterwijk
Hi all, So, our noc02 monitoring of Koji build targets broke because the modularity stuff pushed rawhide to the second page :). Can I get +1s to start testing for "infra" instead, which should match $release-infra and such? Patrick commit dd4583fff2ca0739dee955197be02551373a23f5 Author: Patrick

Re: FBR: Add proxy10 and proxy14 to noc02

2017-03-17 Thread Peter Robinson
On Fri, Mar 17, 2017 at 8:54 AM, Patrick Uiterwijk wrote: > Hi all, > > Last night, we've found that proxy14 was not up "up" the last few days > (since it was rebooted for the RDU migration). > Can I get +1s to get it added to noc02? > Patch after the break. +1 > Patrick > > > commit 0e69fbf106b

SOP for Package Review

2017-03-17 Thread InvalidPath
I'm going to attempt to write this, Im looking for any info anyone currently has: hosting nodes? backend db? application names? Anything at all would be appreciated. Ben ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsub

Re: FBR: Add proxy10 and proxy14 to noc02

2017-03-17 Thread Pierre-Yves Chibon
On Fri, Mar 17, 2017 at 08:54:16AM +, Patrick Uiterwijk wrote: > Hi all, > > Last night, we've found that proxy14 was not up "up" the last few days > (since it was rebooted for the RDU migration). > Can I get +1s to get it added to noc02? > Patch after the break. +1 for me, Pierre > commit

FBR: Add proxy10 and proxy14 to noc02

2017-03-17 Thread Patrick Uiterwijk
Hi all, Last night, we've found that proxy14 was not up "up" the last few days (since it was rebooted for the RDU migration). Can I get +1s to get it added to noc02? Patch after the break. Patrick commit 0e69fbf106b7e5ce361f561de028e8e716825a32 Author: Patrick Uiterwijk Date: Fri Mar 17 08:4

Best practice for 3rd party playbook

2017-03-17 Thread Miroslav Suchý
Hi, I am in process in writing playbook for retrace.fedoraproject.org ABRT team created: https://github.com/abrt/ansible-role-retrace-server Which we can use. I just wonder what is best practise for using such 3rd party roles? Should I just copy it into our ansible.git? Or should I use ansible-g

Re: Freeze Break Request: Enabling Nested Virt for Production Taskotron Virthosts

2017-03-17 Thread Pierre-Yves Chibon
On Thu, Mar 16, 2017 at 07:52:43PM -0600, Tim Flink wrote: > This is less important than the other FBR that I submitted but I'd like > to do it while things are paused for the other change. > > I'd like to enable nested virt on the virthosts that run the Taskotron > production clients. What I'd be

Re: Freeze Break Request: enable package-specific tasks for Taskotron production

2017-03-17 Thread Pierre-Yves Chibon
On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote: > This has been pending for a long time and now that the bureaucratic > stuff has been figured out and our dev/stg instances are running well, > we'd like to enable package-specific tasks in Taskotron production. > > This will involve: >

503 Responses From 8.43.85.67

2017-03-17 Thread Jonathan Steffan
Team, The community has been experiencing issues with the FPO infrastructure intermittently. I believe I've found the destination causing the issue: $ curl -vso /dev/null --resolve fedoraproject.org:443:8.43.85.67 https://fedoraproject.org/wiki/Fedora_Project_Wiki * Added fedoraproject.org:443:8