November 2019 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

The packages app has a short runway
by Randy Barlow 24 Apr '20

24 Apr '20

Greetings! The packages app is running on Fedora 30, and its dependencies are not available in Fedora 31+ as I understand it. This means it has about 7 months before we need to do something about it, or shut it off. Do we know if it can run on RHEL 7?

9 31

Pagure for EL8 (EPEL8)
by Neal Gompa 25 Mar '20

25 Mar '20

Hey all, In the interest of helping to modernize the infrastructure Fedora runs on, I'm working on introducing Pagure into EPEL8. This will hopefully allow us to upgrade our Pagure instances to use RHEL 8 instead of RHEL 7, and notably, make the transition (mostly) complete for moving all Python software Fedora runs to Python 3. I've done an early build locally to determine what's needed to make this possible. The following report from DNF indicates the missing packages that need to be added to EPEL 8 before I can introduce Pagure into EPEL8: Problem 1: conflicting requests - nothing provides python3-jenkins needed by pagure-ci-5.8-1.el8.noarch Problem 2: conflicting requests - nothing provides gitolite3 needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(binaryornot) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(celery) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(flask-wtf) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(redis) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(straight.plugin) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(wtforms) needed by pagure-5.8-1.el8.noarch - nothing provides python3.6dist(pygit2) >= 0.26.0 needed by pagure-5.8-1.el8.noarch Problem 3: conflicting requests - nothing provides python3-trololio needed by pagure-ev-5.8-1.el8.noarch One of the reasons I'd like to have this done sooner rather than later is so that we can drop Python 2 support from Pagure with version 6.0. I think it's quite reasonable to say that version 6.0 isn't going to happen until we can get our Pagure servers running on EL8 using Python 3. So now, I need some help making this happen. I already own trololio, and I'm going to make that available in EPEL 8 ASAP. Can anyone help with some of the other dependencies here? Thanks in advance, Neal -- 真実はいつも一つ！/ Always, there's only one truth!

3 7

[Fedocal, Nuancier] looking for new maintainers
by Francis Gesora 17 Mar '20

17 Mar '20

Hi, I would like to help out with the work for Nuancier. May not be available to take ownership, but willing to assist with the work. Pls advise. -- Regards, Gesora.

2 3

Infrastructure docs & apps.fp.o
by Timothée Floure 05 Feb '20

05 Feb '20

Hi, I wrote [1] to devel some time ago regarding the deprecation of the apps.fp.o index and plan to move its content to the main docs. Kevin mentionned that it could end up in the infrastructure docs and that the whole should be moved to docs.fp.o at some point. I will take a look at both since I have wanted to play with the new documentation pipeline for a while. I am not the best guy to meddle with the infrastructure doc but I might as well do something useful while playing with antora. Tell me if it's not or if I missed something. I might have something to show you at Flock if I have troubles sleeping in the train. [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… See you in Budapest, -- Timothée

5 12

F29 and older instances
by Kevin Fenzi 10 Dec '19

10 Dec '19

Greetings everyone. On 2019-11-26 fedora 29 will go end of life and no longer supported. We still have a number of things that are f29 (or older for various reasons). I'd like everyone to look this over and see if you can't move things to f31 (or at least f30) before the f29 eol. builders: I am working on this, builders right now are mostly f29, but should be all moved before the eol date I hope. openshift apps: modernpaste: fedora-27. :) But I don't think it was ever moved to openshift, so we should delete this. joystick: we should fix this up, I think jdoss was going to take it over? the-new-hotness: can we move to f31? qa-stg01.qa.fedoraproject.org: f24? can we retire? autocloud*: f27, but should die when f29 goes eol (it's only used to test atomic-host). mdadpi: f27, but it moved to openshift, can we clean up the non openshift instances and files please? modernpaste: f27. It goes eol soon, so I guess we just wait notifs-backend: f27. I don't know what to do here. We need a replacement, which we don't have. I'm afraid that upgrading will blow it up, but I guess we could try and rollback? qa-prod01: f27. can we retire? ci-cc-rdu01: f28. Can we retire soon? copr-frontend01/02.stg: f28 and I don't think we need them anymore, can I nuke them? db-qa03: f28. Can we upgrade please? osbs: f28, but I think cverna was moving it to newer? any status? f29's: aarch64-test01/02 - can be redone as f31 anytime composer.stg - should be moved to f31 db-koji01.stg - should be moved to f31 and a prod->stg sync kojipkgs01/02 - I should do these soon to f31, adding to my list. os-proxy01 - I should do this one, on my list packages03/04 - No idea here. Can we upgrade? proxy* - we need to start working on this asap. relepel01 - do we need this one anymore? resultsdb/taskotron - can qa folks upgrade these? old cloud instances: glittergallery-dev: f23, should be nuked fedora-bootstrap: f25, should be nuked waiverdb-dev: f25, still needed? commops: f27, still needed? telegram-irc: ? still needed? copr*stg: f28, can copr folks upgrade? developer: f28, still needed? libravatar: f28, should ask them to move to communishift simple-koji-ci: f29. Can we upgrade to 31? or move it to communishift? I think thats all of them. kevin

5 7

Re: Deprecating Autocloud
by Sinny Kumari 05 Dec '19

05 Dec '19

On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral <kparal(a)redhat.com> wrote: > On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari <ksinny(a)gmail.com> wrote: > >> >> >> On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin(a)scrye.com> wrote: >> >>> Or could we move f29+ all to whatever is replacing it? (taskotron?) >>> >> >> It will be nice but I am not aware of any other system in place which >> would >> replace checks performed by autocloud. >> >> (CC'ed tflink and kparal) >> Does taskotron provides capability to perform tests on Fedora cloud >> Images like booting images and other basic checks? >> > > Theoretically it is possible using nested virt. However, Taskotron is > going away as well. The replacement is Fedora CI: > https://docs.fedoraproject.org/en-US/ci/ > Thanks kamil! yeah, it doesn't make sense to move to Taskotron if it is going to be deprecated as well. > I recommend to ask in the CI list: > https://lists.fedoraproject.org/archives/list/ci%40lists.fedoraproject.org/ > > It should be possible for them to provide the infrastructure you need. > Hmm, I am not very sure if we should spend time investigating and setting up alternative to autocloud unless we have usecases for long run. Fedora Atomic Host Two Week releases ends with F29 EOL. -- http://sinny.io/

5 11

status.fedoraproject.org
by Miroslav Suchý 04 Dec '19

04 Dec '19

Hi. For long time, I plan to do something about https://status.fedoraproject.org/ I think that manual updates of this page does not reflect the capabilities of these century. My question is: do we want to go SasS way? I found https://www.statusdashboard.com/pricing which would cost us $99 per month. Or we want to maintain it in-house? The code of this specific service is open-source https://github.com/tomalessi/statusdashboard thou there are no commits for past few years. And there are some alternatives like: https://github.com/statusdashboard/statusdashboard -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

3 7

[PATCH] aws-iam-policies: fcos-upload-amis: add ability to DescribeRegions
by Dusty Mabe 03 Dec '19

03 Dec '19

Need this since we recently changed to dynamically detect regions to upload to. See https://github.com/coreos/coreos-assembler/commit/ab3cae5 --- files/aws/iam/policies/fcos-upload-amis.json | 1 + 1 file changed, 1 insertion(+) diff --git a/files/aws/iam/policies/fcos-upload-amis.json b/files/aws/iam/policies/fcos-upload-amis.json index 03999c6b0..266074522 100644 --- a/files/aws/iam/policies/fcos-upload-amis.json +++ b/files/aws/iam/policies/fcos-upload-amis.json @@ -22,6 +22,7 @@ "ec2:DescribeImageAttribute", "ec2:DescribeVolumes", "ec2:CreateSnapshot", + "ec2:DescribeRegions", "ec2:DescribeConversionTasks" ], "Resource": "*" -- 2.20.1

3 5

CPE Weekly: 2019-11-29
by Aoife Moloney 30 Nov '19

30 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: Fedora: Rawhide Gating: Bodhi was 5.1 released and is deployed in staging Robosignatory is broken in staging preventing testing much there Application Retirements Elections Elections being moved to Communishift really soon! Stay tuned! Fedocal Still no progress on kanban board last four weeks https://teams.fedoraproject.org/project/fedora-calendar/kanban Jlanda is still hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Still working on running local instance Nuancier Benson Muite is now working on OIDC authentication A PR will be created on Github to test if we can see the progress New PR from sebwoj - Porting to Fedora messaging is under review Pastebin Still on track for December 1 modernpaste shutdown GDPR and privacy centric conversations with respect to application handovers have resulted in…..more conversations needed - shock :) CentOS: The team have been testing projects migration from repospanner to locally hosted git repositores on git.dev.centos.org and come back with a migration script/plan to unblock RCM CentOS Stream Scoping meetings are still ongoing Misc Bugzilla sync script has been resolved Email inviting to review its change has been sent New changes to src.fedoraproject.org deployed: Ability to set the anitya monitoring status directly in the UI Ability to adopt orphan (and not retired) packages directly in the UI New changes to Pagure on the horizon: New API endpoint to enable/disable git hooks Ability to set dist-git in the default assignee overrides for bugzilla EPEL 8 modularity Updates can now be created in bodhi staging! We are currently testing pushes/composes We are also testing epel8-playground-modules composes Aarch64 is now racked and networked Koji New koji owner script was debugged Koji client was updated Koji was also patched for the --title option fix Configured migrations from Ansible/Jinja template https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/1 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/3 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/11 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/14 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/16 Various Resolved Issues https://pagure.io/mdapi/pull-request/91 https://github.com/fedora-infra/bodhi/pull/3782 Comments? Suggestions? Feedback? Let Us Know! Have a great weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

3 2

New Member
by Daren Hammer 28 Nov '19

28 Nov '19

Hello, My name is Daren. I am a full time web applications developer and a computer science student in my junior year. I have dabbled in python for about 2 years now and really enjoy it. I am a new fedora OS user and was looking for some ways that I could contribute. -- Thanks, Daren

4 5

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 27 Nov '19

27 Nov '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-11-28 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Problems using fedpkg
by J. Scheurich 25 Nov '19

25 Nov '19

Hi, When trying $ kinit mufti11(a)FEDORAPROJECT.ORG Password for mufti11(a)FEDORAPROJECT.ORG: $ fedpkg clone vcglib Cloning into 'vcglib'... No such repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command. review request https://bugzilla.redhat.com/show_bug.cgi?id=1677989 $ i had no success. Is something wrong ? so long MUFTI

2 1

autosign / robosignatory status
by Kevin Fenzi 25 Nov '19

25 Nov '19

Just a quick heads up (I am not really here today/this week): Last week the tpm module in autosign01 failed. robosignatory normally binds to a tpm so if any keys/files were copied off to somewhere else, they would be useless, because they require that exact machines tpm to be there. Thanks to Patrick from the iot team, things are back and working, but in a degraded state. Basically currently robosign is requiring passphrases be manually input by an admin on any restart (and then keeping that information in the kernel keyring). I'm out this week, Patrick is also out for a while, so I would urge us to not make autosign mods right now. As soon as we are back, we can evaluate if getting the tpm replaced is the way to go or other measues. Thanks, kevin

1 0

[PATCH] robosignatory.toml.j2: bump FCOS artifacts signing key to f31
by Jonathan Lebon 25 Nov '19

25 Nov '19

From: Jonathan Lebon <jonathan(a)jlebon.com> FCOS is now rebased to f31. Bump the signing key accordingly. Signed-off-by: Jonathan Lebon <jonathan(a)jlebon.com> --- roles/robosignatory/templates/robosignatory.toml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 b/roles/robosignatory/templates/robosignatory.toml.j2 index 8126648c9..520ec72ee 100644 --- a/roles/robosignatory/templates/robosignatory.toml.j2 +++ b/roles/robosignatory/templates/robosignatory.toml.j2 @@ -476,7 +476,7 @@ handlers = ["console"] [consumer_config.coreos] bucket = "fcos-builds" - key = "{{ (env == 'production')|ternary('fedora-30', 'testkey') }}" + key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}" [consumer_config.coreos.aws] access_key = "{{ fcos_builds_releng_aws_access_id }}" -- 2.23.0

2 2

OpenStack images cleanup
by Miroslav Suchý 25 Nov '19

25 Nov '19

In Openstack we have long list of images, which can be deleted. Or likely deleted. These are clearly old, and I will wipe it away on Monday unless somebody say otherwise: Fedora-Cloud-Base-28-1.1.ppc64 Fedora-Cloud-Base-28-1.1.ppc64le Fedora-Cloud-Base-28-1.1.x86_64 Fedora-Cloud-Base-Rawhide-20180423.n.0.x86_64 Fedora-Cloud-Base-28_Beta-1.3.x86_64 Fedora-Cloud-Base-28_Beta-1.1.ppc64le Fedora-Cloud-Base-28_Beta-1.1.x86_64 Fedora-Cloud-Base-28-20180320.n.0.x86_64 Fedora-Cloud-Base-28-20180310.n.0.x86_64 Fedora-Cloud-Base-27-1.6.ppc64 taskotron-f26-20171114 Fedora-Cloud-Base-27-1.6.x86_64.qcow2 Fedora-Atomic-27-1.6.ppc64le.qcow2 taskotron-f26-20171107 Fedora-Atomic-27_Beta-1.5 Fedora-Cloud-Base-27_Beta-1.5 Fedora-Cloud-Base-27-20170910.n.0.x86_64 Fedora-Cloud-Base-26-1.4.x86_64 Fedora-Cloud-Base-26-20170625.n.0.x86_64.qcow2 Fedora-Atomic-26-20170623.n.0.x86_64.qcow2 Fedora-Cloud-Base-26_Beta-1.4.ppc64le Fedora-Cloud-Base-26_Beta-1.4.x86_64 Fedora-Atomic-25-20170327.0.x86_64.qcow2 Fedora-Cloud-Base-26_Alpha-1.2.x86_64 Fedora-Cloud-Base-26_Alpha-1.1.x86_64 Fedora-Cloud-Base-Rawhide-20170315.n.0.x86_64 Fedora-Cloud-Base-26-20170308.n.0 Fedora-Atomic-25-20170228.0.x86_64.qcow2 Fedora-Cloud-Base-Rawhide-20170227.n.0.x86_64.qcow2 Fedora Cloud Base 25 Fedora-Atomic-25-20170209.2.x86_64.qcow2 Fedora-Atomic-25-20170210.0.x86_64.qcow2 Fedora-Atomic-25-20170114.0.x86_64.qcow2 Fedora-Atomic-25-20170124.1.x86_64.qcow2 Fedora base 161216 Fedora-Cloud-Base-25-1.2.ppc64le.qcow2 Fedora-Cloud-Base-25-1.2.ppc64.qcow2 Fedora-Cloud-Base-25-1.3.x86_64 Fedora-Cloud-Base-25-1.2 Fedora-Cloud-Base-25-1.1.x86_64 Fedora-Cloud-Base-25_Beta-1.2.ppc64le.qcow2 Fedora-Cloud-Base-24-1.2.ppc64le.qcow2 Fedora-Cloud-Base-24-20161106.0.i386.qcow2 Fedora-Cloud-Base-25_Beta-1.2.ppc64.qcow2 Fedora-Cloud-Base-24-1.2.ppc64.qcow2 Fedora-Atomic-24-20161025.0.x86_64.qcow2 Fedora-Atomic-25-20161023.n.0.x86_64.qcow2 Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2 Fedora-Cloud-Base-25-20161012 Fedora-Cloud-Base-25_Beta-1.1.x86_64.qcow2 Fedora-Atomic-25-20161005 Fedora-25-20161002 Fedora-Atomic-25-20160928 Fedora-Atomic-25-20160927 F24 Cloud Base release Fedora24Base Fedora24Atomic fed-cloud-24-ppc64le Fedora-Cloud-Base-24-1.2.x86_64.qcow2 Fedora-Cloud-Base-24 (Final) Fedora-Atomic-24-20160602 Fedora-Atomic-24-20160523.n.0.x86_64.qcow2 Fedora-Atomic-24-20160521 Fedora 24 Cloud base test day Fedora 24 Atomic test day Fedora-Cloud-Base-24_Alpha-7.x86_64.qcow2 Fedora-Cloud-Base-23-20160410.x86_64.qcow2 Fedora-Cloud-Atomic-23-20160409.x86_64.qcow2 Fedora-Cloud-Base-24_Alpha-7.x86_64.qcow2 Fedora-Cloud-Atomic-Vagrant-23-20160116.x86_64.vagrant-libvirt.box Fedora-Cloud-Atomic-23-20160116.x86_64.qcow2 Fedora-Cloud-Base-23-20160116.i386.qcow2 Fedora-Cloud-Base-23-20160116.x86_64.qcow2 Fedora-Cloud-Atomic-23-20160128.x86_64.qcow2 Fedora-Cloud-Base-rawhide-20160116.x86_64.qcow2 Fedora-Cloud-Base-rawhide-20160107.x86_64.qcow2 Fedora-Cloud-Atomic-23-20151224.x86_64.qcow2 Fedora-Cloud-Base-23-20151030.x86_64 Fedora-Cloud-Base-23-20151030.i386.qcow2 Fedora-Cloud-Base-23-20151030.x86_64.qcow2 Fedora-Cloud-Base-23_Beta_RC1-20150915.x86_64.qcow2 Fedora-Cloud-Base-23_Beta_TC4-20150907.i386.qcow2 F23 Alpha RC2.2 Fedora-Cloud-Base-23_Alpha-20150806.2.x86_64 Fedora-Cloud-Base-23_Alpha-20150806.1.x86_64 Raw F23 Alpha RC2 Base Image F23 Alpha RC2 Base Image Fedora-Cloud-Base-23_Alpha-20150805.x86_64 Fedora-Cloud-Base-22-20150521.x86_64 Fedora-Cloud-Atomic-22-20150521.x86_64 Fedora-Cloud-Base-22-20150521.x86_64.qcow2 Fedora-Cloud-Base-22-20150521.i386.qcow2 Fedora-Cloud-Base-22_Beta-20150415.x86_64 Fedora-Cloud-Atomic-22_Beta-20150415.x86_64 Fedora-Cloud-Base-22_Alpha-20150305.x86_64 Fedora-Cloud-Atomic-22_Alpha-20150305.x86_64 Fedora-Cloud-Base-20141203-21.i386 Fedora-Cloud-Base-20141203-21.x86_64 Fedora-x86_64-20-20140407 Fedora-x86_64-20-20131211.1 Fedora-Cloud-Base-20141203-21 fedora-cloud-64-20-20140407 Then there is a list of weird images. I will **not** delete them. If it is yours and you do not need them, please delete it: kushal-networkd1 ubuntu kevintest6 rawhide-09-8 tguha-atomic-24 RC13-raw RC13-qcow Ubuntu 14.04 kdtest -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

2 2

Help fixing the ansible-review warnings
by Clement Verna 24 Nov '19

24 Nov '19

Hi all, If you would like to help in solving some of the warnings reported by the ansible-review tool, there are a few steps on how to run the tool and get the report in this ticket https://pagure.io/fedora-infrastructure/issue/8157#comment-611372 You can send your patch to this list for review :-) Thanks Clément

3 2

CPE Weekly: 2019-11-22
by Aoife Moloney 22 Nov '19

22 Nov '19

Happy Friday everyone! Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: *Fedora:* *F31 Upgrades & Reinstallations* Updated s390x buildvm’ Updated buildvmhost-s390x-01 Updated ppc9-01 to f31 and all guests to f31, added on bug about qemu in f31 on ppc64le not being able to do pseries-4.1 guests (the default), switched to pseries-4.0. https://bugzilla.redhat.com/show_bug.cgi?id=1769600 Re-installed buildvm-aarch64-01/02/03 and buildvm-armv7-01/02/03 with f31 and worked though issues with composes on them. Rawhide Gating: <https://github.com/fedora-infra/bodhi/projects/3> Bodhi 5.0 has been deployed for a week now and we are getting some feedback on the new UI We hope to incorporate some of this feedback in the 5.1 release 5.1 will include a fix needed by the CI pipeline Ci pipeline on fedora-messaging JMS plugin has been updated That broke datagrepper: unix timestamp are in seconds, not milliseconds and postgresql doesn’t like the year 51850 Fedora-messaging client on resultsdb had broke Open ticket is for monitoring: https://pagure.io/fedora-infrastructure/issue/8392 repoSpanner <https://github.com/repoSpanner/repoSpanner> 83x performance patch submitted as a pull request and is awaiting review. Once the 83x patch is merged, we hope that it will be possible to make a release/deployment. It is possible that it will still be too slow so our next idea for improvement involves changing the API that nodes use to synchronize objects with each other. *Application Retirements* Elections Blocking issue was fixed https://pagure.io/fedora-infrastructure/issue/8253 Bcotton confirmed the fix is now in place - thanks Ben! Fedocal No progress on kanban board last four weeks https://teams.fedoraproject.org/project/fedora-calendar/kanban Jlanda is still hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Working on running local instance Nuancier Benson Muite is now working on OIDC authentication By creating a PR on Github, we should be able to see the progress New PR from sebwoj - Porting to Fedora messaging Pastebin Magazine article posted after getting bounced between commblog and magazine a few times. On track for December 1 modernpaste shutdown GDPR and privacy centric conversations are ongoing with respect to application handovers *CentOS:* The team have been testing migrating away from Repospanner Wrote a PoC migration script (taking care also of requests/tickets/forks repositories) RCM confirmed that it works Next step is testing on https://git.stg.centos.org and we hope to have an ETA on a migration time soon *CentOS Stream* Scoping meetings are ongoing *Misc* Introduction of a dedicated team for community issues: The CPE Team have created a dedicated team to work through a backlog of issues that are affecting the community. The team has a 6 week plan ahead of them this side of the New Year Check out our Kanban board: https://teams.fedoraproject.org/project/community-fire-team/kanban Our first priority task is to fix the bugzilla sync script Got its own upstream project: https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/ We will be working on these items secondary to other work we have but will try to get some of these issues resolved soon! EPEL 8 modularity: Modules are building in stg koji Tagging is working Bodhi testing is blocked on https://github.com/fedora-infra/bodhi/issues/3779 Nest steps are to test epel8 playground module composing Comments? Suggestions? Feedback? Let Us Know! Have a great weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Re: [Fedora 31 / FAS] Error connecting to my FAS from GNOME "Online Accounts"
by Chris Rainey 22 Nov '19

22 Nov '19

WORKED! Changing my password did the trick. Thanks, Kevin. Now ... what have I gained by this? It has a single toggle switch called: "Use for Network Resources"

4 5

OpenShift-apps playbooks in the master.yml playbook
by Clement Verna 21 Nov '19

21 Nov '19

Hey all, I have just disabled the openshift-apps playbooks from running in the master playbook run (see https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/master.yml… ). The reason behind is that the openshift-apps playbook are written to trigger a new build and a new deployment of the application at each run, this means that every time the master.yml playbook is run we build a version of the application and deploy it. Since a few of our applications are using source-to-image to build the container directly from git it means that a master.yml run can deploy new code into production without the maintainer of that application being aware of it. I wanted to raise awareness of this problem and ask the following questions. Do we need to have the openshift-apps in the master.yml ? If yes how do we prevent the run from deploying unwanted changes in production ? Thanks Clément

5 6

Meeting agenda for 2019-11-21
by Stephen John Smoogen 20 Nov '19

20 Nov '19

The infrastructure team will be having its weekly meeting tomorrow, 2019-11-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a document at https://board.net/p/fedora-infra 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. ## Introduction 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 (2019-11-14) #meetingname infrastructure #topic aloha #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs ``` ### Determine who the next chair is #topic Next chair #info magic eight ball says: 2019-11-21: pingou 2019-11-28 - holiday, NO MEETING! 2019-12-05 -smooge 2019-12-12 -?? 2019-12-19 -?? 2019-12-26 - NO MEETING 2020-01-02 - NO MEETING 2020-01-09 - ?? ### Let new people say hello ``` #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted ``` ### 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 ``` ### 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 /suor 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 Oncall #info https://fedoraproject.org/wiki/Infrastructure/Oncall #info pingou is on call 2019-11-14->2019-11-21 #info kevin is on call 2019-11-21->2019-11-28 #info smooge is on call 2019-11-28->2019-12-05 ## .oncalltakeeu .oncalltakeus #info Summary of last week: (from current oncall ) #info #topic Monitoring discussion #info https://nagios.fedoraproject.org/nagios #info Go over existing out items and fix #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket #infohttps://pagure.io/fedora-infrastructure/issue/8397 #info Fedora CoreOS Team requests #link https://hackmd.io/5uB7hOJKSjGUt65iLgPnbA#Existing-requests-for-Fedora-Infra #topic backlog discussion #info go over our backlog and discuss and determine priority #link https://pagure.io/fedora-infrastructure/issue/8178 #info topic: provision new aarch64 builders #link https://pagure.io/fedora-infrastructure/issue/8157 #info topic: ansible: enable ansible-report as a hook ``` Go thru each ticket one by one #topic Community Fires Team ### Put all topics for discussion under here Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. ### 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 i/nfo 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.) ``` #info ``` ### Meeting end stuff ``` #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 20 Nov '19

20 Nov '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-11-21 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

New mirrorlist server implementation
by Adrian Reber 19 Nov '19

19 Nov '19

Fedora's complete MirrorManager setup is still running on Python2. The code has been ported to Python3 probably over two years ago but we have not switched yet. One of the reasons is that the backend is running on RHEL7 which means we are not in a hurry to deploy the Python3 version. The mirrorlist server which is answering the actual dnf/yum queries for a mirrorlist/metalink is, however, running in a Fedora 29 container. This container also still uses Python2 and it actually cannot use the Python3 version. One of MirrorManager's design points is that the mirrorlist servers, which are answering around 27 000 000 requests per day, are not directly accessing the database. The backend creates a snapshot of the relevant data (113MB) and the mirrorlist servers are using this snapshot to answer client requests. This data exchange is based on Python's pickle format and that does not seem to work with Python3 if it is generated using Python2. Having used protobuf before, I added code to also export the data for the mirrorlist servers based on protobuf. The good news with protobuf is, that the resulting file is only 66MB instead of 113MB. The bad news is, that loading it from Python requires 3.5 times the amount of memory during runtime (3.5GB instead of 1GB). In addition to the data exchange problems between backend and mirrorlist servers the architecture of the mirrorlist server does not really make sense today. 12 years ago it made a lot of sense as it could be easily integrated into httpd and it could be easily reloaded without stopping the service. Today the mirrorlist server and httpd is all part of a container which is then behind haproxy. So there is a lot of infrastructure in the container which is not really useful. To get rid of the pickle format and to have a simpler architecture I reimplemented the mirrorlist-server in Rust. This was brought up some time ago on a ticket and with the protobuf problems I was seeing in Python it made sense to try it out. My code currently can be found at https://github.com/adrianreber/mirrorlist-server and so far the results from the new mirrorlist server are the same as from the Python based mirrorlist server. It requires less than 700MB instead of the 1GB in Python with production based data and seems really fast. I have set up a test instance with the mirror data from Sunday at: https://lisas.de/metalink?repo=updates-testing-f31&arch=x86_64 https://lisas.de/mirrorlist?repo=updates-testing-f31&arch=x86_64 The instance is based on the container I pushed to quay.io: $ podman run quay.io/adrianreber/mirrorlist-server:latest -h With this change the mirrorlist server would also finally switch to geoip2. The currently running mirrorlist server still uses the legacy geoip database. After the Fedora 31 freeze I would like to introduce this new mirrorlist server implementation on the proxies. I already verified that I can run this mirrorlist container rootless. This new container can be a drop-in replacement for the current container and no infrastructure around it needs to be changed. The main changes to get it into production is to change mirrorlist1.service and mirrorlist2.service to include a line "User=mirrormanager" and replace the current container name with new container. Adrian

4 13

Wikiedit FAS group and Fedora Join new workflow
by alciregi＠gmail.com 19 Nov '19

19 Nov '19

Hello! As you can read here[0], the Fedora Join SIG is experimenting a new way to help people become part of the community. This workflow includes also a temporary FAS group if required or asked by the newcomer. Since this overlaps with the current "wikiedit" system, we were wondering if it'd make sense to retire it and send newcomers to the Fedora Join channels instead where they can speak to community members and take their time learning/exploring the community and it's projects. It'll be one less responsibility for the infra team, and it'll help us channel folks to the new workflow. Please let us know if this sounds OK and we'll edit the wiki page here accordingly [1]. We'll send out more posts announcing the new workflow to the community this week. If you have the cycles, please hang out in the Fedora Join channels[2]. [0] : https://communityblog.fedoraproject.org/fedora-join-is-trying-a-new-people-… [1] https://fedoraproject.org/wiki/Help:Editing#Gaining_Edit_Access [2] https://fedoraproject.org/wiki/SIGs/Join?rd=Fedora_Join_SIG Thanks, A.

5 23

Problems with vcglib
by J. Scheurich 18 Nov '19

18 Nov '19

Hi, There are problems with the vcglib package vcglib review request: https://bugzilla.redhat.com/show_bug.cgi?id=1677989 $ kinit mufti11(a)FEDORAPROJECT.ORG Password for mufti11(a)FEDORAPROJECT.ORG: $ fedpkg clone vcglib Cloning into 'vcglib'... No such repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command. $ Did i something wrong ? so long MUFTI

1 0

patches to review to prepare our ansible scripts for fedora-messaging
by karsten＠fedoraproject.org 18 Nov '19

18 Nov '19

Hello, There is work in progress to migrate our applications from the current message bus 'fedmsg' to the AMPG based 'fedora-messaging'. Attached are a couple of patches that prepare our ansible scripts for this. Please review those patches and comment, thanks ! Karsten

5 7

Greenwave release
by Giulia Naponiello 18 Nov '19

18 Nov '19

Hello, I'm going to perform a Greenwave release in a bit. I'll send an email again with the release notes when I'm done with it. Thank you Cheers Giulia

1 1

Fwd: How to approve a review request ?
by J. Scheurich 16 Nov '19

16 Nov '19

Hi, >> I want to approve the review request of vimvi-qt, but this is my first >> offical review 8-( > You need to set fedora-review+ flag. Click on "Show advanced fields" near > the top of the bug, and flags should be visible in a drop-down menu on > the right. | I still don't find it 8-( http://wdune.ourproject.org/examples/vimvi.png | Mufti, it's weird that your screenshot shows that you can set the | fedora-review flag to ? but not to +. Maybe file a ticket with | infra---possibly Bugzilla didn't sync with FAS properly or something? Can you help me ? so long MUFTI

2 1

CPE Weekly: 2019-11-16
by Aoife Moloney 16 Nov '19

16 Nov '19

Hi Everyone! Travelling yesterday saw a delay in sending this weeks CPE email blast, but nevertheless, here it is! Hope everyone has been having a great weekend and if you have any comments or feedback, please let me know- it is always welcome :) Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: Fedora: Rawhide Gating: Bodhi 5.0 has been deployed in production We received some feedback about the changes in the UI and are looking at how we can address them. We are working on documenting on how packagers will use Bodhi for multi-builds updates in rawhide: https://github.com/fedora-infra/bodhi/issues/2322 https://fedoraproject.org/w/index.php?title=User:Nphilipp/Package_update_HO… A 5.1 release is scheduled, likely some time next week, to address some of the issues encountered and fixed in the 5.0 release. repoSpanner Our team came across some test reliability issues last week & these are impeding progress on the 83x patch. Some more debugging/discussions around RCMs pushes that seem to be either very slow or hanging but the team is looking into some solutions Some progress was also made on the 83x patch however and we managed to fix one unreliable test. Application Retirements Elections Blocking issue was fixed (https://pagure.io/fedora-infrastructure/issue/8253) Fedocal jlanda hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Nuancier Benson Muite is now working on OIDC authentication Pastebin An article will be posted to Magazine instead - keep an eye out! GDPR policies are still being looked into so stay tuned for updates soon. This unfortunately takes some time given the legal perspective needed! CentOS: The team is busy working on 8.1 Comps were produced and in git repo for next compose (pungi) Transmodrify tool rewritten to match the mbs/rpm needs Analyzing what RH hasn’t pushed and so that is needed Builds started and are being working on for x86_64, ppc64le, aarch64 and armhfp architectures https://koji.mbox.centos.org/koji/index https://koji.armhfp-mbox.centos.org/koji/index Infrastructure : Dealing with hardware issues on storage box , so opening tickets with vendor and internal IT to play MITM and try to get this solved Dealing with RCM having still issues to push to git.centos.org for some identified packages (reproducible) so now waiting on Repospanner maintainer to come with a fix and an ETA for new release that would fix it Trying to provision some EC2 instances and working with Fedora to get proper access to be able to have proper AWS access for CentOS (also for S3) Working on various PR for cbs-content-control and/or issues with mash on https://cbs.centos.org (now resolved) Misc EPEL 8 modularity EPEL8 module builds are working in staging & composes should be closed There are now tags added to staging in koji Bodhi configs have been updated Pungi configs for epel8-playground are updated Bug about zchunk update for EPEL-7 was fixed https://github.com/fedora-infra/bodhi/pull/3692 Fedora Docs Multiple small PRs were merged where people were being sent to Fedora docs after F31 came out & below are all fixed: https://pagure.io/fedora-docs/system-administrators-guide/issue/40 https://pagure.io/fedora-docs/system-administrators-guide/issue/39 https://pagure.io/fedora-docs/system-administrators-guide/issue/35 https://pagure.io/fedora-docs/install-guide/issue/33 https://pagure.io/fedora-docs/system-administrators-guide/issue/25 https://pagure.io/fedora-docs/system-administrators-guide/issue/23 https://pagure.io/fedora-docs/quick-docs/issue/155 Kindest regards, Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 13 Nov '19

13 Nov '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-11-14 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Mirrorlist server bug report - behaviour change requested
by Adrian Reber 12 Nov '19

12 Nov '19

I was contacted by someone working on openSUSE's Open Build System (OBS). They are using download.fedoraproject.org and some layout change concerning noarch breaks their workflow. The problem is, that the redirect service of download.fedoraproject.org based on the mirrorlist servers returns a 200 and 'error: invalid path'. See https://github.com/adrianreber/mirrorlist-server/issues/1 So this problem is unrelated to the new mirrorlist implementation. The old code did the same. Error message and a 200 return code. I think changing the return code to 404 is the correct thing to do, but I wanted to check if anybody sees any problems with this behaviour change of the mirrorlist server. Adrian

3 3

Another patch that makes nagios send the messages with fedora-messaging
by Karsten Hopp 12 Nov '19

12 Nov '19

Hi all, Now that https://pagure.io/releng/pull-request/8940 got merged we can migrate nagios from fedmsg to fedora-messaging. The attached patches are for switching nagios to fedora-messaging, please review and merge if they look sane to you. Thanks, Karsten

2 4

Meeting Agenda Item: Introduction Kevin Sandy
by Kevin Sandy 12 Nov '19

12 Nov '19

Hi all! I’m very interested in getting involved in the Infrastructure group. I’ve been holding off on this for over a year, waiting to have “more time”, but figured I may as well jump in and start small, maybe 3-5 hours per week? My IRC nick is ks3. I’ve been using Linux since around 1997, and professionally since 1998. Most of that has been RPM based distributions, starting with SuSE but fairly quickly moving to Red Hat, then RHEL and CentOS, and even Oracle Linux. At home, I’m using Fedora on my servers, including a cluster of Intel NUCs that host KVM machines on GlusterFS. At $work, I head up a team of Linux admins responsible for around 800 servers, including some smallish HPC environments. I *had* the RHCE certification until it expired earlier this year. I’m scheduled to take the RHEL8 exams in April 2020. I have a good amount of scripting experience; lately it’s mostly been bash, with Python where SOAP calls or other harder-to-do in bash things were needed. I’m also fairly fluent with Perl. I’m also familiar with Puppet (and using Vagrant to test Puppet code, and Git to manage the Puppet modules), and to a smaller degree Ansible. In addition to getting involved and giving back to the project (I also work at a non-profit, so that’s a bit of a theme...) I’m excited about learning how a different environment works and the tech that goes along with it. My main interests at the moment are probably Python and automation. I see that the Getting Started page mentions a special interest in people with web application skills; that’s definitely not my strong suit, but it is also an interest. I’ve looked through a few of the “Easyfix” issues, and a few do look interesting. But at a few hours per week they all look like they’d take a month or more to complete, so I don’t really have a good idea of whether those are a good starting point or not. I’m definitely open to suggestions on this. -- kevin

2 1

Meeting Agenda Item: Introduction Ekta Arora
by Ekta arora 08 Nov '19

08 Nov '19

Sir/Mam, I am a undergrad pursuing my B.Tech degree in Computer Science. I have worked with python and have explored its framework Django , Flask. I would like to contribute to Fedora.Following are my skills and experiences. Programming languages : Python,C Frameworks and techs: Django,Flask, NodeJs , Mysql , MongoDb Irc handle : ekta__3501 I found following issues really interesting and would love to begin with them. #186 Run worldcloudbot on @fedoracommunity Twitter account #166 Generate a general email introduction template for the onboarding process Thank You Ekta Arora ektaarora3501(a)gmail.com

2 1

CPE Weekly: 2019-11-08
by Aoife Moloney 08 Nov '19

08 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. For increased communication between our communities, we have created #redhat-cpe on Freenode! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: Fedora: Rawhide Gating: We are working towards deployment of Bodhi 5.0 to production Testing & Staging are both going fine Synching with centos.ci.org New ci-resultsdb-listener due in production this week More work is going into docs for rawhide gating repoSpanner Discovered a new bottleneck that appears due to network latency that wasn’t present in local testing. We are also further analysing core dumps for unexplained hanging of the app Tested pushing the Ansible repo to a local repospanner cluster to see how it performed with new 83x patch. It pushed in 4 minutes. Network bottleneck is prenventing real numbers. We are also working on improving testing. Additional developer docblocks landed Application Retirements Elections Blocking issue was fixed (https://pagure.io/fedora-infrastructure/issue/8253) Fedocal jlanda hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Nuancier Benson Muite is now working on OIDC authentication We are emailing him to check the progress and if he needs any help Fpaste Updated fpaste CLI appears to have landed in EPEL. Writing a commblog about it Sunset date: 1 December 2019 Badges GDPR query under investigation CentOS: RHEL 8.1 announced Tuesday, team are busy tackling this Workaround to help automatically restart repospanner 7.8 beta push has 3 packages left Misc Some of the team attended the OpenAlt conference in Brno. Watch out for blogs about our experience! The team are exploring smaller end of year initiatives, and we would welcome any thoughts or feedback. Comments? Suggestions? Feedback? Let Us Know! Kind regards & have a great weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

is download.fedoraproject.org repo down?
by Satish Patel 06 Nov '19

06 Nov '19

I am getting this error during my ansible build fatal: [ostack-eng-infra-1]: FAILED! => {"attempts": 5, "changed": false, "msg": "Failure talking to yum: failure: repodata/fe9a02c498455711d7edb16080658f385ac41ced5f23de26bb308f599158ae3b-primary.sqlite.bz2 from epel-lxc_hosts: [Errno 256] No more mirrors to try.\nhttp://download.fedoraproject.org/pub/epel/7/x86_64/repodata/fe9a02c4…: [Errno 14] HTTP Error 404 - Not Found"}

2 1

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 06 Nov '19

06 Nov '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-11-07 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Upgrading ODCS prod (hopefully) next week.
by Jan Kaluža 04 Nov '19

04 Nov '19

Hi, last few weeks, I was working on ODCS upgrade in staging. This is done now and I would like to do the same upgrade in prod. The ODCS running in Fedora prod infra is quite old and lot of things changed in the upstream. Therefore this upgrade is somehow big and I presume the service will not be running for few hours. The key changes in ODCS infrastructure will be: - ODCS prod VMs will be redeployed to upgrade to Fedora 30. - ODCS will stop using fedmsg-hub and starts using fedora-messaging. - ODCS will start using Celery over fedora-infrastructure's RabbitMQ for job planning. - Upgrade to latest ODCS and Pungi will be done. All of that is already done and tested on staging infrastructure. The service is currently used mainly by OSBS to build flatpak images and therefore I presume the flatpak builds will fail during this upgrade. I will coordinate the upgrade with Clement Verna (OSBS), Owen Taylor (flatpak) and Mikolaj Izdebski (fedora infra). In case you think you should be included in discussions related to this upgrade, please respond here :). Regards, Jan Kaluza

2 1

What is the purpose of my "...@fedoraproject.org" email address?
by Chris Rainey 02 Nov '19

02 Nov '19

I just noticed that my FAS account has an automatic(?) @fedoraproject.org email address. Is there an "Inbox" for this or is it just an alias to my "Primary" account address for privacy, etc.? Thanks!

6 15

FBR bodhi-pungi: only run multi-arch SB on f31+
by Dusty Mabe 01 Nov '19

01 Nov '19

[PATCH] bodhi-pungi: only run multi-arch SB on f31+

4 11

[Fedora 31 / FAS] Error connecting to my FAS from GNOME "Online Accounts"
by Chris Rainey 01 Nov '19

01 Nov '19

Please see attached screenshot for exact error: "Error connecting to Fedora: Preauthentication failed" Thanks!

2 3

CPE Weekly: 2019-11-01
by Aoife Moloney 01 Nov '19

01 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. For increased communication between our communities, we have created #redhat-cpe on Freenode! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: Fedora: F31 was released on Tuesday 29th October! https://fedoramagazine.org/announcing-fedora-31/ F31 documentation was also released. Fedora 31 websites had a harder release, but it is clearer to parties involved the amount of work which was done in the background every release. Fedora Infrastructure freeze ended and so changes to infrastructure can occur until the F32 Beta in about 3 months. Congratulations to everyone in the Community whom were involved with the release, onwards to F32 :) Rawhide Gating: A call to arms email has been sent asking for testers for multi build https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Single build workflow is working again and is aligned with multi-build workflows also https://bodhi.stg.fedoraproject.org/updates/FEDORA-2019-3d6e95211e Update for the multi-build workflow needs to be created with autotime on, otherwise the update will not get pushed https://bodhi.stg.fedoraproject.org/updates/FEDORA-2019-90b8bce568 Overview page of the remaining blockers and dependencies organized at: https://hackmd.io/Gbuu9JOPR--Y2yNCBEYI5A?view Ci.centos.org is still not using fedora-messaging Ci-resultsdb-listener with fedora-messaging and support for the new messages format is not deployed in production yet repoSpanner Developed another experimental patch that got us an ~83x speed up. Got 122% performance patch merged. Worked with smooge to get a repoSpanner cluster deployed on realistic cross-datacenter hardware. repoSpanner is still extremely slow when all three DCs are used. Est. 58 minutes to push Bodhi into it, even with the 83x speedup patch. The team is investigating a solution. Application Retirements Elections: Blocking issue was fixed https://pagure.io/fedora-infrastructure/issue/8253 Fedocal : jlanda started to work on communishift port https://pagure.io/fedora-infrastructure/issue/8274 Nuancier: Benson Muite is now working on OIDC authentication - Thank you Benson! Fed-msg: fedmsg-logger equivalent for fedora-messaging https://pagure.io/releng/pull-request/8940 CentOS: Cbs.centos.org migration Started planning for how to make community builds available with EL8 Deploying a new koji host that will be used for cbs.centos.org migration Migrated following services from puppet configuration management: https://feeds.centos.org (now under ansible, covering CentOS Stream/8) https://planet.centos.org (now under ansible) Continuing conversion of further puppet roles to ansible CentOS CI Added CentOS 8 and CentOS Stream in cico Updated python-cicoclient to support CentOS 8 and CentOS Stream Comments? Suggestions? Feedback? Let Us Know! Have a lovely weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

ansible-report git hook design
by Clement Verna 01 Nov '19

01 Nov '19

Hi all, Today jlanda, austinpowered and mizdebsk discussed about ticket https://pagure.io/fedora-infrastructure/issue/8157 in #fedora-admin and came up with a few questions on how to implement that solution that I think would be nice to share with the wider group. There are basically 2 possibility : 1 - We run ansible-report as a pre-commit hook This means that ansible-report will be run locally before a contributor commit a change. This is not ideal since our contributor are running all kind systems (rhel, fedora, windows ?) so having something that work well for everyone will not be simple. Also this forces our contributors to install ansible-report locally. 2 - We run ansible-report as a pre-receive hook This means that ansible-report is run on batcave01, but we cannot run ansible-report just on a commit, we need to run the tool against the full repository every time. That involve making a clone of the repo applying the changes in the incoming commit, then run ansible-report on that repository. This has also a few disadvantages, first we first need to clear all the errors reported by ansible-report in our repo before we enable the hook otherwise all commits will be rejected. It will also slows down every pushes (time to clone, apply patch, run the tool). Do people have other ideas ? Is this change worth the trouble ? Thanks

6 9

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2019