work_mem check for nagios client

Hello, I've noticed there is no work_mem check https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/nagios_client/templates that would test that working memory is inside allowed limits. I've recently made the work_mem check but specific just to COPR:

dist-git 1.10 release

Hello, I've released a new version of dist-git 1.10 (https://github.com/release-engineering/dist-git). The main thing in there is python2/3 compatibility. When deployed in Fedora, it uses python3 now. I've also fixed a small bug in post-receive hook when there were no hooks to run in

Re: FBR: Make clime be on the pager for COPR

Thanks! Finally, I will immediately know that Copr doesn't work. On Sat, Oct 20, 2018 at 3:52 PM Patrick マルタインアンドレアス Uiterwijk < puiterw...@redhat.com> wrote: > Hi all, > > Can I get +1s for the patchset to allow clime to ack service and host > issues in nagios, and to make the initial COPR

Re: Moving forward with Fedora's PDC

On Mon, Sep 24, 2018 at 2:43 PM Clement Verna wrote: > > > > On Mon, 24 Sep 2018 at 11:30, Michal Novotny wrote: >> >> Hello, >> >> could we use this? >> >> https://github.com/PostgREST/postgrest > > > While I don't have a strong prefe

Re: Anitya 0.13.0 (release-monitoring) deployed on staging

On Thu, Sep 13, 2018 at 9:42 AM Michal Konečný wrote: > > Hi everybody, > > I want to announce that the Anitya 0.13.0 was finally deployed on > staging (https://stg.release-monitoring.org/) > > Feel free to test it. > > You can see the changelog here: >

Re: libravatar in Fedora OpenShift

On Sat, Aug 18, 2018 at 7:09 PM Mikolaj Izdebski wrote: > Hi Michal, > > On 08/01/2018 08:07 AM, Michal Novotny wrote: > > Hello, > > > > I would like to ask if anyone is willing to sponsor running libravatar ( > > https://git.linux-kernel.at/oliver/ivatar) in

Re: fedora messaging

On Fri, Aug 17, 2018 at 9:40 AM Jeremy Cline wrote: > On 08/16/2018 06:22 PM, Michal Novotny wrote: > > On Thu, Aug 16, 2018 at 4:34 PM Jeremy Cline wrote: > >> > >> So, am I right in saying your main objection is the Python package? Or > >> do you obj

Re: fedora messaging

On Thu, Aug 16, 2018 at 4:34 PM Jeremy Cline wrote: > On 08/16/2018 11:53 AM, Michal Novotny wrote: > > On Thu, Aug 16, 2018 at 11:43 AM Jeremy Cline wrote: > > > >> The current solution is fedmsg-meta-fedora-infrastructure, a central > >> Python modul

Re: fedora messaging

On Thu, Aug 16, 2018 at 11:43 AM Jeremy Cline wrote: > On 08/15/2018 01:53 PM, Michal Novotny wrote:>> 1. Make catching > accidental schema changes as a publisher easy. > > > > So we can just solve this by registering the scheme with the publisher > > first bef

new release: dist-git 1.8

Hello, a new dist-git version has been released. Changes include: - fix python-grokmirror dep - add lookaside_dir option, deprecate cache_dir - defattr is not needed since rpm 4.2 - add disable_group_check configuration option for upload script Probably the most interesting one is

Re: fedora messaging

Forgive me if it is not. On Wed, Aug 15, 2018 at 2:53 PM Michal Novotny wrote: > > Anyway, to summarize, I really really want this to be super easy to use > and just work. I hope we can improve it further and I'd love to hear > your thoughts. Do you think my problem state

Re: fedora messaging

at 10:55 AM Jeremy Cline wrote: > On 08/13/2018 10:20 PM, Michal Novotny wrote: > > So I got to know on the flock that fedmsg is going to be replaced? > > > > Anyway, it seems that there is an idea to create schemas for the messages > > and distribute them in packages?

Re: Introduction

On Mon, Aug 13, 2018 at 4:52 PM Michal Konečný wrote: > Hi everyone, > > I'm new in Fedora Infrastructure and will take care of Anitya and > the-new-hotness apps. > Cool and welcome! Could you, please, take a look at updating release-monitoring.org with a newer version of Anitya. That service

fedora messaging

So I got to know on the flock that fedmsg is going to be replaced? Anyway, it seems that there is an idea to create schemas for the messages and distribute them in packages? And those python packages need to be present on producer as well as consumer? > JSON schemas > Message bodies are JSON

libravatar in Fedora OpenShift

Hello, I would like to ask if anyone is willing to sponsor running libravatar ( https://git.linux-kernel.at/oliver/ivatar) in Fedora OpenShift per https://docs.pagure.org/infra-docs/sysadmin-guide/sops/requestforresources.html. I think we could use the automatic deployment options that OpenShift

Re: is copr-be.cloud.fedoraproject.org DOWN?

I've cleaned up stale builder records and restarted copr-backend-service because one of the subservices (copr-backend-log) was down due to failed connection to local redis server. clime On Sun, Jun 24, 2018 at 11:29 PM Satish Patel wrote: > Thank you for your service! > > Sent from my iPhone >

Re: Fedora and PDC

On Fri, Jun 8, 2018 at 8:58 AM, Lubomír Sedlář wrote: > Pierre-Yves Chibon píše v Čt 07. 06. 2018 v 18:20 +0200: > > Good Morning Everyone, > > > > So there has been a number of person who expressed in this topic. > > The list I have so far is: > > - Clime > > - bowlofeggs > > - cverna > > -

Re: Slow Pagure.io

On Fri, May 4, 2018 at 4:36 PM, Vít Ondruch wrote: > If I go to pagure.io/login, I can get logged in, but then I can't access > the issues again ... > > I had those same exact issues yesterday immediatelly after new pagure release. When logged out I could access

Re: Fedora and PDC

> * I kinda don't like the tree of files in git. It would work, but it seems poor, like we don't know how to use a database. Along with just strange to work with. We could use Git repo of yaml files as the basis but import data upon each commit for each branch into a locally mounted sqlite DB.

Re: Fedora and PDC

* Stream branches, branch ownership, retirement dates? - SLA/EOL are currently stored in PDC. - Queried by releng scripts for retirement, fedrepo-req for new branches, etc.. option #1 git repo full of yaml file similar to the override repo compiled into a single JSON

Re: Moving meeting time?

On Thu, Apr 19, 2018 at 2:29 PM, Michal Novotny <cl...@redhat.com> wrote: > On Wed, Apr 18, 2018 at 11:31 PM, Kevin Fenzi <ke...@scrye.com> wrote: > >> Greetings. >> >> It was noted recently that our current meeting time (thursdays at 18UTC) >> is

Re: Moving meeting time?

On Wed, Apr 18, 2018 at 11:31 PM, Kevin Fenzi wrote: > Greetings. > > It was noted recently that our current meeting time (thursdays at 18UTC) > is a bit late/poorly timed for several of our European colleagues. > > Additionally, we sometimes have the go/no-go meeting at the

Re: Freeze Break Request: re-enable fedmsg hook on src

On Thu, Apr 19, 2018 at 2:07 AM, Kevin Fenzi wrote: > Odd. Somehow my patch was not my patch. ;( > > Here is the real one... > > > diff --git a/roles/git/hooks/files/post-receive-chained > b/roles/git/hooks/files/post-receive-chained > > index 5c74da4..99b5a2a 100755 > > ---

Re: Freeze Break Request: re-enable fedmsg hook on src

+1 On Wed, Apr 18, 2018 at 7:21 PM, Kevin Fenzi wrote: > Greetings. > > Just before freeze in ansible commit > dc86b22f9054bdcefd51e46db90433c03d54410c pingou disabled the fedmsg hook > because there was a permissions problem reading the fedmsg key. > > In ansible commit

Re: Zchunk update

On Tue, Apr 17, 2018 at 4:20 PM, Jonathan Dieter <jdie...@gmail.com> wrote: > On Tue, 2018-04-17 at 09:08 +0200, Michal Novotny wrote: > > Hello Jonathan, > > > > On Mon, Apr 16, 2018 at 2:47 PM, Jonathan Dieter <jdie...@gmail.com> > > wrote: > > >

Re: Zchunk update

Hello Jonathan, On Mon, Apr 16, 2018 at 2:47 PM, Jonathan Dieter wrote: > It's been a number of weeks since my last update, so I thought I'd let > everyone know where things are at. > > I've spent most of these last few weeks reworking zchunk's API to make > it easier to use

Re: Libravatar shutting down on 2018-09-01

On Tue, Apr 10, 2018 at 10:47 AM, Till Maas wrote: > Hi > > On Tue, Apr 10, 2018 at 10:27:59AM +0200, Miroslav Suchý wrote: >> Dne 5.4.2018 v 04:16 Neal Gompa napsal(a): >> > The main problem, of course, is finding someone who wants to run it... >> >> Even if you find

Re: Fedora Infrastructure Authentication Roadmap

Currently, in COPR we talk to id.fedoraproject.org to authenticate users. Will there be some change in the name or API for this service? Will it be possible to do user registration and group creation remotely through CAIAPI? Thank you clime On Mon, Apr 2, 2018 at 7:38 PM, Kevin Fenzi

Re: FBR: Update pungi and install python3-modulemd and pdc-client on bodhi-backend

+1 On Wed, Mar 7, 2018 at 1:31 AM, Kevin Fenzi wrote: > +1 here. > > kevin > > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-leave@lists. >

Planned Outage: COPR BACKEND upgrade - 2018-01-16 09:00 UTC

Planned Outage: COPR BACKEND upgrade - 2018-01-16 09:00 UTC There will be an outage starting at 2018-01-16 09:00 UTC, which will last approximately 0.5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-01-16

Re: Need your collaboration to release fedpkg

Hello, On Fri, Oct 27, 2017 at 5:27 AM, Chenxiong Qi wrote: > Hi all, > > New release of fedpkg includes two requested changes, one is to send > namespace along with repo name to lookaside while new-sources[1] and > another one is to clone from https:// anonymous URL instead of

Re: Restructuring hooks in dist-git

Looking further, this is probably unrelated now as the setup script from the upstream dist-git is no longer used. Sorry for the fuss. On Fri, Sep 15, 2017 at 8:13 AM, Michal Novotny <cl...@redhat.com> wrote: > Hello, > > On Thu, Sep 14, 2017 at 11:24 AM, Pierre-Yves Chibon <p

Re: Restructuring hooks in dist-git

Hello, On Thu, Sep 14, 2017 at 11:24 AM, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > After some more testing and debugging in stg, these are the changes I > ended up > doing/running in stg. > > [PATCH 1/3] Add pagure's hook to the post-receive hook and point to

Re: Congrats to Adam Miller

Congratulations, Adam! On Sat, Sep 2, 2017 at 6:27 AM, InvalidPath wrote: > I might not know you, but grats Adam! > > On Fri, Sep 1, 2017 at 9:26 PM, Adam Miller > wrote: > >> On Fri, Sep 1, 2017 at 10:28 AM, Kevin Fenzi

Re: Fedora Infrastructure support for COPR

On Mon, Jul 31, 2017 at 7:03 PM, Michal Novotny <cl...@redhat.com> wrote: > > > On Mon, Jul 31, 2017 at 4:46 PM, Matthew Miller <mat...@fedoraproject.org> > wrote: > >> On Mon, Jul 31, 2017 at 10:16:16AM +0200, Michal Novotny wrote: >> > COPR now operates

Re: Fedora Infrastructure support for COPR

On Mon, Jul 31, 2017 at 4:46 PM, Matthew Miller <mat...@fedoraproject.org> wrote: > On Mon, Jul 31, 2017 at 10:16:16AM +0200, Michal Novotny wrote: > > COPR now operates with packages solely from official Fedora repositories. > > \o/ > > Nice! > > > I partic

Fedora Infrastructure support for COPR

Hello, COPR now operates with packages solely from official Fedora repositories. This was requested in https://pagure.io/fedora-infrastructure/issue/5166 as a condition to get the Fedora Infra support. I would like to ask for the support now as this condition is finally satisfied \o/. Perhaps

Re: FBR: Apply patch to FMN to resume

+1 On Wed, May 31, 2017 at 8:51 PM, Patrick Uiterwijk wrote: > Hi all, > > Can I get +1s to apply the patch for > https://patch-diff.githubusercontent.com/raw/fedora-infra/fedmsg_meta_ > fedora_infrastructure/pull/430.patch > on prod, so that FMN can continue running? > >

Re: FBR: patched libgit2 on pagure.io

+1 On Sat, May 27, 2017 at 8:16 PM, Pierre-Yves Chibon wrote: > On Sat, May 27, 2017 at 11:41:19AM -0600, Kevin Fenzi wrote: > > Greetings. > > > > A while back Patrick made a patch for libgit2 that worked around some of > > its performance and locking issues. When we

Re: COPR and new chroot naming

On Tue, Feb 21, 2017 at 5:15 PM, Kevin Fenzi <ke...@scrye.com> wrote: > On Tue, 21 Feb 2017 11:00:15 +0100 > Michal Novotny <cl...@redhat.com> wrote: > > > On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch <vondr...@redhat.com> > > wrote: > > >

Re: COPR and new chroot naming

nk that makes more sense as well. P.S. Adding devel to the recipient list so that more people can comment. > Vít > > Dne 21.2.2017 v 10:05 Michal Novotny napsal(a): > > Hello folks, > > We have quite recently changed naming of rawhide chroot to fXY in COPR and &g

COPR and new chroot naming

Hello folks, We have quite recently changed naming of rawhide chroot to fXY in COPR and I would like to know your opinion about it. As branching is behind the door, I tried to consider it again and slightly changed my mind. The main problem with just fXY is that it is probably not very

Re: COPR auto-rebuilds on pagure commits

On Mon, Nov 7, 2016 at 3:47 PM, Pierre-Yves Chibon <pin...@pingoured.fr> wrote: > On Mon, Nov 07, 2016 at 02:02:01PM +0100, Michal Novotny wrote: > >Hey, > > > >I'd like to announce that we now support package auto-rebuilding on a > new > >commit(

COPR auto-rebuilds on pagure commits

Hey, I'd like to announce that we now support package auto-rebuilding on a new commit(s) into a Pagure repository. Apart from having your package repo hosted in Pagure, you just need to enable firing of fedmsg notifications for new commits by clicking a single checkbox in 'Hooks' section...well,

Re: PROPOSAL: employ a variant of upstream dist-git package into FedoraInfra

.fr> wrote: > On Thu, Oct 13, 2016 at 02:04:04PM +0200, Michal Novotny wrote: > >Hey, > > > >I'd like to propose employment of an upstream dist-git package for > >deploying pkgs machines. This is the package I have in mind: > >https://github.com/rel

PROPOSAL: employ a variant of upstream dist-git package into FedoraInfra

Hey, I'd like to propose employment of an upstream dist-git package for deploying pkgs machines. This is the package I have in mind: https://github.com/release-engineering/dist-git. This package contains scripts and selinux policy for dist-git files. Note however that I would like to make this

Re: September status update for Fedora Infrastructure Apprentices

On Tue, Sep 6, 2016 at 6:48 PM, Kevin Fenzi wrote: > You are getting this email because you are in the 'fi-apprentice' group > in the fedora account system (or are reading this on the > infrastructure list). > > Feel free to reply just directly to me, or cc the infrastructure