Re: Freeze Break request: playbook run over all hosts with fedmsgdconfig tag
On Wed, Jul 29, 2015 at 09:22:56AM -0600, Kevin Fenzi wrote: Greetings. The addition of mm-frontend02 yesterday meant that all the dynamically generated fedmsg config needs to add a entry for it. This means the check/diff daily report is pretty large because all these are pending. I would like to run the master playbook with -t fedmsgdconfig and then -t fedmsgmonitor I don't think there will be any issues. +1s? This will make the following changes on fedmsg enabled hosts: --- before: /etc/fedmsg.d/endpoints.py +++ after: /srv/web/infra/ansible/roles/fedmsg/base/templates/endpoints.py.j2 @@ -41,20 +41,24 @@ ], askbot.ask02: [ tcp://ask02.%s:30%02i % (suffix, i) for i in range(6) ], # The mirrormanager2 frontend runs as 2 processes with 1 thread each. mirrormanager2.mm-frontend01: [ tcp://mm-frontend01.%s:30%02i % (suffix, i) +for i in range(2) +], +mirrormanager2.mm-frontend02: [ +tcp://mm-frontend02.%s:30%02i % (suffix, i) for i in range(2) ], # mizdebsk says he thinks we'll need four sockets. Two services # (koschei-resolver and koschei-polling) are only sending messages, one # service (koschei-watcher) can both send and receive them. The wsgi # webapp doesn't use fedmsg at all and all services are single-threaded # koschei-watcher uses two endpoints koschei.koschei01: [ tcp://koschei01.%s:30%02i % (suffix, i) +1 for me Pierre pgpD1LCGyiyHT.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze Break request: playbook run over all hosts with fedmsgdconfig tag
+1 for this On 29 July 2015 at 09:22, Kevin Fenzi ke...@scrye.com wrote: Greetings. The addition of mm-frontend02 yesterday meant that all the dynamically generated fedmsg config needs to add a entry for it. This means the check/diff daily report is pretty large because all these are pending. I would like to run the master playbook with -t fedmsgdconfig and then -t fedmsgmonitor I don't think there will be any issues. +1s? This will make the following changes on fedmsg enabled hosts: --- before: /etc/fedmsg.d/endpoints.py +++ after: /srv/web/infra/ansible/roles/fedmsg/base/templates/endpoints.py.j2 @@ -41,20 +41,24 @@ ], askbot.ask02: [ tcp://ask02.%s:30%02i % (suffix, i) for i in range(6) ], # The mirrormanager2 frontend runs as 2 processes with 1 thread each. mirrormanager2.mm-frontend01: [ tcp://mm-frontend01.%s:30%02i % (suffix, i) +for i in range(2) +], +mirrormanager2.mm-frontend02: [ +tcp://mm-frontend02.%s:30%02i % (suffix, i) for i in range(2) ], # mizdebsk says he thinks we'll need four sockets. Two services # (koschei-resolver and koschei-polling) are only sending messages, one # service (koschei-watcher) can both send and receive them. The wsgi # webapp doesn't use fedmsg at all and all services are single-threaded # koschei-watcher uses two endpoints koschei.koschei01: [ tcp://koschei01.%s:30%02i % (suffix, i) ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break request: minor change to host ordering priorities
When building ppc builders which reside on qa.fedoraproject.org we get
the wrong /etc/hosts file because the generic ansible_domain executes
before the more specific due to task host_group option.
In general I believe if we have something explicitly in a host_group
we'd want to prioritise that over a generic sub domain.
Peter
diff --git a/roles/hosts/tasks/main.yml b/roles/hosts/tasks/main.yml
index faeccb9..c74827e 100644
--- a/roles/hosts/tasks/main.yml
+++ b/roles/hosts/tasks/main.yml
@@ -16,9 +16,9 @@
- {{ inventory_hostname }}-hosts
- {{ ansible_fqdn }}-hosts
- {{ ansible_hostname }}-hosts
+- {{ host_group }}-hosts
- {{ ansible_domain }}-hosts
- {{ datacenter }}-hosts
-- {{ host_group }}-hosts
skip: true
tags:
- config
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, Jul 29, 2015 at 08:46:43AM -0600, Kevin Fenzi wrote: On Wed, 29 Jul 2015 07:58:57 -0600 Stephen John Smoogen smo...@gmail.com wrote: On 29 July 2015 at 07:54, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. The dependency here is two things: 1) buildrawhide and buildbranched scripts are pulled from there now each day when their cron job runs. If things are down, they would fail. However, this is just a few minutes around the time the cron jobs run, so as long as those are avoided that should be fine. 2) releng uses pagure.io now for a bunch of things. If we needed a change to build fedora 23 and pagure was down it would affect things, but that would need to be a lengthy downtime (like days/weeks). I can't imagine an upgrade causing that, especially since we have backups and could just restore from them in a matter of hours. Anyhow, I am +1 to this. We should be able to backout if it causes a big problem (change db back and downgrade rpm). I have added 2 bug fixes: - Fix the anchors for the comments of a pull-request - Fix internal server error when someone not logged in sees PR I will cut the release and push it to stg where we can test and ensure it's all running fine. Pierre pgpapY_WeFPNR.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
[release] pagure: 0.1.20
Hi everyone, As announce and discussed I just cut a new release of pagure: 0.1.20 Here is its changelog: * Wed Jul 29 2015 Pierre-Yves Chibon pin...@pingoured.fr - 0.1.20 - Update to 0.1.20 - Include the tags in the JSON representation of a project - Add the ability to open a pull-request from a git repo not hosted on pagure - Fix pagination when browsing the list of commits - Fix the fork button when viewing the Settings of a project - Adjust the example apache configuration file - Add a favicon with pagure's logo - Fix asynchronous commentting on pull-requests - Start working on some documentation on how to install pagure - Do no flash messages when a comment is submitted via javascript (ie: async) - Do not blink the tittle of the page if the page is already on focus - Retrieve ssh key from FAS and set it up in pagure if none is currently set-up - Fix anchors for comments on the pull-request pages - Fix checking the merge status of a PR when user is not logged in This is currently running fine in stg, I will play a little more with it and if everything goes fine, push to prod tomorrow. Please test stg as well and let me know if anything breaks :) Thanks, Pierre pgpXklN2cEu44.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: minor change to host ordering priorities
On Wed, Jul 29, 2015 at 5:29 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote:
On Wed, Jul 29, 2015 at 05:24:46PM +0100, Peter Robinson wrote:
When building ppc builders which reside on qa.fedoraproject.org we get
the wrong /etc/hosts file because the generic ansible_domain executes
before the more specific due to task host_group option.
In general I believe if we have something explicitly in a host_group
we'd want to prioritise that over a generic sub domain.
Peter
diff --git a/roles/hosts/tasks/main.yml b/roles/hosts/tasks/main.yml
index faeccb9..c74827e 100644
--- a/roles/hosts/tasks/main.yml
+++ b/roles/hosts/tasks/main.yml
@@ -16,9 +16,9 @@
- {{ inventory_hostname }}-hosts
- {{ ansible_fqdn }}-hosts
- {{ ansible_hostname }}-hosts
+- {{ host_group }}-hosts
- {{ ansible_domain }}-hosts
- {{ datacenter }}-hosts
-- {{ host_group }}-hosts
skip: true
tags:
- config
Sounds ok to me, do we have a way to check which hosts are impacted by this
change?
Kevin says he has a report that check/diff report what machines would
change based on it
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
OK with that information I am +1 also. On 29 July 2015 at 08:46, Kevin Fenzi ke...@scrye.com wrote: On Wed, 29 Jul 2015 07:58:57 -0600 Stephen John Smoogen smo...@gmail.com wrote: On 29 July 2015 at 07:54, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. The dependency here is two things: 1) buildrawhide and buildbranched scripts are pulled from there now each day when their cron job runs. If things are down, they would fail. However, this is just a few minutes around the time the cron jobs run, so as long as those are avoided that should be fine. 2) releng uses pagure.io now for a bunch of things. If we needed a change to build fedora 23 and pagure was down it would affect things, but that would need to be a lengthy downtime (like days/weeks). I can't imagine an upgrade causing that, especially since we have backups and could just restore from them in a matter of hours. Anyhow, I am +1 to this. We should be able to backout if it causes a big problem (change db back and downgrade rpm). kevin ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, Jul 29, 2015 at 08:46:43AM -0600, Kevin Fenzi wrote: On Wed, 29 Jul 2015 07:58:57 -0600 Stephen John Smoogen smo...@gmail.com wrote: On 29 July 2015 at 07:54, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. The dependency here is two things: 1) buildrawhide and buildbranched scripts are pulled from there now each day when their cron job runs. If things are down, they would fail. However, this is just a few minutes around the time the cron jobs run, so as long as those are avoided that should be fine. Do you know when these cron jobs are running? Just to be sure I don't run into Murphy :) Thanks, Pierre pgp5f1zjbPn49.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: minor change to host ordering priorities
On Wed, Jul 29, 2015 at 05:24:46PM +0100, Peter Robinson wrote:
When building ppc builders which reside on qa.fedoraproject.org we get
the wrong /etc/hosts file because the generic ansible_domain executes
before the more specific due to task host_group option.
In general I believe if we have something explicitly in a host_group
we'd want to prioritise that over a generic sub domain.
Peter
diff --git a/roles/hosts/tasks/main.yml b/roles/hosts/tasks/main.yml
index faeccb9..c74827e 100644
--- a/roles/hosts/tasks/main.yml
+++ b/roles/hosts/tasks/main.yml
@@ -16,9 +16,9 @@
- {{ inventory_hostname }}-hosts
- {{ ansible_fqdn }}-hosts
- {{ ansible_hostname }}-hosts
+- {{ host_group }}-hosts
- {{ ansible_domain }}-hosts
- {{ datacenter }}-hosts
-- {{ host_group }}-hosts
skip: true
tags:
- config
Sounds ok to me, do we have a way to check which hosts are impacted by this
change?
Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze Break request: playbook run over all hosts with fedmsgdconfig tag
Greetings. The addition of mm-frontend02 yesterday meant that all the dynamically generated fedmsg config needs to add a entry for it. This means the check/diff daily report is pretty large because all these are pending. I would like to run the master playbook with -t fedmsgdconfig and then -t fedmsgmonitor I don't think there will be any issues. +1s? This will make the following changes on fedmsg enabled hosts: --- before: /etc/fedmsg.d/endpoints.py +++ after: /srv/web/infra/ansible/roles/fedmsg/base/templates/endpoints.py.j2 @@ -41,20 +41,24 @@ ], askbot.ask02: [ tcp://ask02.%s:30%02i % (suffix, i) for i in range(6) ], # The mirrormanager2 frontend runs as 2 processes with 1 thread each. mirrormanager2.mm-frontend01: [ tcp://mm-frontend01.%s:30%02i % (suffix, i) +for i in range(2) +], +mirrormanager2.mm-frontend02: [ +tcp://mm-frontend02.%s:30%02i % (suffix, i) for i in range(2) ], # mizdebsk says he thinks we'll need four sockets. Two services # (koschei-resolver and koschei-polling) are only sending messages, one # service (koschei-watcher) can both send and receive them. The wsgi # webapp doesn't use fedmsg at all and all services are single-threaded # koschei-watcher uses two endpoints koschei.koschei01: [ tcp://koschei01.%s:30%02i % (suffix, i) pgpUHhaHTHP79.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, 29 Jul 2015 18:06:22 +0200 Pierre-Yves Chibon pin...@pingoured.fr wrote: Do you know when these cron jobs are running? Just to be sure I don't run into Murphy :) 05:15 UTC for rawhide 07:15 UTC for branched. kevin pgp3MSIRghZds.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: minor change to host ordering priorities
Sounds ok to me, do we have a way to check which hosts are impacted by this change? Kevin says he has a report that check/diff report what machines would change based on it Yeah, if we push this change now, I can tell you tomorrow any hosts that would have changed. ;) Pushed I'm +1 to the change and we can clean up anything that shouldn't change. Ideally only the aarch64 builders are affected. s/aarch64/ppc64*/ aarch64 uses .arm.fedora where as for some reason PPC uses .qa.fedora... Peter ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: decrease number of crawlers to 29
On Wed, 29 Jul 2015 21:24:02 +0200 Adrian Reber adr...@lisas.de wrote: Can I get two +1's for: +1. Also, if we want, I could also give them another 32GB memory... kevin pgpt8viDLW0QQ.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: decrease number of crawlers to 29
On Wed, Jul 29, 2015 at 09:24:02PM +0200, Adrian Reber wrote: Can I get two +1's for: commit 863cbad2434f5bf612a59cce7cfcb9b242177ad7 Author: Adrian Reber adr...@lisas.de Date: Wed Jul 29 19:20:19 2015 + Reduce the number of parallel crawled hosts to 29. There has been a report that the MM database was not updated correctly and dmesg on mm-crawler01 shows three OOM killed crawlers. https://fedorahosted.org/fedora-infrastructure/ticket/4845 diff --git a/roles/mirrormanager/crawler/files/crawler.cron b/roles/mirrormanager/crawler/files/crawler.cron index 43f85f7..f77d61d 100644 --- a/roles/mirrormanager/crawler/files/crawler.cron +++ b/roles/mirrormanager/crawler/files/crawler.cron @@ -1,8 +1,8 @@ # run the crawler twice a day # logs sent to /var/log/mirrormanager/crawler.log and crawl/* by default -# 30 threads with 32GB of RAM seems to work so far +# 29 threads with 32GB of RAM seems to work so far # # [ `hostname -s` == mm-crawler02 ] sleep 2h is used to start the crawl # later on the second crawler to reduce the number of parallel accesses to # the database -0 */12 * * * mirrormanager [ `hostname -s` == mm-crawler02 ] sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 30 `/usr/local/bin/run_crawler.sh 2` /dev/null 21 +0 */12 * * * mirrormanager [ `hostname -s` == mm-crawler02 ] sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 29 `/usr/local/bin/run_crawler.sh 2` /dev/null 21 +1 here as well Pierre pgp2nrGuHSvqh.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: minor change to host ordering priorities
On Wed, 29 Jul 2015 17:58:52 +0100 Peter Robinson pbrobin...@gmail.com wrote: Sounds ok to me, do we have a way to check which hosts are impacted by this change? Kevin says he has a report that check/diff report what machines would change based on it Yeah, if we push this change now, I can tell you tomorrow any hosts that would have changed. ;) I'm +1 to the change and we can clean up anything that shouldn't change. Ideally only the aarch64 builders are affected. kevin pgpCNkts5QrfE.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: decrease number of crawlers to 29
On Wed, Jul 29, 2015 at 01:48:57PM -0600, Kevin Fenzi wrote: On Wed, 29 Jul 2015 21:24:02 +0200 Adrian Reber adr...@lisas.de wrote: Can I get two +1's for: +1. Thanks Kevin and Pierre. Pushed. Also, if we want, I could also give them another 32GB memory... Either that or we can setup a crawler in Europe to crawl European mirrors from there. The crawler has the necessary functionality and we could try continent based crawls. I was aiming for after alpha freeze. Adrian pgp4XbSgiZtsw.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Plan for tomorrow's Fedora Infrastructure meeting - 2015-07-30
The infrastructure team will be having it's weekly meeting tomorrow, 2015-07-30 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-07-30) #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 old cloud to new cloud migration moving along, hopefully done by friday - kevin/patrick #info ibiblio05 installed and ready for service - kevin #info virthost19/20/21/22 installed and ready for service - smooge #info smooge onsite at phx2 #info bapp02/app01.stg now gone. Down to just 9 hosts in puppet - kevin #info We are now in Fedora 23 Alpha freeze! - 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 There are many tickets left alone for months with comments that let thin there are done/inactual. Examples: https://fedorahosted.org/fedora-infrastructure/ticket/1684 https://fedorahosted.org/fedora-infrastructure/ticket/1180 https://fedorahosted.org/fedora-infrastructure/ticket/3627 Maybe we should review all open tickets one by one and decide whether we should do something or just close the ticket? #topic Idea: We could create official Fedoraproject Docker repo - p_klos I found some Fedora cloud repo on Docker Hub but we don't have any official FedoraProject repo with Docker images. Maybe we could create one and put there Docker-ready images? I.E. Latest, alpha, server minimal, server freeipa, other options available to click in anaconda during installation? = 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 pgpMb2g6C65dN.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [release] MirrorManager2: 0.4.1
On Tue, Jul 28, 2015 at 03:42:44PM +0200, Pierre-Yves Chibon wrote: Good morning everyone, I just released a new version of MirrorManager2: 0.4.1 Here is its changelog: * Tue Jul 28 2015 Pierre-Yves Chibon pin...@pingoured.fr - 0.4.1-1 - Update to 0.4.1 - If the host has no categories do not auto-disable it (Adrian Reber) - Different small umdl and crawler fixe (Adrian Reber) As you can see it is a bug-fix release with few fixes by Adrian. It is currently running in staging and will be pushed to prod once testing is done. Testing in stg were all successful but since this we went into freeze, could I have a couple of +1 to push this update to prod? Thanks, Pierre pgp0MnaOsWiaA.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [release] MirrorManager2: 0.4.1
On Wed, Jul 29, 2015 at 9:18 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, Jul 28, 2015 at 03:42:44PM +0200, Pierre-Yves Chibon wrote: Good morning everyone, I just released a new version of MirrorManager2: 0.4.1 Here is its changelog: * Tue Jul 28 2015 Pierre-Yves Chibon pin...@pingoured.fr - 0.4.1-1 - Update to 0.4.1 - If the host has no categories do not auto-disable it (Adrian Reber) - Different small umdl and crawler fixe (Adrian Reber) As you can see it is a bug-fix release with few fixes by Adrian. It is currently running in staging and will be pushed to prod once testing is done. Testing in stg were all successful but since this we went into freeze, could I have a couple of +1 to push this update to prod? +1 seems reasonable to me ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
RE: [release] MirrorManager2: 0.4.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 +1 from me - -- With kind regards, Patrick Uiterwijk Fedora Infra -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJVuLGeAAoJEIZXmA2atR5QMrQP/0GxKVkjpOYrjZVSBKU3OnAe fNJvYgSWfcEFM4wBo6bz2JSaqQNYIP0LWpwqMDSXJ1fGJxRA8fhoNYoytwF5CHGI R/inhM+d0rTO9bue5KsrKp9sSAkJgZ1aKUDCPg8S/gqQLqym/J59hXgvGwLuXyxN 8qIYN73rAxk/3PHKQncOqb3tbSoehz67zX7lqBkZ+e8TH5VXgwd7OtFWJsV5pAnR TZEkmGljaBteEl2CGYsMRPMPQ1j2CO86tB2MtfnWf4gEazMuuzxBiWbC7wQGgpgD fPRAtzK2UsZFHsq0eQOow0XlmGfEcyy+YyOuiVoTcUGhcMAmGWog1aWVqMeil9Vn gIzZ20JUWLNqhVoq/XQ3BRzWKSmzl/e9I55XxWnSvOWKHk39xuBLOYaO0RaTXvmh 0iG2sfUKitXROHCOofeAxxaXf65h3FM97zLCXOVqdFRwVp4cguoXrM1hjXzCWHfY 1k3qQI7isoiEMLHVxOzFUrB7vJyS5/fQxVhaZUyZpLyoDjw2PiQKtTNPmCutQEhi PfCMWp5fYIttqzta4vymI7iO4M3rKvs598KS/NqlLKtCVG9+/70j7vJVR54F759u 4KPHVVcImPRjsB/2AiowP5VJOYwx2lGtEFRLsvYKo7nK5+XVw2pOuaFsR4PYA71G R002kFdY2k8sr99L8Kzj =nX5H -END PGP SIGNATURE- ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: Setup G11N fedmsg irc bot
On Wed, Jul 29, 2015 at 12:14:20PM +0200, Patrick Uiterwijk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Could I get +1s for the following change that adds fedmsg ircbot for the G11N
team?
commit a8ddd164691692775e89f6e10802aec65e6d0075
Author: Patrick Uiterwijk puiterw...@redhat.com
Date: Wed Jul 29 10:13:27 2015 +
Setup G11N with fedmsg irc
diff --git a/roles/fedmsg/irc/templates/ircbot.py
b/roles/fedmsg/irc/templates/ircbot.py
index 8b76651..f26ec01 100644
- --- a/roles/fedmsg/irc/templates/ircbot.py
+++ b/roles/fedmsg/irc/templates/ircbot.py
@@ -174,6 +174,25 @@ config = dict(
),
),
+# And for #fedora-g11n
+dict(
+network='chat.freenode.net',
+port=6667,
+make_pretty=True,
+make_terse=True,
+
+{% if env == 'staging' %}
+nickname='fedmsg-g11n-stg',
+{% else %}
+nickname='fedmsg-g11n',
+{% endif %}
+channel='#fedora-g11n',
+# If the word G11N appears in any message, forward it.
+filters=dict(
+body=['^((?!G11N).)*$'],
+),
+),
+
# Hook up the design-team with badges messages
dict(
network='chat.freenode.net',
Looks good to me, +1
Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break request: Setup G11N fedmsg irc bot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Could I get +1s for the following change that adds fedmsg ircbot for the G11N
team?
commit a8ddd164691692775e89f6e10802aec65e6d0075
Author: Patrick Uiterwijk puiterw...@redhat.com
Date: Wed Jul 29 10:13:27 2015 +
Setup G11N with fedmsg irc
diff --git a/roles/fedmsg/irc/templates/ircbot.py
b/roles/fedmsg/irc/templates/ircbot.py
index 8b76651..f26ec01 100644
- --- a/roles/fedmsg/irc/templates/ircbot.py
+++ b/roles/fedmsg/irc/templates/ircbot.py
@@ -174,6 +174,25 @@ config = dict(
),
),
+# And for #fedora-g11n
+dict(
+network='chat.freenode.net',
+port=6667,
+make_pretty=True,
+make_terse=True,
+
+{% if env == 'staging' %}
+nickname='fedmsg-g11n-stg',
+{% else %}
+nickname='fedmsg-g11n',
+{% endif %}
+channel='#fedora-g11n',
+# If the word G11N appears in any message, forward it.
+filters=dict(
+body=['^((?!G11N).)*$'],
+),
+),
+
# Hook up the design-team with badges messages
dict(
network='chat.freenode.net',
- --
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJVuKd8AAoJEIZXmA2atR5QmcQP/1MOTzKUegP5FQDfX25cce3j
aPwBS4UMZqkt4QJqjeSsqf1qzZuDq62nI+SQo33PmZ8D6dOCy7F8vN2uWNm73ygB
8zSLqdz79R1lLZ2ElTDG70CL+z3qV4L4Tkt+MYJzIizrZ4GQCe22v5NfxpiCdZ2j
WvWKKvUV3noZu8TpBmNM/L6aGLcEBFfKfHVYJtCnOTbX76ILt5R+tHMzbrj6oX7R
REXsK6HkGRxbmdsgj/vQ9TAbYaNKTYs5nl3L8YWzc8Pa8INRz0S9FUbHqGGbg31/
NgWNjT6E1kx4S26f9MnsFhswYnU+so1okfoipqjkto5GBXJpF9LaZpa+OHIT0Ln3
YUEPMawt8PDeGeMDnsXSSh+nNGlh8p/RJBQy5SiksdUPiK24yONWzo2DXY7hJfOI
cpIspj6Zo5yG9jsnrHGz+aX5qABfSUboKUnUq8rNCmGUKLlC6uSuIFIKsIgomiw6
fAWeR6bjU+La99ki04xZkySDv1xcyycen7DMrLqeH6c4lSWKUX902XikN5lTiXY8
zwQTqD1o5LpPSfYTEltkKB20GcP/AgZC1etz3yH668B7XTe7SzzQRWpmsVJ82M9d
m928akl2gv8KnYysUZWSVnbvgqlh8bRxgCeR41GxuDQQtLRL+01PwY3RUQWqN9/K
uqGU2Sg/h+Pk7WVYMQDM
=fWbe
-END PGP SIGNATURE-
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break request? Pagure update
Hi everyone, I was planning on making a new release of pagure today, not realizing that we were entering freeze. I would like to hear more opinions about pushing this release, here is the current changelog: - Include the tags in the JSON representation of a project - Add the ability to open a pull-request from a git repo not hosted on pagure - Fix pagination when browsing the list of commits - Fix the fork button when viewing the Settings of a project - Adjust the example apache configuration file - Add a favicon with pagure's logo - Fix asynchronous commentting on pull-requests - Start working on some documentation on how to install pagure - Do no flash messages when a comment is submitted via javascript (ie: async) - Do not blink the tittle of the page if the page is already on focus - Retrieve ssh key from FAS and set it up in pagure if none is currently set-up The remote PR needs a small DB change, everything else is pretty much bug fixes or minor improvements. Thoughts? Thanks, Pierre pgpmI5j9L9yFW.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: [post] Add a pagure.org - pagure.io redirect
On Wed, Jul 29, 2015 at 11:00 AM, Patrick Uiterwijk
puiterw...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Could I get retroactive +1s for the following commit, which fixes
pagure.org urls (instaad of getting them trapped in the docs.pagure.org
vhost).
Seems to work with testing so +1
1 files changed, 22 insertions(+), 0 deletions(-)
[puiterwijk@lockbox01 templates]$ git show HEAD
commit 0a7efdc4fb9fa7b14d2447294cae56100624f9b7
Author: Patrick Uiterwijk puiterw...@redhat.com
Date: Wed Jul 29 09:57:44 2015 +
Make a pagure.org - pagure.io redirect
diff --git a/roles/pagure/frontend/templates/0_pagure.conf
b/roles/pagure/frontend/templates/0_pagure.conf
index ea81a92..05bb090 100644
- --- a/roles/pagure/frontend/templates/0_pagure.conf
+++ b/roles/pagure/frontend/templates/0_pagure.conf
@@ -27,6 +27,28 @@ WSGIDaemonProcess paguredocs user=git group=git
maximum-requests=1000 display-na
{% endif %}
/VirtualHost
+VirtualHost *:443
+{% if env == 'pagure-staging' %}
+ ServerName stg.pagure.org
+{% else %}
+ ServerName pagure.org
+{% endif %}
+
+ SSLEngine on
+ SSLProtocol all -SSLv2 -SSLv3
+ # Use secure TLSv1.1 and TLSv1.2 ciphers
+ Header always add Strict-Transport-Security max-age=15768000;
includeSubDomains; preload
+
+ SSLCertificateFile /etc/pki/tls/certs/docs.pagure.org.crt
+ SSLCertificateChainFile /etc/pki/tls/certs/docs.pagure.org.intermediate.crt
+ SSLCertificateKeyFile /etc/pki/tls/certs/docs.pagure.org.key
+{% if env == 'pagure-staging' %}
+ Redirect permanent / https://stg.pagure.io/
+{% else %}
+ Redirect permanent / https://pagure.io/
+{% endif %}
+/VirtualHost
+
VirtualHost *:443
{% if env == 'pagure-staging' %}
- --
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJVuKQ5AAoJEIZXmA2atR5Q/voP/jm5JZtzX1StwAN07b8CxfRK
2dWxTL7nWagRqt+LcmootLNHb4GmH58wyS2XpEa+BlnDt33BeEK8AuoO4QdbISgI
tWygWNQwyPaME4gPRdxCNhnJ8Xo+9S/ss5j98dMqQz31MnwclxXdMsz0NYlyE4NX
DKgxfiJayelP6EjR1lfjnBTag7S+Hoj3QXBYU74ACky8Um0SKOLc/nRjX2ccHYFL
q3qwz4VedunKFvCmlhybGXVs5CANA6Z+W846jXQSiBXx7WaoduvIIYzKVX9Zmdll
ZMvjNk6ZmkKDuqKGG51FMyjMe4J0RMu9TW7pWWDYMz6+yOLcrJfUDp17w1JVbZ0g
jnuA7XnsEGsvcWoLU4dtClE0SIkyRnrL+A44Ahpa+5Xo1M0eZxUZ+6kBq0LSl5Jo
LhOpDhxQ25nVMqjMLjdmfn8+3usUl+8TkxSGnbeKljR6nnOtpA3wRCZ75UXmXf6/
sr6eTCm7RF6+kbkovU7F8jS9aqMDP+Pvzz/GyB4eFuODhUGjPHVsvbh9XKY3YZfH
hW3wH85tabaoQJrH3OS0QPpnHln67Ey57tH9ZUroeNVKTx1ulw/o6/Dwdc34iY/D
YqWi6ak7QSkTWnuvpEumoM+Uk0BsgQSSa1gE2lObMCfTzC2jyO5lmghlO/ET3RCY
rkiGx/E3qRJ3qfp0dnDE
=Lbie
-END PGP SIGNATURE-
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: Setup G11N fedmsg irc bot
Looks good to me.
On 29 July 2015 at 04:52, Pierre-Yves Chibon pin...@pingoured.fr wrote:
On Wed, Jul 29, 2015 at 12:14:20PM +0200, Patrick Uiterwijk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Could I get +1s for the following change that adds fedmsg ircbot for the
G11N team?
commit a8ddd164691692775e89f6e10802aec65e6d0075
Author: Patrick Uiterwijk puiterw...@redhat.com
Date: Wed Jul 29 10:13:27 2015 +
Setup G11N with fedmsg irc
diff --git a/roles/fedmsg/irc/templates/ircbot.py
b/roles/fedmsg/irc/templates/ircbot.py
index 8b76651..f26ec01 100644
- --- a/roles/fedmsg/irc/templates/ircbot.py
+++ b/roles/fedmsg/irc/templates/ircbot.py
@@ -174,6 +174,25 @@ config = dict(
),
),
+# And for #fedora-g11n
+dict(
+network='chat.freenode.net',
+port=6667,
+make_pretty=True,
+make_terse=True,
+
+{% if env == 'staging' %}
+nickname='fedmsg-g11n-stg',
+{% else %}
+nickname='fedmsg-g11n',
+{% endif %}
+channel='#fedora-g11n',
+# If the word G11N appears in any message, forward it.
+filters=dict(
+body=['^((?!G11N).)*$'],
+),
+),
+
# Hook up the design-team with badges messages
dict(
network='chat.freenode.net',
Looks good to me, +1
Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
--
Stephen J Smoogen.
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. If there are no impacts on production then it isn't covered by a freeze. If there are few impacts on production then a freeze break request can be granted. If there are many impacts on production then FBR probably won't be granted unless not doing so makes things worse. On 29 July 2015 at 05:06, Pierre-Yves Chibon pin...@pingoured.fr wrote: Hi everyone, I was planning on making a new release of pagure today, not realizing that we were entering freeze. I would like to hear more opinions about pushing this release, here is the current changelog: - Include the tags in the JSON representation of a project - Add the ability to open a pull-request from a git repo not hosted on pagure - Fix pagination when browsing the list of commits - Fix the fork button when viewing the Settings of a project - Adjust the example apache configuration file - Add a favicon with pagure's logo - Fix asynchronous commentting on pull-requests - Start working on some documentation on how to install pagure - Do no flash messages when a comment is submitted via javascript (ie: async) - Do not blink the tittle of the page if the page is already on focus - Retrieve ssh key from FAS and set it up in pagure if none is currently set-up The remote PR needs a small DB change, everything else is pretty much bug fixes or minor improvements. Thoughts? Thanks, Pierre ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, Jul 29, 2015 at 04:07:46PM +0200, Mathieu Bridon wrote: On Wed, 2015-07-29 at 15:54 +0200, Pierre-Yves Chibon wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). Unrelated to this freeze request, but I'm curious: what happens if you restart apache right in the middle of someone pushing over http? My first reaction was like: no clue, but in fact I have a 2 parts answer: a/ we do not support push over http, only clone, pull and fetch b/ apache on RHEL7 has this tendency to wait for all the connection to close before actually doing the restart. This is really quite annoying sometime but might save us this time. Pierre ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request: re-add qadevel.qa.fedoraproject.org to backups
Pushed, thanks. kevin pgpB3xoJqdf1e.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. Not knowing how rel-eng relies on pagure I can't estimate the impact. I can however estimate the down-time to be very short (in the order of the 10s of minutes), it's updating the package, calling alembic to upgrade the database and restart apache. Pierre If there are no impacts on production then it isn't covered by a freeze. If there are few impacts on production then a freeze break request can be granted. If there are many impacts on production then FBR probably won't be granted unless not doing so makes things worse. On 29 July 2015 at 05:06, Pierre-Yves Chibon pin...@pingoured.fr wrote: Hi everyone, I was planning on making a new release of pagure today, not realizing that we were entering freeze. I would like to hear more opinions about pushing this release, here is the current changelog: - Include the tags in the JSON representation of a project - Add the ability to open a pull-request from a git repo not hosted on pagure - Fix pagination when browsing the list of commits - Fix the fork button when viewing the Settings of a project - Adjust the example apache configuration file - Add a favicon with pagure's logo - Fix asynchronous commentting on pull-requests - Start working on some documentation on how to install pagure - Do no flash messages when a comment is submitted via javascript (ie: async) - Do not blink the tittle of the page if the page is already on focus - Retrieve ssh key from FAS and set it up in pagure if none is currently set-up The remote PR needs a small DB change, everything else is pretty much bug fixes or minor improvements. Thoughts? Thanks, Pierre ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On 29 July 2015 at 07:54, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. Not knowing how rel-eng relies on pagure I can't estimate the impact. I can however estimate the down-time to be very short (in the order of the 10s of minutes), it's updating the package, calling alembic to upgrade the database and restart apache. I would ping dgilmore/pbrobinson then to get their take on it.. but it does sound like this falls into the second category since the main service used gitolite is not affected. -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, 2015-07-29 at 15:54 +0200, Pierre-Yves Chibon wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). Unrelated to this freeze request, but I'm curious: what happens if you restart apache right in the middle of someone pushing over http? -- Mathieu ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break request? Pagure update
On Wed, 29 Jul 2015 07:58:57 -0600 Stephen John Smoogen smo...@gmail.com wrote: On 29 July 2015 at 07:54, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen wrote: In doing something like this we would need to know what the impact is. What parts of production of an Alpha would be down during the upgrade? I think there things releng has in pagure but I don't know if those would make any release parts impossible if it was down for 2-3 hours. That is also something I don't know, git access will remain available (via ssh always, via http most of the time (except when I restart apache)). The update only influences the web-UI part, not gitolite in anyway. The dependency here is two things: 1) buildrawhide and buildbranched scripts are pulled from there now each day when their cron job runs. If things are down, they would fail. However, this is just a few minutes around the time the cron jobs run, so as long as those are avoided that should be fine. 2) releng uses pagure.io now for a bunch of things. If we needed a change to build fedora 23 and pagure was down it would affect things, but that would need to be a lengthy downtime (like days/weeks). I can't imagine an upgrade causing that, especially since we have backups and could just restore from them in a matter of hours. Anyhow, I am +1 to this. We should be able to backout if it causes a big problem (change db back and downgrade rpm). kevin pgpL9iHwGL6WW.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
