infrastructure January 2020

infrastructure@lists.fedoraproject.org

18 participants
28 discussions

[PATCH] regindexer: create two sets of indexes
by Owen Taylor 22 Jan '20

22 Jan '20

From: "Owen W. Taylor" <otaylor(a)fishsoup.net> Flatpak-1.6 expects metadata to be stored in Docker-compatible labels rather than OCI annotations. We build Flatpaks for Fedora with both labels and annotations for compatibility with older and newer Flatpaks, but we also need to have two sets of indexes: - One that is served in response to a query for labels, and skips including Flatpak annotations in the response (to reduce size) - One that is served in response to a query for annotation, and skips including Flatpak labels in the response. This commit requires regindexer-1.6. See: https://pagure.io/fedora-infrastructure/issue/8579 Signed-off-by: Owen W. Taylor <otaylor(a)fishsoup.net> --- .../reversepassproxy.registry-generic.conf | 16 ++++++++ roles/regindexer/build/templates/config.yaml | 38 +++++++++++++++++++ 2 files changed, 54 insertions(+) diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf index 3030b1d73..e2878a8d7 100644 --- a/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf +++ b/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf @@ -25,17 +25,33 @@ RewriteCond "&%{QUERY_STRING}" &tag=testing RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) RewriteRule "^/index/static$" /index/flatpak-testing-%1.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &tag=testing +RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) +RewriteRule "^/index/static$" /index/flatpak-testing-%1-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) RewriteRule "^/index/static$" /index/flatpak-%1.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) +RewriteRule "^/index/static$" /index/flatpak-%1-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteCond "&%{QUERY_STRING}" &tag=testing RewriteRule "^/index/static$" /index/flatpak-testing.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &tag=testing +RewriteRule "^/index/static$" /index/flatpak-testing-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteRule "^/index/static$" /index/flatpak.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteRule "^/index/static$" /index/flatpak-labels.json [L,PT] + DocumentRoot /srv/web/registry-index/ <Directory /srv/web/registry-index> diff --git a/roles/regindexer/build/templates/config.yaml b/roles/regindexer/build/templates/config.yaml index 569dc9466..7b30290f8 100644 --- a/roles/regindexer/build/templates/config.yaml +++ b/roles/regindexer/build/templates/config.yaml @@ -7,6 +7,15 @@ indexes: registry_public: / tags: ['latest'] required_annotations: ['org.flatpak.ref'] + skip_flatpak_labels: True + extract_icons: True + flatpak_labels: + output: /var/lib/regindexer/index/flatpak-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['latest'] + required_labels: ['org.flatpak.ref'] + skip_flatpak_annotations: True extract_icons: True flatpak_testing: output: /var/lib/regindexer/index/flatpak-testing.json @@ -14,6 +23,15 @@ indexes: registry_public: / tags: ['testing'] required_annotations: ['org.flatpak.ref'] + skip_flatpak_labels: True + extract_icons: True + flatpak_testing_labels: + output: /var/lib/regindexer/index/flatpak-testing-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['testing'] + required_labels: ['org.flatpak.ref'] + skip_flatpak_annotations: True extract_icons: True flatpak_amd64: output: /var/lib/regindexer/index/flatpak-amd64.json @@ -22,6 +40,16 @@ indexes: tags: ['latest'] required_annotations: ['org.flatpak.ref'] architectures: ['amd64'] + skip_flatpak_labels: True + extract_icons: True + flatpak_amd64_labels: + output: /var/lib/regindexer/index/flatpak-amd64-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['latest'] + required_labels: ['org.flatpak.ref'] + architectures: ['amd64'] + skip_flatpak_annotations: True extract_icons: True flatpak_testing_amd64: output: /var/lib/regindexer/index/flatpak-testing-amd64.json @@ -30,6 +58,16 @@ indexes: tags: ['testing'] required_annotations: ['org.flatpak.ref'] architectures: ['amd64'] + skip_flatpak_labels: True + extract_icons: True + flatpak_testing_amd64_labels: + output: /var/lib/regindexer/index/flatpak-testing-amd64-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['testing'] + required_labels: ['org.flatpak.ref'] + architectures: ['amd64'] + skip_flatpak_annotations: True extract_icons: True daemon: topic_prefix: org.fedoraproject -- 2.21.1

1 0

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

22 Jan '20

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2020-01-23 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/9675/

1 0

Meeting agenda 2020-01-23 15:00 UTC
by Randy Barlow 22 Jan '20

22 Jan '20

The infrastructure team will be having its weekly meeting tomorrow, 2020-01-23 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.

1 0

Anitya (relese-monitoring.org) 0.18.0 deployed on production
by Michal Konecny 20 Jan '20

20 Jan '20

Hi everybody, Anitya (release-monitoring.org) 0.18.0 was deployed on production [0]. This release contains plenty of new features and bug fixes. See changelog for more information [1]. Few highlighted changes: - Filters in APIv2 are now case insensitive (No issue with foo vs. Foo anymore, when trying to look for project) - Automatically delete projects without versions that reached configured error threshold (No more junk projects, that can't get any version) - Add error counter to project (You can now see how many latest checks for new version failed on each project) - Github: Link to commit of latest version if known - Fix for "Current page is forgotten on login" (Now, after login, you will be redirected back to page from which you were redirected to login) On behalf of mages from release-monitoring.org, Michal [0] - https://release-monitoring.org/ [1] - https://github.com/release-monitoring/anitya/releases/tag/0.18.0 -- Role: Fedora CPE Team - Software Engineer IRC: mkonecny FAS: zlopez

1 0

CPE Weekly: 2020-01-17
by Aoife Moloney 18 Jan '20

18 Jan '20

Hi everyone, Welcome (back!) 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. High Level Project Updates: Fedora: General Updates Anitya is being prepared for a new release https://teams.fedoraproject.org/project/community-fire-team/us/8?kanban-sta… https://github.com/release-monitoring/anitya/milestone/5 RabbitMQ support for jms-messaging-plugin is merged UI around the bugzilla overriding support in src.fp.o was reworked Erlang stack in Fedora was rebuilt so it would work on the s390x architecture OSBS aarch64 is in staging Deploy OpenShift cluster on aarch64 boxes Configured OSBS on the x86_64 and aarch64 Openshift cluster in staging Test build is failing Bodhi maintenance work The team looked at https://pagure.io/fedora-infrastructure/issue/8466 New Team Initiatives CI/CD Some of our team are working across CI/CD initiatives this year. The team has identified a goal of Releng Automation, beginning with monitoring gating workflow. Right now they are forming their workflow so more updates to follow in the coming weeks on progress they are making! Sustaining Some of our team are also going to be working across sustainability initiatives, taking over more formally from the Community Fires Team. Check out the list of repos this team will be monitoring for tickets >>here<< We will have some weekly updates on tickets/issues resolved/needs action in the coming weeks! Application Retirements GDPR conversations between CPE and Red Hat are still happening surrounding some applications currently residing with the team Elections [Michal] Move to communishift is on hold till the GDPR situation is clear Fedocal Jlanda wants to try different approach due to permission errors https://pagure.io/fedora-infrastructure/issue/8274 No progress on kanban board - looks abandoned https://teams.fedoraproject.org/project/fedora-calendar/kanban Nuancier PR from sebwoj - Porting to Fedora messaging Schema completed Few errors remains to be solved before merging Benson Muite is now working on OIDC authentication - no update CentOS 8.1.1911 is seeding out to the mirrors! S3/Cloudfront distribution creation for Staging/PoC “Live” on mirrorlists.stg.centos.org CentOS 8 cloud images changes + jenkins jobs Update made to CentOS installation guide, which was also updated in the RHEL 7 installation guide too https://github.com/CentOS/docs-installation-guide/pull/10 Misc Fixes & Reviews https://pagure.io/fedora-infrastructure/issue/8515 https://pagure.io/fedora-infrastructure/issue/8464 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/41 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/42 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/44 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/45 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/46 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/47 Docs Reviews https://github.com/CentOS/docs-web-ui/pull/2 https://pagure.io/fedora-docs/quick-docs/pull-request/172 https://pagure.io/fedora-docs/quick-docs/pull-request/170 https://pagure.io/fedora-docs/quick-docs/pull-request/169 https://pagure.io/fedora-docs/quick-docs/pull-request/168 Note: This document is currently built from individual reports rolled into a 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. Comments? Suggestions? Feedback? Let Us Know! Kindest regards, Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

2 1

[PATCH] openshift-apps/docsbuilding: add dustymabe to owners
by Dusty Mabe 16 Jan '20

16 Jan '20

Considering we have CoreOS documentation. I'd like to be able to see the build processes to know when/if they are failing for any reason. --- playbooks/openshift-apps/docsbuilding.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/playbooks/openshift-apps/docsbuilding.yml b/playbooks/openshift-apps/docsbuilding.yml index 431e14392..b3f4f10be 100644 --- a/playbooks/openshift-apps/docsbuilding.yml +++ b/playbooks/openshift-apps/docsbuilding.yml @@ -15,6 +15,7 @@ appowners: - asamalik - jibecfed + - dustymabe tags: - apply-appowners - role: openshift/imagestream -- 2.24.1

3 3

Fedora Infrastructure Weekly meeting agenda (2020-01-16)
by Stephen John Smoogen 15 Jan '20

15 Jan '20

## Preamble The infrastructure team will be having its weekly meeting tomorrow, 2020-01-16 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 (2020-01-16) #meetingname infrastructure #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs #info Agenda is at: https://board.net/p/fedora-infra #topic aloha ``` ### Determine who the next chair is #topic Next chair #info magic eight ball says: #info 2020-01-16 - smooge #info 2020-01-23 - ??? #info 2020-01-30 - no meeting? ### 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 builder reinstalls/uprgades to f31 continuing. Should be done before holiday break - kevin #info ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin #info smooge is on PTO 2020-01-13 -> 2020-01-23 #info the following people will be AFK for Devconf: cverna, pingou, mkonecny, mboddu, nirik, relrod, nils #info the following people will be AFK for FOSDEM: pingou, mboddu ``` ### 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 cverna is oncall 2019-12-12 -> 2019-12-19 #info NOONE is oncall 2019-12-19 -> 2020-01-02 #info ??? is oncall 2020-01-02 -> 2020-01-09 #info smooge is oncall 2020-01-09 -> 2020-01-16 #info nirik is oncall 2020-01-16 -> 2020-01-23 #info ??? is oncall 2020-01-23 -> 2020-01-30 ## .oncalltakeeu .oncalltakeus #info Summary of last week: (from current oncall ) #info #topic Monitoring discussion [nirik] #info https://nagios.fedoraproject.org/nagios #info Go over existing out items and fix #topic Tickets discussion [nirik] #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket #topic ResultsDB Ownership Going Forward #link https://pagure.io/fedora-infrastructure/issue/8415 (revist post DevConf) #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 ``` 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 15 Jan '20

15 Jan '20

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2020-01-16 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/9675/

1 0

Meeting Agenda Item: Introduction James Richardson
by James Richardson 14 Jan '20

14 Jan '20

Hi everyone. My name is James Richardson and I have just joined the community platform engineering team as an intern. I have been using Fedora for about 6 months after making the change from Ubuntu. I am looking forward to contributing to the platform in any way I can. I am familiar with Javascript, Python3, and have a passion for security as it relates to data protection. My irc nick is jrichardson. Looking forward to chatting with you all soon. James -- James Richardson Software Engineer Intern Red Hat Waterford

1 0

Meeting Agenda Item: Introduction (Ernestas Kulik)
by Ernestas Kulik 14 Jan '20

14 Jan '20

Hi, I’m Ernestas Kulik (ernestask on freenode) and I seek to become one of youse. At my day job (not much of a secret, given the signature), I take care of the ABRT stack, including the Fedora server. I have an RHCSA and RHCE certifications, which, as of recently, means that I have Ansible in my swear word arsenal, but, by nature, I’m mostly a C programmer. However, I have dabbled in some web hackery, so I could probably also lend a hand with related issues in Fedora. As for what I’d like to learn/do - not sure. Probably just helping out with the day-to-day stuff to get a better grasp of how things work, what other swear words you use, so I could more effectively contribute towards our side of the infrastructure (especially since our bus factor is 1). And that’s pretty much it. Currently monitoring the issues on Pagure to see where I can jump in. -- Ernestas Kulik Associate Software Engineer - Base Operating Systems (Core Services/ABRT) Red Hat Czech, s.r.o.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2020