Re: FBR : Greenwave gunicorn timeout back to 30s

:app strategy: type: Docker dockerStrategy: -- 2.20.1 +1s ? -1s ? Clément On Wed, 20 Mar 2019 at 11:57, Clement Verna wrote: > > On Wed, 20 Mar 2019 at 11:52, Stephen John Smoogen wrote: > > > > On Wed, 20 Mar 2019 at 05:15, Pierre-Yves Chibon > > wrote: > &g

Re: FBR : Greenwave gunicorn timeout back to 30s

On Wed, 20 Mar 2019 at 11:52, Stephen John Smoogen wrote: > > On Wed, 20 Mar 2019 at 05:15, Pierre-Yves Chibon wrote: > > > > Sure which value would you suggests ? > > > > We have the data*, we should just look at it :) > > > > * We have stored the time it took to query greenwave for each of the

Re: FBR : Greenwave gunicorn timeout back to 30s

On Wed, 20 Mar 2019 at 09:57, Pierre-Yves Chibon wrote: > > On Wed, Mar 20, 2019 at 08:22:09AM +0100, Clement Verna wrote: > > Hi all, > > > > I would like to revert greenwave's gunicorn timeout to the default > > 30s. Changing it to 10+min was useful for our inve

FBR : Greenwave gunicorn timeout back to 30s

Hi all, I would like to revert greenwave's gunicorn timeout to the default 30s. Changing it to 10+min was useful for our investigation but it now slows down bodhi cron job. Also the greenwave team is working on fix for this so long term we should not need to have a specific timeout. I am leaving

Re: FBR: Greenwave increase gunicorn worker timeout

On Tue, 19 Mar 2019 at 21:42, Randy Barlow wrote: > > On Fri, 2019-03-15 at 15:17 +0100, Clement Verna wrote: > > Hi all, > > > > So after setting higher timeout to the openshift route, it seems that > > now we are hitting gunicorn worker default timeout (30s

Re: FBR - Greenwave investigation bigger timeout

> Last +1 for me of the day. Thanks :-) > > On Fri, 15 Mar 2019 at 15:22, Clement Verna wrote: ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedorapr

Re: FBR - Greenwave investigation bigger timeout

> On Fri, Mar 15, 2019 at 08:10:10PM +0100, Clement Verna wrote: > > +1 for me, but please consider making the openshift time out > than the > gunicorn > one as otherwise they do not appear in the logs of the application. > So something like 660 for gunicorn and 750 for open

FBR - Greenwave investigation bigger timeout

Hi all Still going on with greenwave investigation, I would like to double the timeout (from 330s to 660s) to see if that helps getting the last few tests results that are still failing. I would like to apply the following patch diff --git a/playbooks/openshift-apps/greenwave.yml

FBR: Greenwave increase gunicorn worker timeout

Hi all, So after setting higher timeout to the openshift route, it seems that now we are hitting gunicorn worker default timeout (30s). The following patch increase this value. diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml

FBR: Increase the openshift route timeout for greenwave

Hi all, After doing some investigation on bodhi requests to greenwave I found that the requests are hitting a default 30 seconds timeout from the openshift route (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). I would like to increase this timeout to 330 seconds,

Re: FBR: Add tag to update appowners for Greenwave and Bodhi

at 02:43:07PM +0100, Clement Verna wrote: > > Hi all, > > > > I would like to update the appowners for Greenwave and Bodhi in > > Openshift but I don't want to restart the services so following is a > > Patch to add an ansible tag to only update the appowners. >

FBR: Add tag to update appowners for Greenwave and Bodhi

Hi all, I would like to update the appowners for Greenwave and Bodhi in Openshift but I don't want to restart the services so following is a Patch to add an ansible tag to only update the appowners. diff --git a/playbooks/openshift-apps/bodhi.yml b/playbooks/openshift-apps/bodhi.yml index

Re: FBR : Add cverna to Greenwave appowners

On Thu, 14 Mar 2019 at 14:23, Clement Verna wrote: > > Thanks > > I have applied the patch, could someone run the playbook > (playbooks/openshift-apps/greenwave.yml) for me. We need to hold on so that we don't restart the service when running the playbook > > On Thu,

Re: FBR: Add cverna to Bodhi appowners

On Thu, 14 Mar 2019 at 14:24, Clement Verna wrote: > > Thanks, > > I just applied the patch, could someone run the playbook > (playbooks/openshift-apps/bodhi.yml) for me. Actually this need to hold on so that we don't restart the service when running the playbook > > On T

Re: FBR: Add cverna to Bodhi appowners

Thanks, I just applied the patch, could someone run the playbook (playbooks/openshift-apps/bodhi.yml) for me. On Thu, 14 Mar 2019 at 14:12, Stephen John Smoogen wrote: > > +! > > On Thu, 14 Mar 2019 at 08:44, Pierre-Yves Chibon wrote: > > > > On Thu, Mar 14, 2019 at 1

Re: FBR : Add cverna to Greenwave appowners

2019 at 12:02:20PM +0100, Clement Verna wrote: > > > Hi all, > > > > > > After talking with Giulia on irc, I would like to add myself to the > > > Greenwave appowners to be able to access the logs in openshift. > > > > > > Here is the diff > > >

FBR: Add cverna to Bodhi appowners

Hi all, I would like to be able to check Bodhi's log in openshift, so I would like to add myself to the appowners. diff --git a/playbooks/openshift-apps/bodhi.yml b/playbooks/openshift-apps/bodhi.yml index e761e090f..0e0ccae4c 100644 --- a/playbooks/openshift-apps/bodhi.yml +++

FBR : Add cverna to Greenwave appowners

Hi all, After talking with Giulia on irc, I would like to add myself to the Greenwave appowners to be able to access the logs in openshift. Here is the diff diff --git a/playbooks/openshift-apps/greenwave.yml b/playbooks/openshift-apps/greenwave.yml index b1002abcf..ce86f6951 100644 ---

Re: Fedora Cloud SIG github organization

> On 3/7/19 2:56 PM, Clement Verna wrote: > > Done! Thanks :) ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-con

Fedora Cloud SIG github organization

Hi all, For a while now I take care to update the Fedora container image on Docker Hub using this repo https://github.com/fedora-cloud/docker-brew-fedora. I would like to make this a bit easier and self serviced using a jenkins pipeline. For that I would need administration write to add to

Re: Ansible repo yaml auto format

On Tue, 5 Mar 2019 at 09:59, Alessandro Lorenzi wrote: > > On 3/5/19 9:27 AM, Clement Verna wrote: > > Hi all, > > I would like to know what do you think about using an opinionated code > formatter for our ansible repo ? I think this would help with > enforcing a common

Fedora Badges - User Stories brainstorm meeting

Hi all, I am scheduling a meeting Friday March 08 at 1400 UTC [0] so that we can brainstorm some user stories for Fedora Badges, we will look at the Persona listed in the wiki [1] and find what can be improved for each of them, the expected output of this meeting is to have a Backlog of stories

Re: Future of fedora-packages

On Mon, 4 Mar 2019 at 19:21, Kevin Fenzi wrote: > > On 3/3/19 11:28 PM, Clement Verna wrote: > > > The frontend will be an independent application that we will need to > > develop or as suggested by Ryan we may explore using src.fp.o. Having > > a separated backend fo

Re: Future of fedora-packages

On Sat, 2 Mar 2019 at 21:36, Kevin Fenzi wrote: > > On 2/26/19 11:38 AM, Clement Verna wrote: > > Hi all, > > > > fedora-packages [0] code base is showing its age. The code base and > > the technology stack (Turbogears2 [1] web framework and the Moksha > > [2

Re: External access to the AMQP broker

On Thu, 28 Feb 2019 at 16:04, Jeremy Cline wrote: > > On 2/27/19 2:10 PM, Clement Verna wrote: > > On Wed, 27 Feb 2019 at 18:27, Aurelien Bompard > > wrote: > >> > >> I'm assuming you're considering the solution where we have a single > >> broker

Re: External access to the AMQP broker

On Thu, 28 Feb 2019 at 11:26, Aurelien Bompard wrote: > > > my overall feeling is that the > > risk of DoS should be one of the factor we take into account to make > > the decision but we should also consider how easy is it to use, how > > easy is it to maintain, how much effort is it to setup. >

Re: Future of fedora-packages

/www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/index.html) and handle the search in the frontend then it does not have to go via our infrastructure. > > > > On 2/27/19 4:19 AM, Stephen John Smoogen wrote: > > > On Tue, 26 Feb 2019 at 14:39, Clement Verna &

Re: Future of fedora-packages

d it take to use our current AWS account to setup a test cluster ? > > On 2/27/19 4:19 AM, Stephen John Smoogen wrote: > > On Tue, 26 Feb 2019 at 14:39, Clement Verna > > wrote: > >> > >> Hi all, > >> > >> fedora-packages [0] code base

Re: Future of fedora-packages

On Wed, 27 Feb 2019 at 13:27, Stephen John Smoogen wrote: > > On Tue, 26 Feb 2019 at 14:39, Clement Verna wrote: > > > > Hi all, > > > > fedora-packages [0] code base is showing its age. The code base and > > the technology stack (Turbogears2 [1] web framewo

Re: External access to the AMQP broker

On Wed, 27 Feb 2019 at 18:27, Aurelien Bompard wrote: > > I'm assuming you're considering the solution where we have a single > broker and we make it publicly accessible (option 1). > > > how easy would it be to turn off the possibility for external > > publisher to flood the broker ? > >

Re: External access to the AMQP broker

On Wed, 27 Feb 2019 at 13:32, Stephen John Smoogen wrote: > > On Wed, 27 Feb 2019 at 05:17, Clement Verna wrote: > > > > On Wed, 27 Feb 2019 at 10:57, Aurelien Bompard > > wrote: > > > > > > Hey y'all, > > > > > > Fedora M

Re: Future of fedora-packages

On Wed, 27 Feb 2019 at 10:27, Vít Ondruch wrote: > > > Dne 26. 02. 19 v 23:42 Ryan Lerch napsal(a): > > > > On Wed, 27 Feb 2019 at 05:39, Clement Verna wrote: >> >> Hi all, >> >> fedora-packages [0] code base is showing its age. The code base and

Re: Future of fedora-packages

On Tue, 26 Feb 2019 at 23:52, Ryan Lerch wrote: > > > > On Wed, 27 Feb 2019 at 05:39, Clement Verna wrote: >> >> Hi all, >> >> fedora-packages [0] code base is showing its age. The code base and >> the technology stack (Turbogears2 [1] web

Re: Meeting Agenda Item Introduction: Antonette Caldwell

On Thu, 14 Feb 2019 at 17:01, Antonette Caldwell wrote: > > I just checked in the #fedora-admin and I was added to the Apprentice group. > I would like to know what to do to get started. I read through the > documentation regarding the setup. Since your are interested in development and

Re: Meeting Agenda Item: Introduction Joey Engel

On Thu, 7 Feb 2019 at 05:38, Joey Engel wrote: > > Hello all, > > My name is Joey, and I'm excited to contribute to the Fedora Project. I'm > located in Ohio (UTC -5) and my irc handle is armnhmr. > > I recently obtained my RHCSA, and will graduate with a BS in IT this Spring. > I'm very

Re: Meeting Agenda Item Introduction: Antonette Caldwell

On Wed, 13 Feb 2019 at 17:46, Antonette Caldwell wrote: > > Hi all, > Hi and welcome, > I first came across Fedora back in 2016. I was introduced to Fedora in my > Linux course. I have been interested in computer technologies for nearly have > my life, and I've done web development, as well

Re: Release Engineering Automation effort

On Wed, 30 Jan 2019 at 21:41, Kevin Fenzi wrote: > > On 1/30/19 1:28 AM, Clement Verna wrote: > > Hi all, > > > > I have started a document [0] to gather the releng tasks that would > > benefit automation. At this point I am not looking for the HOW, but > >

Release Engineering Automation effort

Hi all, I have started a document [0] to gather the releng tasks that would benefit automation. At this point I am not looking for the HOW, but more for the WHAT. So if you have any ideas please add an entry to this bullet list [1], Once we have a few items there we can start looking at HOW,

Re: Project Details

On Tue, 29 Jan 2019 at 14:29, Leigh Griffin wrote: > Hey everyone, > > I am trying to get a handle on the number of projects that we are > actively working on for any given day of the week. Could I ask everybody to > reply here with some information. At a minimum if you could share with me: > >

Re: Development brainstorming for Tahrir / Badges (was: Fedora-badges)

. > > On 1/17/19 3:39 AM, Clement Verna wrote: > > Hi Justin, > > > > I am replying here to your IRC questions :-) > > > > So I think that indeed setting up basic CI/CD and maybe a container > > based development environment would be a good start.

Re: Help with docker images for NeuroFedora

> On Tue, Jan 15, 2019 14:54:06 -0000, Clement Verna wrote: > > Ah, right. The pages still mention the cloud SIG. Please update that bit > or you'll find more like me e-mailing the cloud SIG :D > https://fedoraproject.org/wiki/Container:Guidelines#Discussion Cool I just upd

Re: Help with docker images for NeuroFedora

> Hello, > > As part of NeuroFedora, we'd like to make docker images of commonly used > tools available to the research community. This comes in very very handy > when researchers try to replicate scientific results to validate them > (which of course, is paramount). > > Unfortunately, none of

Re: How do we find the source code for our services?

On Thu, 3 Jan 2019 at 11:31, Brian (bex) Exelbierd wrote: > > > > On Thu, Jan 3, 2019 at 8:58 AM Sayan Chowdhury wrote: >> >> On Wed, Jan 2, 2019 at 2:56 PM Brian (bex) Exelbierd >> wrote: >> > >> > I was looking for the source to the badges website/application to fix >> > >> >

Re: New to Fedora

On Thu, 3 Jan 2019 at 05:26, Salman Siddiqui wrote: > > I am a Python Developer and I want to Join this Awesome Open Source > Community. I Love Fedora and now want to contribute in it for GSOC > 2019 to Become a Part of this Community. > Hi Salman and Welcome :) Did you take a look at the

Quay.io fedora-infra organization.

Hi all, In the effort to run asknot-ng [0] to our openshift instance, I have created the fedora-infra organization on quay.io [1]. If you are interested to build and host an infra application on this organization feel free to ping me so I can add you to it. Thanks [0] -

[Fedora-join] Re: Updating Classroom post(s)

On Fri, 14 Dec 2018 at 23:43, Alberto Rodriguez Sanchez wrote: > > Hello Magazine Team, > > I'm looking to update this post: > > https://fedoramagazine.org/fedora-classroom-containers-101-podman/ > > Adding/changing the "Joining the session" section to add the link to the > video of the session:

Proposal : Use OSBS to build the fedora container base image

Hi all, I would like to get feedbacks on the following proposal. Use OSBS to build the fedora container base image, indeed OSBS has the capability to build a base container image using a kickstart file. To do this OSBS needs a Dockerfile, a kickstart file and an image-build.conf file stored in

Proposal : Use OSBS to build the fedora container base image

Hi all, I would like to get feedbacks on the following proposal. Use OSBS to build the fedora container base image, indeed OSBS has the capability to build a base container image using a kickstart file. To do this OSBS needs a Dockerfile, a kickstart file and an image-build.conf file stored in

Re: Proposal: Move to an annual platform release starting at F30

On Tue, 27 Nov 2018 at 17:23, Owen Taylor wrote: > > On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote: > > On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote: > > > But for the next thousand or so Fedora developers, the release cycle > > > is actually not a big deal - not something that takes

Re: Container updates available in bodhi

On Wed, 21 Nov 2018 at 16:37, Ken Dreyer wrote: > On Thu, Nov 15, 2018 at 6:09 AM Clement Verna > wrote: > > > > On Thu, 15 Nov 2018 at 13:55, Petr Pisar wrote: > >> And unrelated question: The koji build NVR does not contain dist-git > >> name spac

Re: How does an apprentice graduate ?

On Sun, 18 Nov 2018 at 20:40, Kevin Fenzi wrote: > On 11/16/18 11:08 AM, Clement Verna wrote: > > Hi all, > > > > Is there an official way for an apprentice to move ot the next level ? ( > > joining the sysadmin group ?). > > > > I was looking a

Packages Full text search API : fedora-search

Dear all, In a effort to run fedora-packages [0] on our infrastructure Openshift instance, I have been working on replacing the current full text search engine powered by xapian by a new service that uses postgresql full text search capabilities and Django DRF. The proof of concept of this

How does an apprentice graduate ?

Hi all, Is there an official way for an apprentice to move ot the next level ? ( joining the sysadmin group ?). I was looking at [0] but could find anything about how an apprentice stops being an apprentice. [0] - https://fedoraproject.org/wiki/Infrastructure_Apprentice

Re: Container updates available in bodhi

On Thu, 15 Nov 2018 at 13:55, Petr Pisar wrote: > On 2018-11-14, Clement Verna wrote: > > After a successful OSBS build, a bodhi update can be created. Fedpkg does > > not yet support creating updates for containers [0], so you have to > either > > use bodhi web UI or th

Re: Container updates available in bodhi

> On Wed, Nov 14, 2018 at 09:05:44PM +0100, Clement Verna wrote: > > This is a great news! > > Just to clarify for those like me who aren't playing with containers much. > What happened before? There was no updates of containers at all? > Assuming there was update, is t

Re: Introducing Luiz Carvalho

On Thu, 15 Nov 2018 at 03:34, Ralph Bean wrote: > Hi all, > > Just an FYI - I've moved off of the Factory 2 team inside Red Hat to > take a different role in the internal devops organization there. > > Luiz Carvalho (lucarval in both FAS and irc) takes my place leading > the Factory 2 team!

Container updates available in bodhi

Dear all, It is now possible to use bodhi to release a new container build. Currently it is following the same flow as packages. After a successful OSBS build, a bodhi update can be created. Fedpkg does not yet support creating updates for containers [0], so you have to either use bodhi web UI

[atomic-devel] Container updates available in bodhi

Dear all, It is now possible to use bodhi to release a new container build. Currently it is following the same flow as packages. After a successful OSBS build, a bodhi update can be created. Fedpkg does not yet support creating updates for containers [0], so you have to either use bodhi web UI

fedora-tagger and statscache sunset

Dear all, As previously announced [0][1] fedora-tagger and statscache will be retired next Tuesday Oct 02 2018 at 21.00 UTC. Thanks [0] - https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/message/RY23KIVRXFVXMTGMXNDV4D7NXM2V2NUJ/ [1] -

fedora-tagger and statscache sunset

Dear all, As previously announced [0][1] fedora-tagger and statscache will be retired next Tuesday Oct 02 2018 at 21.00 UTC. Thanks [0] - https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/message/RY23KIVRXFVXMTGMXNDV4D7NXM2V2NUJ/ [1] -

fedora-tagger and statscache sunset

Dear all, As previously announced [0][1] fedora-tagger and statscache will be retired next Tuesday Oct 02 2018 at 21.00 UTC. Thanks [0] - https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/RY23KIVRXFVXMTGMXNDV4D7NXM2V2NUJ/ [1] -

Re: Proposal: Add release announcement post to Go/No-Go criteria

On Wed, 26 Sep 2018 at 14:44, Brian (bex) Exelbierd wrote: > > > On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote: > >> On 09/25/2018 01:35 PM, Ben Cotton wrote: >> > With today's Beta release, the release announcement post for Fedora >> > Magazine was not ready. As a result, the announcement

Re: [PATCH] Anitya 0.13.0 release

On Wed, 12 Sep 2018 at 10:45, Michal Konečný wrote: > Hi, > > here is a patch for ansible for deployment of Anitya 0.13.0. > That's an interesting case Anitya is not in the frozen application list but Openshift is. Since Anitya will now run on Openshift does that mean that to deploy a new

Re: Moving forward with Fedora's PDC

On Wed, 12 Sep 2018 at 09:40, Aurelien Bompard wrote: > > everything should be there for > > this with one exception: We really want to have some check in place for > > s2i so that it checks license, so we don't accidentally push out > > something thats not under a open source license. This

Moving forward with Fedora's PDC

Hi all, I would like to start working on the replacement application for PDC in Fedora. So far I have been mostly looking at the technical side of the application and how it will be setup in our infrastructure. Below is a list of the design decisions I am looking to take. I would really value

Re: FBR - Add the Fedora Favicon to registry.fp.o

Thanks, I just pushed this change. On Wed, 5 Sep 2018 at 17:10, Stephen John Smoogen wrote: > +1 > On Wed, 5 Sep 2018 at 09:27, Michal Konečný wrote: > > > > +1 > > > > mkonecny > > > > On 5.9.2018 15:14, Clement Verna wrote: > > > > &

Re: FBR - Add the Fedora Favicon to registry.fp.o

On Mon, 3 Sep 2018 at 22:24, Kevin Fenzi wrote: > Seems simple enough... +1 > > kevin > > Anybody else for another +1 ? > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

FBR - Add the Fedora Favicon to registry.fp.o

Hi all, Currently https://registry.fedoraproject.org does not have the Fedora favicon. The following patch should fix this. +1s ? Thanks >From 61aae4a233a9081e41d12a1341d7c8156ffe44b8 Mon Sep 17 00:00:00 2001 From: Clement Verna Date: Sun, 2 Sep 2018 12:21:13 +0200 Subject: [PATCH 1/1]

Re: FBR Add OSBS to aarch64.

On Thu, 30 Aug 2018 at 20:54, Stephen John Smoogen wrote: > This needs review by both infrastructure and people who are familiar > with osbs. I am mostly copya pasta editing here so it may or may not > work. It is also not clear if we need both a master and a node or just > a master. > > Looks

Re: [atomic-devel] [CoreOS] Re: Re: Starting a Container SIG

On Sat, 25 Aug 2018 at 15:29, Dusty Mabe wrote: > > > On 08/24/2018 10:24 AM, Brian Clark wrote: > > Are there any minutes from this meeting? > > Here ya go: > > > https://meetbot.fedoraproject.org/fedora-containers/2018-08-23/fedora_container_sig_kickoff.2018-08-23-15.00.html We also have a

Fwd: fedora-tagger sunset - week post F29 beta freeze

Dear all, The Fedora Infrastructure is running the fedora-tagger [0] service, however it gets little usage and also has no one really maintaining it or fixing issues with it. Earlier this year [1] we have tried to support community members who expressed their interests in maintaining this

Fwd: fedora-tagger sunset - week post F29 beta freeze

Dear all, The Fedora Infrastructure is running the fedora-tagger [0] service, however it gets little usage and also has no one really maintaining it or fixing issues with it. Earlier this year [1] we have tried to support community members who expressed their interests in maintaining this

Call for users of statscache

Dear all, During our last meeting [0], we have talked about retiring the statscache service [1]. This is in line with an on going effort to reduce the number of application the infrastructure team has to maintain. The motivation behind this service was to generate statistics using the data of

Re: [atomic-devel] [CoreOS] Re: Re: Starting a Container SIG

Dear all, I have scheduled our first IRC meeting for this week Thursday (August 23, 2018 - 15:00 UTC) on #fedora-containers (freenode) [0]. The agenda for this meeting is : - everyone interested in the SIG to introduce themselves - Go through some of the discussion we had during flock. -

Re: [atomic-devel] [CoreOS] Re: Re: Starting a Container SIG

Dear all, I have scheduled our first IRC meeting for this week Thursday (August 23, 2018 - 15:00 UTC) on #fedora-containers (freenode) [0]. The agenda for this meeting is : - everyone interested in the SIG to introduce themselves - Go through some of the discussion we had during flock. -

Re: Introduction

On Mon, 13 Aug 2018 at 17:47, Michal Konečný wrote: > > Hi everyone, > > I'm new in Fedora Infrastructure and will take care of Anitya and > the-new-hotness apps. > > I will try to do my best to make these applications great and shiny. > > My IRC nick: mkonecny > My Github nick: Zlopez >

Re: [Fedocal] Reminder meeting : Infra Office Hours

I won't be available to run the office hours this week because of Flock :) On Mon, 6 Aug 2018, 20:57 , wrote: > Dear all, > > You are kindly invited to the meeting: >Infra Office Hours on 2018-08-07 from 18:00:00 to 19:00:00 UTC >At fedora-ad...@irc.freenode.net > > The meeting will be

Re: [atomic-devel] [CoreOS] Re: Starting a Container SIG

des some initial help that > shouldn't be underestimated. > I added https://discussion.fedoraproject.org/c/containers to the wiki page. I am happy to use it instead of the mailing list :) > On Tue, Jul 31, 2018 at 10:59 AM, Matthew Miller > wrote: >> >> On Wed, Jul 25, 2018

Re: [atomic-devel] [CoreOS] Re: Starting a Container SIG

des some initial help that > shouldn't be underestimated. > I added https://discussion.fedoraproject.org/c/containers to the wiki page. I am happy to use it instead of the mailing list :) > On Tue, Jul 31, 2018 at 10:59 AM, Matthew Miller > wrote: >> >> On Wed, Jul 25, 2018

Re: [atomic-devel] Starting a Container SIG

> > development within > > Fedora Workstation. > > > > I can contribute a certain familiarity with OCI images, OSBS, the image > > registry, etc. > > > > Owen > > > > On Wed, Jul 25, 2018 at 1:09 PM, Clement Verna > > wrote: > &g

Re: [atomic-devel] Starting a Container SIG

> > development within > > Fedora Workstation. > > > > I can contribute a certain familiarity with OCI images, OSBS, the image > > registry, etc. > > > > Owen > > > > On Wed, Jul 25, 2018 at 1:09 PM, Clement Verna > > wrote: > &g

Re: Rust SIG

On Mon, 30 Jul 2018 at 17:45, Brian (bex) Exelbierd wrote: > > > > On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka wrote: >> >> Do you plan any hackfest during Flock? > > > We are booked out for schedule hacks during Flock, however there is usually > some space on the edges for impromptu

Re: Introduction

On Sun, 29 Jul 2018 at 01:24, wrote: > > Hi all! > > I would like to join the Fedora Infrastructure group. > > IRC: se-sm-ca > > Skills: > > > Bash, and an okay amount of Python. Have written a couple web apps > with Python > > Work as a Linux admin with a few years of experience - more Ops >

Starting a Container SIG

Greeting all, The container effort in Fedora has until now been looked after by the Atomic WG, since this Working Group is now going to focus mostly on Fedora CoreOS, I propose to create a new container SIG to regroup people interested in the maintenance of application containers in Fedora. This

[atomic-devel] Starting a Container SIG

Greeting all, The container effort in Fedora has until now been looked after by the Atomic WG, since this Working Group is now going to focus mostly on Fedora CoreOS, I propose to create a new container SIG to regroup people interested in the maintenance of application containers in Fedora. This

Re: python2 and fedora deployed applications

On Tue, 24 Jul 2018 at 00:02, Kevin Fenzi wrote: > > Greetings. > > There's discussion on the devel list about how to handle the end of life > of python2 in Fedora. This will most likely happen next year. Of course > our applications still running on rhel7 should continue to be ok, but > anything

Re: github fedora-infra project cleanup

On Mon, 23 Jul 2018 at 22:56, Kevin Fenzi wrote: > > ok. I went and archived all the following. > > Please let me know if there's anything here that should be unarchived or > any other projects that aren't yet archived that should be. > > https://github.com/fedora-infra/android-pusher >

Re: Compose tooling completed deadline today

On Wed, 18 Jul 2018 at 23:33, Kevin Fenzi wrote: > > On 07/18/2018 10:40 AM, Ben Cotton wrote: > > Hi Infra team, > > > > The schedule[1] says today is the deadline for compose tooling > > completed. Are we good on this or are there still changes to that in > > flight? > > > > [1]

Re: Fedora and PDC, road forward

On Tue, 12 Jun 2018 at 16:48, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > So yesterday we held a meeting on #fedora-apps about the future of PDC in > Fedora. > We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora > Here is the gist of it: > > What do we currently

Re: Fedora and PDC, road forward

On Tue, 19 Jun 2018 at 01:13, Aurelien Bompard wrote: > > > Within limits. It should be a version thats supported and gets at least > > security updates. Hopefully the one(s) in Fedora follow this. > > Yeah it's 1.11 now which is LTS, since it'll be the last version to > support Python 2 > > >

Re: Infrastructure office hours

> I create a poll so we can try to see if there is a time slot that > would please most of us :). > > Please vote for the time (In UTC) that you like best: > > https://framadate.org/bhNm9poKGUV93hDG > > If there is a time that would work out best for you but it is not in > the poll, just reply to

Re: Fedora and PDC

On Thu, 7 Jun 2018 at 20:34, Randy Barlow wrote: > > On 06/07/2018 12:20 PM, Pierre-Yves Chibon wrote: > > I propose that we meet up next week on Monday at 14:00 UTC. > > Works for me. That works for me too > > > What do you prefer, IRC or video (bluejeans)? > > I have a slight preference for

Re: Infrastructure office hours

On Sun, 3 Jun 2018 at 20:42, Till Maas wrote: > > Hi, > > On Fri, Jun 01, 2018 at 01:14:29PM -0700, Kevin Fenzi wrote: > > > We have tried things like this in the past, but I'd be happy to give it > > another go. ;) > > great. > > > The hard part is picking times. What day/time should we give

Infrastructure office hours

Dear all, I would like to get feedback about starting a weekly infrastructure office hours which would be used to help anyone with contributing to Fedora's infrastructure. This would be a dedicated IRC meeting where people would be available to answer questions, help setting up development

FBR - Fixing OSBS build

Currently OSBS builds are failing because of the kerberos configuration not been up-to-date. I would like to add the following to the osbs-playbook, this will make sure that the buildroot container is rebuild using the latest krb5.conf file. +1 ? diff --git

Re: FBR: open heart surgery on fedimg01

On 25 April 2018 at 18:50, Dusty Mabe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > On Sunday April 22nd we identified an issue with the describe-conversion-tasks > AWS API that was causing fedimg to fail when uploading images. I worked with > David Duncan

Re: [release] - fedora-packages 4.0.0

This is version 4.1.1 and not 4.0.0 as the subject suggest :) On 23 April 2018 at 13:34, Clement Verna <cve...@fedoraproject.org> wrote: > Greetings, > > A new release of fedora-packages is now deployed in stg and prod. This > release allows to display F28 in the Active

[release] - fedora-packages 4.0.0

Greetings, A new release of fedora-packages is now deployed in stg and prod. This release allows to display F28 in the Active Releases Overview. The changelog is available in here[0]. Happy searching. [0] - https://github.com/fedora-infra/fedora-packages/blob/develop/CHANGELOG.rst#411

Re: Fedora and PDC

On 20 April 2018 at 20:15, Randy Barlow wrote: > Bodhi also uses PDC to determine which packages are critpath per release. > > I'm interested in this topic, so please do invite me to discuss next week! > > > ___ >

FBR - Adding myself to nagios permission

I would like to add myself to the nagios permission, so that I can acknowledge problems (mostly packages03 and OSBS). I pushed this commit --> https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=2f212ac9a8c5f39bd6026b407aa0453fee5446ab +1 to run the playbook ? Thanks

<    1   2   3   4   5   >