infrastructure September 2017

infrastructure@lists.fedoraproject.org

41 participants
67 discussions

[FBR] Make cvsadmin the admin group for dist-git pagure
by Till Maas 26 Sep '17

26 Sep '17

Hi, currently I cannot (un)orphan packages in dist-git pagure or give them to other maintainers. AFAIU only people in sysadmin-main can this so other releng members not in sysadmin-main are affected as well. Therefore I would like to change the admin group for dist-git pagure to cvsadmin, which was the admin group for dist-git/pkgdb in the past. There are the current group members: sysadmin-main:x:100322:ausil,codeblock,jstanley,kevin,maxamillion,pbrobinson,pingou,puiterwijk,ralph,smooge,tflink cvsadmin:x:101197:ausil,jwboyer,kevin,limb,mohanboddu,pbrobinson,releng,spot,tibbs,till Kind regards Till From 684353289eca2f38c190cd426b962c169d446812 Mon Sep 17 00:00:00 2001 From: Till Maas <opensource(a)till.name> Date: Fri, 22 Sep 2017 21:46:47 +0200 Subject: [PATCH] Make cvsadmin group admin for dist-git pagure Releng manages dist-git pagure and in the past cvsadmin was used for adminstrative permissions for dist-git. Therefore use it in dist-git pagure as well. Reference: https://pagure.io/releng/issue/7061 Signed-off-by: Till Maas <opensource(a)till.name> --- roles/distgit/pagure/templates/pagure.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/distgit/pagure/templates/pagure.cfg b/roles/distgit/pagure/templates/pagure.cfg index 833c57dc8..e3508aee0 100644 --- a/roles/distgit/pagure/templates/pagure.cfg +++ b/roles/distgit/pagure/templates/pagure.cfg @@ -29,7 +29,7 @@ PREFERRED_URL_SCHEME='https' DB_URL = 'postgresql://{{ distgit_pagure_db_user }}:{{ distgit_pagure_db_pass }}@{{ distgit_pagure_db_host }}/{{ distgit_pagure_db_name }}' ### The FAS group in which the admin of pagure are -ADMIN_GROUP = ['sysadmin-main'] +ADMIN_GROUP = ['cvsadmin'] ### The email address to which the flask.log will send the errors (tracebacks) EMAIL_ERROR = 'pingou(a)pingoured.fr' -- 2.13.5

4 6

Weekly Koji Infra Tag Report
by Nobody 24 Sep '17

24 Sep '17

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- fas-plugin-yubikey epel6-infra puiterwijk fedora-packages epel6-infra puiterwijk mediawiki119-Cite epel6-infra puiterwijk mediawiki119-Lockdown epel6-infra puiterwijk mediawiki119-SpecialInterwiki epel6-infra puiterwijk fas epel6-infra puiterwijk mediawiki-FedoraBadges epel6-infra puiterwijk epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-zope-sqlalchemy epel7-infra puiterwijk fedmsg-beaker-repoupdate epel7-infra tflink ansible_utils epel7-infra puiterwijk apps-fp-o epel7-infra puiterwijk fedora-elections epel7-infra puiterwijk fedora-releng-dash epel7-infra puiterwijk fedora-tagger epel7-infra puiterwijk nuancier epel7-infra puiterwijk python-fedmsg-fasclient epel7-infra puiterwijk supybot-pinglists epel7-infra puiterwijk testdays epel7-infra puiterwijk venus epel7-infra puiterwijk glusterfs epel7-infra kevin basset epel7-infra puiterwijk kerneltest epel7-infra pingou pkgdb2 epel7-infra pingou flask-login epel7-infra ralph python-velruse epel7-infra puiterwijk python-pdc epel7-infra ralph the-new-hotness epel7-infra jcline iptables epel7-infra puiterwijk freeipa-ktutils epel7-infra puiterwijk compose-utils epel7-infra ausil anitya epel7-infra jcline python-stomper epel7-infra puiterwijk python-flask-login epel7-infra ralph fas epel7-infra puiterwijk pdc-updater epel7-infra ralph python-IPy epel7-infra kevin blockerbugs epel7-infra tflink python-summershum epel7-infra puiterwijk python-robosignatory epel7-infra puiterwijk fedocal epel7-infra pingou pagure-dist-git epel7-infra pingou koji-theme-fedora epel7-infra puiterwijk python-webhelpers epel7-infra puiterwijk python-django-jsonfield epel7-infra ralph mirrormanager2 epel7-infra puiterwijk f23-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- libphutil, f23-infra tflink arcanist, f23-infra tflink phabricator f23-infra tflink phabricator-extension-ipsilonauth f23-infra tflink libphutil f23-infra tflink arcanist f23-infra tflink f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin phabricator-extension-oauth f24-infra tflink python-twill f24-infra codeblock stickynotes2modernpaste f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-skin-fedora f24-infra puiterwijk mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk phabricator f24-infra tflink mediawiki-Lockdown f24-infra kevin libphutil f24-infra tflink arcanist f24-infra tflink mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- cssdb f25-infra puiterwijk python-flask-testing f25-infra codeblock modern-paste f25-infra codeblock python-coveralls f25-infra codeblock phabricator f25-infra tflink basset f25-infra puiterwijk mediawiki-FedoraBadges f25-infra kevin mediawiki-Lockdown f25-infra kevin mediawiki-RSS f25-infra kevin rdbsync f25-infra pingou plus-plus-service f25-infra pingou python-pdc f25-infra ralph python-django-cors-headers f25-infra ralph python-django-rest-framework-composed-permissions f25-infra ralph patternfly1 f25-infra ralph mediawiki-openid f25-infra kevin piwik f25-infra codeblock fas f25-infra kevin libphutil, f25-infra tflink arcanist, f25-infra tflink mdapi f25-infra pingou phabricator-extension-ipsilonauth f25-infra tflink libphutil f25-infra tflink arcanist f25-infra tflink python-twill f25-infra codeblock stickynotes2modernpaste f25-infra codeblock mediawiki-skin-fedora f25-infra kevin f26-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- fas f26-infra puiterwijk greenwave f26-infra ralph piwik f26-infra codeblock f27-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- fas f27-infra kevin piwik f27-infra codeblock f28-infra (no matching packages)

1 0

FBR: Update Dockerfile for OSBS buildroot container
by Adam Miller 24 Sep '17

24 Sep '17

Hello all, Yesterday I noticed that the container builds are not properly "content generator metadata importing" into koji post build in OSBS. This is because the version of osbs-client on the koji builders got updated but I forgot to update the buildroot to contain the new version of atomic-reactor (this all happened right around Flock and I had to fix a build issue with atomic-reactor and then just forgot). I would like to make this ansible change, deploy it to the osbs machines, and trigger a rebuild of the buildroot container on the osbs nodes. Thank you, -AdamM commit faec00e81d9f178b05238e0b295423a2397245e8 Author: Adam Miller <admiller(a)redhat.com> Date: Fri Sep 22 14:28:48 2017 +0000 update osbs buildroot container Dockerfile for prod Signed-off-by: Adam Miller <admiller(a)redhat.com> diff --git a/files/osbs/buildroot-Dockerfile-production.j2 b/files/osbs/buildroot-Dockerfile-production.j2 index fcc5568..0de835a 100644 --- a/files/osbs/buildroot-Dockerfile-production.j2 +++ b/files/osbs/buildroot-Dockerfile-production.j2 @@ -1,9 +1,8 @@ -FROM fedora:24 +FROM registry.fedoraproject.org/fedora ADD ./infra-tags.repo /etc/yum.repos.d/infra-tags.repo -RUN dnf -y install --refresh dnf-plugins-core && dnf -y install docker git python-docker-py python-setuptools e2fsprogs koji python-backports-lzma osbs-client gssproxy fedpkg python-docker-squash atomic-reactor python-atomic-reactor* +RUN dnf -y install --refresh dnf-plugins-core && dnf -y install docker git python3-docker-py python3-setuptools e2fsprogs koji osbs-client gssproxy fedpkg python3-docker-squash atomic-reactor python3-atomic-reactor* go-md2man RUN sed -i 's|.*default_ccache_name.*| default_ccache_name = DIR:/tmp/ccache_%{uid}|g' /etc/krb5.conf ADD ./krb5.osbs_{{osbs_url}}.keytab /etc/ ADD ./ca.crt /etc/pki/ca-trust/source/anchors/osbs.ca.crt RUN update-ca-trust -CMD ["python2", "/usr/bin/atomic-reactor", "--verbose", "inside-build"] - +CMD ["python3", "/usr/bin/atomic-reactor", "--verbose", "inside-build"]

3 2

Freeze break: add compose-x86-02 compose machine
by Kevin Fenzi 22 Sep '17

22 Sep '17

Greetings. In ticket https://pagure.io/fedora-infrastructure/issue/6383 releng asks for a new machine that is like compose-x86-01 to do modular server composes with. Attached is a patch to make such a machine. Additionally this will need running the noc playbook (to add to nagios) and the fedmsg playbooks (to add it as a fedmsg sender). +1s? kevin -- From 52657c6540da0c120ed6a3723ea6b76d1431106d Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Fri, 22 Sep 2017 21:10:06 +0000 Subject: [PATCH] add compose-x86-02 host for modular server composes Signed-off-by: Kevin Fenzi <kevin(a)scrye.com> --- .../compose-x86-02.phx2.fedoraproject.org | 44 ++++++++++++++++++++++ inventory/inventory | 1 + 2 files changed, 45 insertions(+) create mode 100644 inventory/host_vars/compose-x86-02.phx2.fedoraproject.org diff --git a/inventory/host_vars/compose-x86-02.phx2.fedoraproject.org b/inventory/host_vars/compose-x86-02.phx2.fedoraproject.org new file mode 100644 index 0000000..7ca9fe1 --- /dev/null +++ b/inventory/host_vars/compose-x86-02.phx2.fedoraproject.org @@ -0,0 +1,44 @@ +nm: 255.255.255.0 +gw: 10.5.125.254 +dns: 10.5.126.21 + +# +# These are 64bit +# +libdir: /usr/lib64 + +ks_url: http://10.5.126.23/repo/rhel/ks/buildvm-fedora-26 +ks_repo: http://10.5.126.23/pub/fedora/linux/releases/26/Server/x86_64/os/ +virt_install_command: "{{ virt_install_command_two_nic }}" + +lvm_size: 30000 +mem_size: 8192 +num_cpus: 8 + +volgroup: /dev/xenGuests +eth0_ip: 10.5.125.42 +eth1_ip: 10.5.127.27 +eth1_gw: 10.5.127.254 +vmhost: bvirthost05.phx2.fedoraproject.org +datacenter: phx2 + +fas_client_groups: sysadmin-releng + +koji_hub_nfs: "fedora_koji" + +kojipkgs_url: kojipkgs.fedoraproject.org +kojihub_url: koji.fedoraproject.org/kojihub +kojihub_scheme: https + +fedmsg_certs: +- service: releng + owner: root + group: sysadmin-releng + can_send: + # new school pungi-koji stuff (ask dgilmore) + - pungi.compose.phase.start + - pungi.compose.phase.stop + - pungi.compose.status.change + - pungi.compose.createiso.targets + - pungi.compose.createiso.imagefail + - pungi.compose.createiso.imagedone diff --git a/inventory/inventory b/inventory/inventory index 3021edf..606d47e 100644 --- a/inventory/inventory +++ b/inventory/inventory @@ -25,6 +25,7 @@ arm03-qa01.cloud.fedoraproject.org [releng-compose] compose-x86-01.phx2.fedoraproject.org +compose-x86-02.phx2.fedoraproject.org branched-composer.phx2.fedoraproject.org rawhide-composer.phx2.fedoraproject.org -- 1.8.3.1

4 3

Introduction: David Reed
by David Reed 21 Sep '17

21 Sep '17

Hello all. I'm a long time user of Fedora (been using it since Fedora 4) and finally decided it's about time I start contributing to this awesome distro and thought the infrastructure group would be a good fit. I'm a Sr. Software Engineer by profession and have 8 years of experience using python for developing internal infrastructure applications. My current project consists of writing/maintaining code for a farm of 300 embedded development boards. That farm distributes benchmarking workloads across all the active embedded systems and performs performance analysis of the results. I love python and use it every day. I'm interested in helping in the development of python based stacks, but wouldn't mind picking up a new language or framework should the need arise. My IRC handle is dreed and I just logged into the #fedora-admin channel, though I apparently just missed the weekly meeting. --David

2 1

FBR: Remove old files from /pub/fedora /pub/fedora-secondary
by Stephen John Smoogen 21 Sep '17

21 Sep '17

The actions to do this would be the following: $ sudo -i ssh root(a)bodhi-backend01.phx2.fedoraproject.org # su - -s /bin/bash ftpsync # cd /pub/fedora/linux/releases/22 # rm -rvf ./* # ln -s ../21/README . # cd ../23 # rm -rvf ./* # ln -s ../21/README . # cd ../24 # rm -rvf ./* # ln -s ../21/README . # cd ../../updates/22 ... # cd ../testing/22 ... # cd /pub/fedora-secondary/releases/21 ... -- Stephen J Smoogen.

4 3

Re: How to change upstream release monitoring in pagure?
by Zamir SUN 21 Sep '17

21 Sep '17

I'm forwarding my question to Infra. I want to enable release monitoring for my packages. The wiki[1] mentions that the-new-hotness "...when it receives a message indicating that a project has a new release, if that project is mapped to a Fedora package, it will check in pkgdb2 if the Fedora package is marked to be monitored. " However pkgdb is retired and I cannot see an option to turn monitoring status on package page of src.fedoraproject.org. So, is there anyone that can point us how we can change the 'release monitoring' status? Thanks. [1] https://fedoraproject.org/wiki/Upstream_release_monitoring On 09/19/2017 08:04 PM, Zamir Sun wrote: > On Mon, Aug 14, 2017 at 11:06 PM, Jaroslav Skarvada <jskarvad(a)redhat.com> wrote: >> How to change upstream release monitoring, i.e. how to >> switch the states between disabled, monitoring, and >> monitoring with build? I didn't find anything related in [1], >> so I tried: >> > > Does anyone know how can we do this? Recently I also want to change > the status for some packages. > > Thanks in advance. > >> $ fedrepo-req preeny -m monitoring -t 1479022 >> >> But the request [2] was closed as invalid? What's the correct >> procedure for it? >> >> thanks & regards >> >> Jaroslav >> -- Ziqian SUN (Zamir) zsun(a)fedoraproject.org GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E Want to know more about Fedora? Visit https://fedoraproject.org/wiki/

2 2

Freeze break request: add pki redirects to proxies
by Kevin Fenzi 21 Sep '17

21 Sep '17

Greetings. Per https://pagure.io/fedora-infrastructure/issue/6375 I would like to add the following redirects and run the proxy playbooks. +1s? kevin -- > diff --git a/files/httpd/fedorahosted-redirects.conf b/files/httpd/fedorahosted-redirects.conf > index e5bbe40..8480ea3 100644 > --- a/files/httpd/fedorahosted-redirects.conf > +++ b/files/httpd/fedorahosted-redirects.conf > @@ -231,6 +231,12 @@ RewriteRule ^/fedora-medical/ https://pagure.io/fedora-medical [R=301] > RewriteRule ^/libverto/ https://github.com/latchset/libverto/ [R=301] > RewriteRule ^/libverto https://github.com/latchset/libverto [R=301] > > +RewriteRule ^/pki/report https://pagure.io/dogtagpki/issues [L,R] > +RewriteRule ^/pki/ticket/(.*) https://pagure.io/dogtagpki/issue/$1 [L,R] > +RewriteRule ^/pki/p/k/pki/(.*) https://releases.pagure.org/dogtagpki/$1 [L,R] > +RewriteRule ^/pki/p/k/pki https://releases.pagure.org/dogtagpki/ [L,R] > +RewriteRule ^/pki https://pagure.io/dogtagpki [R=301] > + > # Ipsilon wiki is now moving content > ReWriteCond %{REQUEST_URI} !^/ipsilon/.*

3 2

FBR: Configure Bodhi to use pre-beta policy on F27
by Randy Barlow 20 Sep '17

20 Sep '17

Peter notified me today that Bodhi had not been configured to use the pre-beta policy on F27 when the F27 release was created in Bodhi. This patch should do the trick.

5 5

Plan for Thursdays Fedora Infrastructure Meeting (2017-09-21)
by Stephen John Smoogen 20 Sep '17

20 Sep '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-09-21 at 18:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2017-09-21) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson maxamillion = 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 = 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 PHX2 Colo Trip, Dec 4th - 9th #info Infrastructure will be down during that trip. #info beta freeze still going on. #info Moving .stg. ips will wait til after freeze #info Moving i2 download server is done! = 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 These 3 easy tips will make you a better Linux admin #topic He typed a command. You will never believe what happened next! = Apprentice office hours = #topic Apprentice Open office hours 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.) #topic Learn about: We will be drafting people this meeting for next week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2017