infrastructure October 2019

infrastructure@lists.fedoraproject.org

42 participants
59 discussions

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

Fedora 31 Final Freeze now in effect!
by Kevin Fenzi 30 Oct '19

30 Oct '19

Greetings. we are now in the infrastructure freeze leading up to the Fedora 31 Final release. This is a final release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2019-10-22 (or later if release slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

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

30 Oct '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-10-31 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

CPE Weekly Update: 2019-10-25
by Aoife Moloney 29 Oct '19

29 Oct '19

Good Morning/Afternoon/Evening Everyone, Welcome to week four of the CPE Weekly Updates! *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. * *FedoraRawhide Gating: <https://github.com/fedora-infra/bodhi/projects/3>New Bodhi 5.0 release is now in staging- Bodhi staging container being moved from rpms to source to allow for faster releaseStaging- Openshift issue blocking builds now resolved, can be viewed here ->https://pagure.io/fedora-infrastructure/issue/8300 <https://pagure.io/fedora-infrastructure/issue/8300>- Both Koji & fedpckg/rpckg all working well- Looking into a way to trigger bodhi updates rather than builds in the CI pipelineTracked here -> https://pagure.io/fedora-ci/general/issue/70 <https://pagure.io/fedora-ci/general/issue/70>Fedora Messaging:- Ci-resultsdb-listener -> 1.0 release is out and running in staging (w/ support for fedora-messaging as well as the new message format)- Results with the new format not fully showing on bodhi in staging yet so the team is investigating!- Bugzilla2fedmsg was down this week, the team are working to get it back online, if not already done so at the time of this email :)- el8 is installed on aarch64/emag- Documentation created on how packagers can use bodhi to manage Rawhide, including sidetags can be viewed here -> https://github.com/fedora-infra/bodhi/issues/2322 <https://github.com/fedora-infra/bodhi/issues/2322>- Documentation reviewed and updates made here ->https://github.com/CentOS/docs-installation-guide/pull/9 <https://github.com/CentOS/docs-installation-guide/pull/9>- Changelog entry to update notes for automatic updates is added here -> <http://goog_1278793625/>https://github.com/fedora-infra/bodhi/pull/3548 <https://github.com/fedora-infra/bodhi/pull/3548> <https://github.com/repoSpanner/repoSpanner>repoSpanner: <https://github.com/repoSpanner/repoSpanner>- Performance prototype is now PR: https://github.com/repoSpanner/repoSpanner/pull/98 <https://github.com/repoSpanner/repoSpanner/pull/98>- Performance now boosted by 122%!!- Now looking towards profiling on production-like hardware - stay tuned!CentOSMirrors- Switched https://mirror-status.centos.org <https://mirror-status.centos.org/> to centos 7 node (ansible managed) CentOS CI- Investigating an issue with provisioning CentOS 6 in duffyw - https://lists.centos.org/pipermail/ci-users/2019-October/000971.html <https://lists.centos.org/pipermail/ci-users/2019-October/000971.html>Migrations:- phpbb version is also updgraded on www.centos.org/forums <http://www.centos.org/forums> and fr.centos.org/forums <http://fr.centos.org/forums> - blog.centos.org <http://blog.centos.org/> is now moved to a new host/ansible roleCommunity Handover Applications:- Elections: Still blocked - please help!PostgreSQL database is missing in application cataloguehttps://pagure.io/fedora-infrastructure/issue/8253 <https://pagure.io/fedora-infrastructure/issue/8253>- Fedocal: Maintainer found and the team are working through the handover- Nuancier: New maintainer is currently working on OIDC authentication so keep an eye out for an update next week!- Pastebin: Fpaste client has been updated and we are now working on redirecting fpaste.org <http://fpaste.org/> and paste.fpo to the centos pastebinMaintainers Needed:- Tahrir: If you would like to volunteer to maintain this app, please let us know by 2019-12-31!- Tahrir-api: If you would like to volunteer to maintain this app, please let us know by 2019-12-31!Retiring Applications:- Kitchen: Retiring on 2019-10-31- Keys: Retiring on 2019-10-31Comments? Suggestions? Feedback? Let Us Know!And have a great weekend!Kindest regards,Aoife*-- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com/> Communications House Cork Road Waterford <https://www.redhat.com/> -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

3 2

FBR: Change IoT devel/ keys to f31
by Patrick Uiterwijk 28 Oct '19

28 Oct '19

Hi, Can I get +1s for the following patch? Regards, Patrick From e0a17965cfa9b6e25171821a3fa4964d8d99963a Mon Sep 17 00:00:00 2001 From: Patrick Uiterwijk <patrick(a)puiterwijk.org> Date: Mon, 28 Oct 2019 14:16:41 +0100 Subject: [PATCH] Update IoT devel/ keys to f31 Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org> --- roles/robosignatory/templates/robosignatory.toml.j2 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 b/roles/robosignatory/templates/robosignatory.toml.j2 index bff118e3f..85bb0bfe7 100644 --- a/roles/robosignatory/templates/robosignatory.toml.j2 +++ b/roles/robosignatory/templates/robosignatory.toml.j2 @@ -329,13 +329,13 @@ handlers = ["console"] [consumer_config.ostree_refs."fedora/stable/x86_64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" - key = "{{ (env == 'production')|ternary('fedora-iot-2019', 'testkey') }}" + key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" - key = "{{ (env == 'production')|ternary('fedora-iot-2019', 'testkey') }}" + key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/armhfp/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" - key = "{{ (env == 'production')|ternary('fedora-iot-2019', 'testkey') }}" + key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}" [consumer_config.ostree_refs."fedora/31/x86_64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" -- 2.21.0 (Apple Git-122)

3 2

Please review: MBS platform definition for EPEL8
by Merlin Mathesius 24 Oct '19

24 Oct '19

Please review the attached patch to add a new file to https://infrastructure.fedoraproject.org/cgit/ansible.git/. This patch provides a new platform:el8 default module definition so fm-orchestrator knows about EPEL8. Some review and discussion has already taken place at https://pagure.io/Fedora-Infra/ansible/pull-request/40. The contents are based on the current Fedora platform module definitions plus the rpm profiles from the package groups found in https://kojipkgs.fedoraproject.org/repos/epel8-infra-build/latest/groups/co… . Note: I'm starting with just this platform:el8 module definition for staging MBS. Once we're happy with it, it can be replicated for platform:el8-playground. Then, when ready, they can be copied to production. Regards, Merlin

6 14

FBR: updates Silverblue in bodhi pungi config
by Dusty Mabe 24 Oct '19

24 Oct '19

[PATCH 1/2] bodhi-pungi: F32 will be the next "branched" [PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue Now that F31 is a go we need to do a few things. One of them is enabling other architectures, which was done in rawhide and f31. This propagates it into bodhi.

3 10

FBR: Update releases.json to make f31 active and no retirement
by Mohan Boddu 24 Oct '19

24 Oct '19

Hi, Another FBR to update releases.json to make sure retirement is not allowed diff --git a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections index aac977e..9e0cbf2 100644 --- a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json +++ b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json @@ -12,14 +12,14 @@ "version": "devel" }, { - "allow_retire": true, + "allow_retire": false, "branchname": "f31", "date_created": "2014-05-14 12:36:15", "date_updated": "2018-08-14 17:07:23", "dist_tag": ".fc31", "koji_name": "f31", "name": "Fedora", - "status": "Under Development", + "status": "Active", "version": "31" }, {

3 2

FBR new-updates-sync: sync multiarch silverblue ostree content
by Dusty Mabe 24 Oct '19

24 Oct '19

[PATCH] new-updates-sync: sync multiarch silverblue ostree content

3 4

FBR: Update koji-sidetag-plugin on Koji hub
by Mikolaj Izdebski 24 Oct '19

24 Oct '19

In order to fix issue 8322 [1] python2-koji-sidetag-plugin-hub needs to be updated. This would be done with the following commands: $ koji move epel7-infra-stg epel7-infra koji-sidetag-plugin-0.1-2.el7.infra [root@batcave01]# ansible koji -m package -a 'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes update_only=yes' [root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded' [1] https://pagure.io/fedora-infrastructure/issue/8322

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure October 2019