infrastructure December 2018

infrastructure@lists.fedoraproject.org

17 participants
30 discussions

Planned Outage - PHX2 Colocation- 2018-12-13 23:00 UTC
by Stephen John Smoogen 10 Dec '18

10 Dec '18

There will be an outage starting at 2018-12-13 23:00 UTC, which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2017-05-03 21:00UTC' Reason for outage: Various switches at the colocation are needing updates and reboots to get latest firmware working. While the outage should not take the entire 5 hours, it is being blocked out in case there are problems which are not realized and need backing out or other changes. Affected Services: dl.fedoraproject.org all build services most web services copr and all other cloud services. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7433 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 10 Dec '18

10 Dec '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-12-11 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

Holiday plans and reminders
by Kevin Fenzi 10 Dec '18

10 Dec '18

Greetings everyone. The holidays are coming up later this month and so I thought I would remind folks about holiday handling in Fedora Infrastructure. Red Hat has a shutdown period, this year between 2018-12-22 and 2019-01-02. All Red Hat employees (at least in the US) are supposed to take this time to spend with friends and family and recharge for the year ahead. So, this means there's not too many Red Hat employees around then. If you are making changes to Fedora Infrastructure during this time, please be aware that alerts or problems might call in someone who is spending time away, so be especially careful not to disrupt things, cause alerts or outages. If you are someone who does want to work on things, try and update tickets or PR's or lists posts with your work instead of pinging people or mailing them directly. This work can then be processed when everyone is back. Hope everyone has a lovely holidays... kevin

1 0

Patch for issue 7378
by Zach Villers 10 Dec '18

10 Dec '18

All - patch is attached. https://pagure.io/fedora-infrastructure/issue/7378 diff --git a/playbooks/include/proxies-redirects.yml b/playbooks/include/proxies-redirects.yml index 3a108eda3..004b2d4dc 100644 --- a/playbooks/include/proxies-redirects.yml +++ b/playbooks/include/proxies-redirects.yml @@ -62,7 +62,7 @@ - role: httpd/redirect shortname: jenkins website: jenkins.fedorainfracloud.org - target: https://jenkins-fedora-infra.apps.ci.centos.org + target: https://jenkins-fedora-infra.apps.ci.centos.org/$1 - role: httpd/redirectmatch shortname: fpaste Thanks, Zach #aikidouke

2 4

Releasing Greenwave
by Giulia Naponiello 10 Dec '18

10 Dec '18

Hello, I'll try to release Greenwave today. I'm available on IRC on #fedora-apps - giulia/gnaponie is my nickname. Cheers Giulia

1 1

Best path for Fedora zchunk dictionaries
by Jonathan Dieter 08 Dec '18

08 Dec '18

I'm currently in the process of packaging up fedora-repo-zdicts[1], a package which will contain the zchunk dictionaries for all active Fedora releases. When running createrepo_c or mergerepo_c with zchunk support, the directory containing the zdicts is passed in and createrepo_c will choose the right zdict for each metadata file. The form of that directory is /usr/share/fedora-repo-dicts/<release> where <release> is the release that the metadata is being generated for. My question is what <release> should actually look like. This is very Fedora specific, so I want to choose whatever the easiest variable is for infra to pass to createrepo_c or mergerepo_c. Currently <release> is set to PLATFORM_ID in /etc/os-release (so, platform:fedora-30 for Rawhide), but that's probably overly generic. What would be a better pattern for <release>? fedora-30? f30? Just 30? Jonathan

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 05 Dec '18

05 Dec '18

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2018-12-06 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 or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

[PATCH] bodhi-pungi: don't run silverblue compose for testing
by Dusty Mabe 04 Dec '18

04 Dec '18

This is a temporary hack to workaround https://pagure.io/pungi/issue/1092. Note this also just re-uses the f27 logic, which is no longer needed. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index ee1edb6ed..74c0378ec 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -153,8 +153,8 @@ ostree = { "failable": ["ppc64le", "aarch64"], [% endif %] }, - # Atomic Workstation - [% if release.version_int >= 27 %] + # Fedora Silverblue + [% if request.name == 'stable' %] { [% if release.version_int >= 28 %] "version": "!VERSION_FROM_VERSION_DATE_RESPIN", -- 2.14.5

2 1

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 03 Dec '18

03 Dec '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-12-04 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

[PATCH] bodhi-pungi: pass in ostree_oskey to fedora-lorax-templates
by Dusty Mabe 03 Dec '18

03 Dec '18

This is needed because of a recent change to parameterize the key. https://pagure.io/fedora-lorax-templates/pull-request/30 --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index baed32f3f..ee1edb6ed 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -312,6 +312,7 @@ ostree_installer = [ 'ostree_install_repo=https://kojipkgs.fedoraproject.org/compose/atomic/repo/', 'ostree_update_repo=https://dl.fedoraproject.org/atomic/repo/', 'ostree_osname=fedora-atomic', + 'ostree_oskey=fedora-[[ release.version_int ]]-primary', 'ostree_install_ref=fedora/[[ release.version_int ]]/[[ arch ]]/[% if request.name == "testing" %]testing[% else %]updates[% endif %]/atomic-host', 'ostree_update_ref=fedora/[[ release.version_int ]]/[[ arch ]]/atomic-host', ], -- 2.14.5

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2018