infrastructure March 2019

infrastructure@lists.fedoraproject.org

40 participants
97 discussions

dist-git 1.10 release
by Michal Novotny 12 Mar '19

12 Mar '19

Hello, I've released a new version of dist-git 1.10 (https://github.com/release-engineering/dist-git). The main thing in there is python2/3 compatibility. When deployed in Fedora, it uses python3 now. I've also fixed a small bug in post-receive hook when there were no hooks to run in post-receive-chained.d and did a few fixes in tests. You can see the updates here: https://bodhi.fedoraproject.org/updates/?packages=dist-git clime

1 0

Proposal to increase number of concurrent MBS builds
by Mikolaj Izdebski 11 Mar '19

11 Mar '19

I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to value 100 after beta freeze is over. The above MBS setting controls how many parallel component builds MBS can run at the same time. Current value is only 20. That value was defined 3 years ago, in March 2017 when there were much fewer modules in Fedora. Our Koji has capacity to run many more builds. Currently we have 158 Koji builders in default channel that are able to run RPM builds. Their total capacity is 566. Therefore it should be safe to increase MBS NUM_CONCURRENT_BUILDS to at least 100. Especially since Koji builds submitted by MBS have lower priority than default for non-modular component builds submitted by packagers, so packager-submitted builds will take precedence over builds submitted by MBS. -- Mikolaj Izdebski

3 6

[PATCH] Add zchunk support to updates and updates-testing repositories
by Jonathan Dieter 11 Mar '19

11 Mar '19

This adds zchunk support for the updates and updates-testing repositories for both rpms and modularity Signed-off-by: Jonathan Dieter <jdieter(a)gmail.com> --- roles/bodhi2/backend/templates/pungi.module.conf.j2 | 3 +++ roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 3 +++ 2 files changed, 6 insertions(+) diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2 index bb021eb13..7dad35403 100644 --- a/roles/bodhi2/backend/templates/pungi.module.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.module.conf.j2 @@ -59,6 +59,9 @@ greedy_method = 'build' createrepo_c = True createrepo_checksum = 'sha256' createrepo_deltas = False +[% if release.version_int >= 30 %] +createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]'] +[% endif %] #jigdo create_jigdo = False diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 8d9e9a3f2..020736aee 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -66,6 +66,9 @@ createrepo_deltas = [ ('^Everything$', {'*': True}) ] createrepo_database = True +[% if release.version_int >= 30 %] +createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]'] +[% endif %] # CHECKSUMS media_checksums = ['sha256'] -- 2.20.1

3 2

[FBR] Adding f30 key to bodhi modular pungi config
by Mohan Boddu 11 Mar '19

11 Mar '19

This patch will add fedora-30 key to bodhi modular pungi config. diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2 index bb021eb..43c6a7e 100644 --- a/roles/bodhi2/backend/templates/pungi.module.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.module.conf.j2 @@ -14,6 +14,8 @@ sigkeys = [ '9db62fb1', [% elif release.version_int == 29 %] '429476b4', +[% elif release.version_int == 30 %] + 'cfc659b9', [% endif %] {% if env == "staging" %} None Please +1 this patch to resume the failed f30-modular-updates-testing. Thanks.

3 3

FBR: Rebuild Bodhi frontend containers
by Randy Barlow 11 Mar '19

11 Mar '19

Greetings! The Bodhi frontend container was not rebuilt when the Fedora 30 configurations were added to production.ini. This means that the frontend is not aware of the policy of 3 days to stable, while the backend is aware. This means that the backend is adding comments to updates to tell packagers they can push their packages, but the frontend is not allowing them to push the packages. To fix this, I will run this command: $ sudo rbac-playbook openshift-apps/bodhi.yml I will also send a patch to the releng SOP which doesn't explicitly mention this step - it really should just link to the Bodhi SOP where this is mentioned.

3 3

How do we turn zchunk on for updates-testing for F30?
by Jonathan Dieter 10 Mar '19

10 Mar '19

Hey, I just noticed that, while we have zchunked metadata for the F30 base repository, it's not enabled to for updates-testing. I've looked in the ansible repo and in pungi, but I can't see where createrepo_c is actually called for updates-testing. Can someone please point me in the right direction? Jonathan

4 6

A short reminder on commit messages, freezes and hotfixes
by Kevin Fenzi 08 Mar '19

08 Mar '19

Greetings everyone. First, I don't mean to point to anyone specifically here, but I just wanted to send a reminder about some things: 1. For ansible commit messages, could everyone try and do: area/thing/host: short synopsis of the change <blank line> Longer explanation of the change. I realize it's anoying when just fixing a syntax error from a previous commit or something, but when looking back at commit history it's really a lot nicer to see: src.fedoraproject.org: fixing a typo in previous commit, Z should be Q than fix error I realize it's fun to add amusing log entries, but I have had to look at git commit logs and it really makes it anoying to tell when something was done unless it's nice and clear. Feel free to add your funny line in the longer comment. :) 2. We are in freeze, so please get freeze breaks for any frozen hosts. Of course if something is down/on fire you can push the fix and then go back and make sure it gets approved. This will get a bunch easier when we have ansible repo in pagure. 3. Finally: hotfixes. We have a process for these... I don't know if it's too much of a pain or what, but it seems like sometimes we just don't use it. The basic process is: * add ansible play to copy files from our repo to the filesystem * commit all the files you are going to touch. * commit in a second commit the changes for the hotfix. * push both with a comment about it. * run playbook. Perhaps we could make this easier with a ansible hotfix role that already had all the ansible side and you just needed to commit the files and diffs? in any case, it makes my teeth itch when running ansible or applying updates drops a hotfix. Thanks and I return you to your wed. :) kevin

4 4

[(FBR):] pagure: Turn off debug mode on pagure.io
by Pierre-Yves Chibon 08 Mar '19

08 Mar '19

This leads to some exception being raised instead of by-pass safely. It was useful at some point because pagure would not log error to its logs otherwise but Patrick has since fixed it and I believe it may be triggering some errors now. Signed-off-by: Pierre-Yves Chibon <pingou(a)pingoured.fr> --- roles/pagure/frontend/templates/pagure.wsgi | 1 - 1 file changed, 1 deletion(-) diff --git a/roles/pagure/frontend/templates/pagure.wsgi b/roles/pagure/frontend/templates/pagure.wsgi index 7f327fd0e..75c6ef343 100644 --- a/roles/pagure/frontend/templates/pagure.wsgi +++ b/roles/pagure/frontend/templates/pagure.wsgi @@ -27,4 +27,3 @@ os.environ['TEMP'] = '/srv/tmp/' from pagure.flask_app import create_app application = create_app() -application.debug = True -- 2.20.1

3 5

Ansible repo yaml auto format
by Clement Verna 07 Mar '19

07 Mar '19

Hi all, I would like to know what do you think about using an opinionated code formatter for our ansible repo ? I think this would help with enforcing a common style and make our yaml files easier to read and maintain. I have been looking at https://prettier.io/ which support yaml and I ran it on the repo's playbooks directory (see attached patch). Most of the changes are indentation but we could enforce more rules using prettier's configuration options if we wish (vhttps://prettier.io/docs/en/configuration.html). Prettier looks quite cool but the only down side is that it is a Javascript application and it is currently not packaged in Fedora, I have used a container to run it on my laptop. Anyway what do you think about it ? Does anybody knows an alternative to prettier ?

5 5

Fedora Badges - User Stories brainstorm meeting
by Clement Verna 07 Mar '19

07 Mar '19

Hi all, I am scheduling a meeting Friday March 08 at 1400 UTC [0] so that we can brainstorm some user stories for Fedora Badges, we will look at the Persona listed in the wiki [1] and find what can be improved for each of them, the expected output of this meeting is to have a Backlog of stories that we can then refined and prioritize. Anyone who is interested in the work or has idea is welcome to attend. The call will be recorded an available later to watch. To join the Meeting: https://bluejeans.com/2600891060 Cheers Clément [0] - https://apps.fedoraproject.org/calendar/meeting/9481/ [1] - https://fedoraproject.org/wiki/Infrastructure_2020/Fedora_Badges

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2019