Re: Redis on OCP4 - Operator or ansible?
You could develop re-usable ansible roles that would fit both scenarios. An ansible operator can load external roles as any ansible project. On Thu, May 19, 2022 at 2:37 PM Michal Konecny wrote: > Hi everyone, > > the-new-hotness [0] was recently moved to OpenShift 4 cluster [1] on > staging. One of the latest commits added support for Redis as cache to > the-new-hotness and according to the Redis documentation there is an > OpenShift 4 operator for Redis [2]. > > The question is: Do we want to use operators or just write the > deployment by yourself in ansible? Or it is possible to convert the > Redis deployment made by operator to ansible? > > I would prefer to have everything in the ansible in case we need to > start with fresh OpenShift project. > > What do you think? > > Michal > > [0] - https://github.com/fedora-infra/the-new-hotness > [1] - https://console-openshift-console.apps.ocp.stg.fedoraproject.org/ > [2] - > > https://docs.redis.com/latest/kubernetes/deployment/openshift/openshift-operatorhub/ > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Self Introduction: Prakash Mishra
Welcome Prakash, happy to have you onboard :-) On Fri, Apr 15, 2022 at 1:09 PM David Kirwan wrote: > Welcome Prakash! > > On Fri, 15 Apr 2022 at 16:09, Prakash Mishra > wrote: > >> Hello everyone, >> >> I'm Prakash from Bangalore in India. I currently work as a Golang >> developer working mainly with Kubernetes Operators and multi cluster >> Kubernetes management. I've used Fedora as my daily driver for large parts >> in the past. >> >> I started my contribution journey with Vipul(Vipul SIddharth) back in >> 2016 by contributing to Fedora QA when we were attending university. My >> career took me down a different path later as I got more involved with the >> Kubernetes community here in India. >> >> I recently got involved with Fedora Infrastructure and the KubeDev SIG >> where David(Dkirwan) and Leo(Lrossett) have helped me immensely in getting >> started. David and I spent a couple of hours today migrating >> https://stg.whatcanidoforfedora.org to OCP4. The changes can be viewed >> here: >> https://pagure.io/fedora-infra/ansible/c/46b773c87a1dc6edd1c19425c6ef2fa169720420?branch=main. >> I look forward to working with you and I hope you have a great weekend >> ahead. >> >> Cheers, >> Prakash Mishra. >> >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > > > -- > David Kirwan > Software Engineer > > Community Platform Engineering @ Red Hat > > T: +(353) 86-8624108 IM: @dkirwan > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: fedimg
I can take a look at it if nobody wants/is working it :-) On Mon, Jun 7, 2021 at 2:39 PM Kevin Fenzi wrote: > Hey everyone. > > We have a application called fedimg that takes our images and uploads > them to AWS. We have talked about replacing it, but we haven't done so. > > However, we now have a request to also upload the ELN images: > https://pagure.io/fedora-infrastructure/issue/9944 > > Would there be anyone who would like to investigate how to add ElN image > uploads to fedimg? I can do it, but I have a bunch of other things too, > so this might be a nice thing for others to work on to get involved. > > https://github.com/fedora-infra/fedimg > > Any takers? > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Possible outdated Jenkins jobs
Apologies, let me add some context again :-) We are planning on migrating the fedora-infra jenkins instance[1] to a new cluster (also moving from static jenkins agents to kubernetes/openshift based agents) but I wanted to check how many of those jobs are still used since some look to be outdated. I got responses for the majority of jobs but there are still a few in the list that remain unknown about their status: https://jenkins-fedora-infra.apps.ci.centos.org/job/fegistry/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-infra-reports/ https://jenkins-fedora-infra.apps.ci.centos.org/job/gimp-help-2/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-kickstarts/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-comps/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-module-defaults-sgallagh/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_py2.7/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_EL6_py2.6/ https://jenkins-fedora-infra.apps.ci.centos.org/job/javapackages-tools/ https://jenkins-fedora-infra.apps.ci.centos.org/job/java-packaging-howto/ https://jenkins-fedora-infra.apps.ci.centos.org/job/xmvn/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-metadata-service/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-dnf-plugin/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-trello-taiga-sync/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd-resolver/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd/ [1] - https://jenkins-fedora-infra.apps.ci.centos.org On Thu, Nov 5, 2020 at 7:59 AM Leonardo Rossetti wrote: > Ha, thanks, there are only a few jobs left now: > > https://jenkins-fedora-infra.apps.ci.centos.org/job/fegistry/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-infra-reports/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/gimp-help-2/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-kickstarts/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-comps/ > > https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-module-defaults-sgallagh/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_py2.7/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_EL6_py2.6/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/javapackages-tools/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/java-packaging-howto/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/xmvn/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-metadata-service/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-dnf-plugin/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-trello-taiga-sync/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd-resolver/ > https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd/ > > Looping the devel mailing list for wider reach. > > > On Wed, Nov 4, 2020 at 2:54 PM Adam Williamson > wrote: > >> On Mon, 2020-11-02 at 11:30 -0300, Leonardo Rossetti wrote: >> > https://jenkins-fedora-infra.apps.ci.centos.org/job/pungi-modularity/ >> >> This looks to be associated with >> https://pagure.io/pungi-modularity , which hasn't been touched for four >> years. Seems pretty likely it can go. The maintainer is now a release >> manager at SUSE, according to Github...:) >> -- >> Adam Williamson >> Fedora QA Community Monkey >> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net >> http://www.happyassassin.net >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> > > > -- > > Leonardo Rossetti > > Senior Software Engineer, > > Red Hat <https://www.redhat.com> > > lross...@redhat.com > M: +55-11-99703-0621 > <https://www.redhat.com> > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Possible outdated Jenkins jobs
Ha, thanks, there are only a few jobs left now: https://jenkins-fedora-infra.apps.ci.centos.org/job/fegistry/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-infra-reports/ https://jenkins-fedora-infra.apps.ci.centos.org/job/gimp-help-2/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-kickstarts/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-comps/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-module-defaults-sgallagh/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_py2.7/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_EL6_py2.6/ https://jenkins-fedora-infra.apps.ci.centos.org/job/javapackages-tools/ https://jenkins-fedora-infra.apps.ci.centos.org/job/java-packaging-howto/ https://jenkins-fedora-infra.apps.ci.centos.org/job/xmvn/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-metadata-service/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-dnf-plugin/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-trello-taiga-sync/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd-resolver/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd/ Looping the devel mailing list for wider reach. On Wed, Nov 4, 2020 at 2:54 PM Adam Williamson wrote: > On Mon, 2020-11-02 at 11:30 -0300, Leonardo Rossetti wrote: > > https://jenkins-fedora-infra.apps.ci.centos.org/job/pungi-modularity/ > > This looks to be associated with > https://pagure.io/pungi-modularity , which hasn't been touched for four > years. Seems pretty likely it can go. The maintainer is now a release > manager at SUSE, according to Github...:) > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Possible outdated Jenkins jobs
I would like some feedback on those jobs as well, they have a considerable number of builds but some haven't been used for a long time while others have been failing a lot (some don't even have one successful build): https://jenkins-fedora-infra.apps.ci.centos.org/job/fegistry/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-infra-reports/ https://jenkins-fedora-infra.apps.ci.centos.org/job/gimp-help-2/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-kickstarts/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-comps/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-module-defaults-sgallagh/ https://jenkins-fedora-infra.apps.ci.centos.org/job/elections/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedocal/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-hubs/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-rube/ https://jenkins-fedora-infra.apps.ci.centos.org/job/nuancier/ https://jenkins-fedora-infra.apps.ci.centos.org/job/PackageDB2/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_py2.7/ https://jenkins-fedora-infra.apps.ci.centos.org/job/FedoraReview_EL6_py2.6/ https://jenkins-fedora-infra.apps.ci.centos.org/job/javapackages-tools/ https://jenkins-fedora-infra.apps.ci.centos.org/job/java-packaging-howto/ https://jenkins-fedora-infra.apps.ci.centos.org/job/xmvn/ https://jenkins-fedora-infra.apps.ci.centos.org/job/blockerbugs/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-metadata-service/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-dnf-plugin/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-trello-taiga-sync/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd-resolver/ https://jenkins-fedora-infra.apps.ci.centos.org/job/pungi-modularity/ https://jenkins-fedora-infra.apps.ci.centos.org/job/tunir/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd/ On Tue, Nov 3, 2020 at 2:43 PM Leonardo Rossetti wrote: > sounds good :-) > > On Tue, Nov 3, 2020 at 2:33 PM Vít Ondruch wrote: > >> I have rather suggesting the opposite direction, i.e. dropping it and if >> I by a chance found the energy, I'll set it up again. But thx for cheering >> me up ;) >> >> >> Vít >> >> >> Dne 03. 11. 20 v 18:30 Leonardo Rossetti napsal(a): >> >> ha no worries we can keep it and make it work :) >> >> On Mon, Nov 2, 2020 at 2:16 PM Vít Ondruch wrote: >> >>> >>> Dne 02. 11. 20 v 15:30 Leonardo Rossetti napsal(a): >>> > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/ >>> > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/> >>> > >>> > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/ >>> > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/> >>> >>> >>> I have never found the energy to make this work after migration from >>> Fedora CI to CentOS CI :/ >>> >>> >>> Vít >>> ___ >>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >>> To unsubscribe send an email to >>> infrastructure-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >>> >> >> >> -- >> >> Leonardo Rossetti >> >> Senior Software Engineer, >> >> Red Hat <https://www.redhat.com> >> >> lross...@redhat.com >> M: +55-11-99703-0621 >> <https://www.redhat.com> >> >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedo
Re: Possible outdated Jenkins jobs
sounds good :-) On Tue, Nov 3, 2020 at 2:33 PM Vít Ondruch wrote: > I have rather suggesting the opposite direction, i.e. dropping it and if I > by a chance found the energy, I'll set it up again. But thx for cheering me > up ;) > > > Vít > > > Dne 03. 11. 20 v 18:30 Leonardo Rossetti napsal(a): > > ha no worries we can keep it and make it work :) > > On Mon, Nov 2, 2020 at 2:16 PM Vít Ondruch wrote: > >> >> Dne 02. 11. 20 v 15:30 Leonardo Rossetti napsal(a): >> > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/ >> > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/> >> > >> > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/ >> > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/> >> >> >> I have never found the energy to make this work after migration from >> Fedora CI to CentOS CI :/ >> >> >> Vít >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> > > > -- > > Leonardo Rossetti > > Senior Software Engineer, > > Red Hat <https://www.redhat.com> > > lross...@redhat.com > M: +55-11-99703-0621 > <https://www.redhat.com> > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Possible outdated Jenkins jobs
ha no worries we can keep it and make it work :) On Mon, Nov 2, 2020 at 2:16 PM Vít Ondruch wrote: > > Dne 02. 11. 20 v 15:30 Leonardo Rossetti napsal(a): > > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/ > > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/> > > > > https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/ > > <https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/> > > > I have never found the energy to make this work after migration from > Fedora CI to CentOS CI :/ > > > Vít > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Possible outdated Jenkins jobs
Hello all, We would like to "migrate" the current jenkins instance to a new centos-ci infrastructure but there are several jobs that will need to be migrated as well - the process would be to provision a new openshift cluster + a Jenkins instance and migrate those jobs from the current instance to the new one. Some jobs were never used while others had a few runs but haven't been used since 2018, so I would like to get some feedback on how many of those could be skipped/ignored. *Jobs that were never used/triggered:* https://jenkins-fedora-infra.apps.ci.centos.org/job/autocloudreporter-pagure-pr/ https://jenkins-fedora-infra.apps.ci.centos.org/job/Fedora%20Docs%20Builder%202.0%20POC/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-bootstrap/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedrepo_req/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-orchestrator/ https://jenkins-fedora-infra.apps.ci.centos.org/job/gotun/ https://jenkins-fedora-infra.apps.ci.centos.org/job/ipsilon/ https://jenkins-fedora-infra.apps.ci.centos.org/job/kgt/ https://jenkins-fedora-infra.apps.ci.centos.org/job/koschei/ https://jenkins-fedora-infra.apps.ci.centos.org/job/koschei-it/ https://jenkins-fedora-infra.apps.ci.centos.org/job/koschei-rpm/ https://jenkins-fedora-infra.apps.ci.centos.org/job/lib389/ https://jenkins-fedora-infra.apps.ci.centos.org/job/modularity-testing-framework/ https://jenkins-fedora-infra.apps.ci.centos.org/job/modularity-tools/ https://jenkins-fedora-infra.apps.ci.centos.org/job/NetworkManager/ https://jenkins-fedora-infra.apps.ci.centos.org/job/OpenShift%20Sample/ https://jenkins-fedora-infra.apps.ci.centos.org/job/pagure/ https://jenkins-fedora-infra.apps.ci.centos.org/job/relvalconsumer-pagure-pr/ https://jenkins-fedora-infra.apps.ci.centos.org/job/resultsdb_conventions/ https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby-chkbuild/ *Jobs that were triggered once or twice (last run was in 2018):* https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-dnf-plugin/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-metadata-service/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-modulemd-resolver/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fm-trello-taiga-sync/ https://jenkins-fedora-infra.apps.ci.centos.org/job/mpi4py/ https://jenkins-fedora-infra.apps.ci.centos.org/job/pungi-modularity/ https://jenkins-fedora-infra.apps.ci.centos.org/job/tunir/ https://jenkins-fedora-infra.apps.ci.centos.org/job/blockerbugs/ *Jobs that had more than 2 runs but the last run was back in 2018:* https://jenkins-fedora-infra.apps.ci.centos.org/job/xmvn/ https://jenkins-fedora-infra.apps.ci.centos.org/job/javapackages-tools/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-tagger/ *Jobs that had their last run in 2019:* https://jenkins-fedora-infra.apps.ci.centos.org/job/nuancier/ https://jenkins-fedora-infra.apps.ci.centos.org/job/fedora-module-defaults-sgallagh/ https://jenkins-fedora-infra.apps.ci.centos.org/job/java-packaging-howto/ https://jenkins-fedora-infra.apps.ci.centos.org/job/ruby/ Regards, -- Leonardo Rossetti Senior Software Engineer Red Hat <https://www.redhat.com> lross...@redhat.com <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Ideas for more releng automation
Would it be possible to use ansible vault files for that (using some kind of internal ansible API)? On Fri, Apr 17, 2020 at 10:15 AM Pierre-Yves Chibon wrote: > On Fri, Apr 17, 2020 at 09:22:27AM -0300, Leonardo Rossetti wrote: > >On Fri, Apr 17, 2020 at 8:07 AM Clement Verna > ><[1]cve...@fedoraproject.org> wrote: > > > > Hi all, > > I wanted to start a discussion and possibly some work around > automating > > the manual tasks involved in the release engineering work. > > In particular I have in mind the following tasks : > > - processing the unretire package tickets. > > - processing the requests for a new package or a new branch. > > - container base image release. > > Instead of looking at each of these individually I was thinking > that it > > might be interesting to look at having an automation framework or > > something like a bot that could be flexible enough to add more > tasks or > > process in the future. > > To do that we have different possibilities, one could be to build a > bot > > that has a similar architecture than the compose-tracker > > ([2]https://pagure.io/releng/compose-tracker) ie a fedora-messaging > > consumer processing messages. > > Another option is to use loopabull > > ([3]https://github.com/maxamillion/loopabull) to trigger ansible > > playbook on fedora-messaging messages. > > Both solutions are quite similar, but one (loopabull) provides > already > > the boilerplate to trigger a script or a function based on messages > > received (a bit like AWS lambda or other serverless framework). We > also > > have already a few process automated that way > > ([4]https://pagure.io/Fedora-Infra/loopabull-tasks). > > So I believe that using loopabull might be the best way forward, > but I > > would be interested to hear about other ideas :-) > > > >I would lean to use loopabull because it already works in a "reactive > way" > >with mq messages and we don't need to write a full application since > we > >will be using ansible (which still can be "extended" developing > modules > >for complex tasks) - the above script could become a couple of ansible > >modules to be used in a playbook with loopabull. > > I like loopabull, having been pretty much the only one playing with it > since > Adam, I think it's a nice and fine tool and we should try leveraging it. > There is one angle where it isn't straight forward to use, it's secrets. > Currently the API tokens the scripts are using are passed as CLI argument > when > calling the script. > If we end up needing something like kerberos keytab for example, we may > have to > think how to do this and evaluate if loopabull is still a good fit. > > > Pierre > ___ > rel-eng mailing list -- rel-...@lists.fedoraproject.org > To unsubscribe send an email to rel-eng-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/rel-...@lists.fedoraproject.org > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Ideas for more releng automation
On Fri, Apr 17, 2020 at 8:07 AM Clement Verna wrote: > Hi all, > > I wanted to start a discussion and possibly some work around automating > the manual tasks involved in the release engineering work. > > In particular I have in mind the following tasks : > - processing the unretire package tickets. > - processing the requests for a new package or a new branch. > - container base image release. > > Instead of looking at each of these individually I was thinking that it > might be interesting to look at having an automation framework or something > like a bot that could be flexible enough to add more tasks or process in > the future. > > To do that we have different possibilities, one could be to build a bot > that has a similar architecture than the compose-tracker ( > https://pagure.io/releng/compose-tracker) ie a fedora-messaging consumer > processing messages. > Another option is to use loopabull ( > https://github.com/maxamillion/loopabull) to trigger ansible playbook on > fedora-messaging messages. > > Both solutions are quite similar, but one (loopabull) provides already the > boilerplate to trigger a script or a function based on messages received (a > bit like AWS lambda or other serverless framework). We also have already a > few process automated that way ( > https://pagure.io/Fedora-Infra/loopabull-tasks). > So I believe that using loopabull might be the best way forward, but I > would be interested to hear about other ideas :-) > I would lean to use loopabull because it already works in a "reactive way" with mq messages and we don't need to write a full application since we will be using ansible (which still can be "extended" developing modules for complex tasks) - the above script could become a couple of ansible modules to be used in a playbook with loopabull. > > Now if we look at the tasks to automate, I was thinking that we could > implement that automation in different phases : > > *un-retiring tickets*: > >- First step would be to run automatically the check-unretirement >script ( >https://pagure.io/releng/blob/master/f/scripts/check-unretirement.py) >and redirect its output into the ticket comments. That way people >processing the ticket have all the information available in the ticket. >- Second step would be to process automatically the tickets that do >not require a new bz review (retired less than 8 weeks ago) >- Finally see if we can process automatically all the tickets. > > > *creating new dist-git repo or branches:* > >- Idea here would be to run the fedscm-admin ( >https://pagure.io/fedscm-admin) cli automatically when a new ticket is >created here (https://pagure.io/releng/fedora-scm-requests). > > I think it would also need to check for missed tickets from time to time, like every 5 minutes for example, in case it missed one for whatever reason. > *container base image release:* > >- Instead of building the image every night, we could rebuild the >image only when at least 1 package present in the base image has been >updated. >- Push the image weekly to the registry if a build happened during >that week. > > Is there any particular reason for using a weekly push schedule (assuming doing one on every build is way too much)? > > > Again here are some ideas, and I would very much appreciate feedback or > other ideas :-). Also if you think about another process that could be > automated that way please share it :-). > > Thanks > Clément > > ___ > rel-eng mailing list -- rel-...@lists.fedoraproject.org > To unsubscribe send an email to rel-eng-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/rel-...@lists.fedoraproject.org > -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
[AAA] automation repository
I noticed that we have ansible automation in some of our repositories: * Securias: https://github.com/fedora-infra/securitas/tree/master/devel/ansible * Local dev env using vagrant for fasjson being landed: https://github.com/fedora-infra/fasjson/pull/5 Do you think it makes sense to have a dedicated repository for this "installation/automation" work? This "automation" repository could have: * ansible code to deploy freeipa, fasjson, securitas and any other related component (to provision it in bare servers, local vm or even kubernetes) * Vagrantfile for local dev env * terraform code for infra provisioning I would like to know your thoughts on this. Regards, -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lross...@redhat.com M: +55-11-99703-0621 <https://www.redhat.com> ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Meeting Agenda Item: Introduction Leonardo Rossetti
Hello there, My name is Leonardo Rossetti, nickname Leo, I am currently located in São Paulo - Brazil (GMT-3) and my irc username in freenode is "lrossetti". I have been working as a software engineer for the last 10 years with a focus on automation and backend services (with a particular heavy usage in python). My most recent work is an open source project that enables mobile ci/cd on top of openshift and jenkins[1]. I am currently employed by Red Hat but I am joining as an individual and not on behalf of my employer. I've been using fedora for a while now (former debian and slackware user) so I started looking on how to contribute it back to fedora and that's how I found about the fedora infrastructure community. I would like to work on this issue if possible: https://pagure.io/fedora-infrastructure/issue/6505 (I am already familiar with nagios). I would like to learn more about fedora's infrastructure and its system environment with a low level flavor if possible (I began to study linux kernel modules development a few months ago). I can currently work around 20 hours a week since I would be using my free time to work on any issues - Looking forward to meet a mentor :) [1] - https://github.com/aerogear/aerogear-digger ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
