infrastructure August 2022

infrastructure@lists.fedoraproject.org

19 participants
20 discussions

Fedora 37 Beta Freeze now in effect
by Kevin Fenzi 14 Sep '22

14 Sep '22

Greetings. We are now in the infrastructure freeze leading up to the Fedora 37 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 37 Beta 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 2022-09-13 (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 or a pull request for review. Thanks, Kevin

1 1

About JS framework
by Pierre-Yves Chibon 14 Sep '22

14 Sep '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

15 19

Meeting Agenda Item: Introduction Anwesha Das
by Anwesha Das 31 Aug '22

31 Aug '22

Hello, This is Anwesha, a lawyer turned into a technologist. Wanted to contribute to the Fedora infrastructure for a long time. Finally I guess it is my time to jump in :). IRC nick: anwesha Technologies I know (in no particular order) : - Linux - Ansible - Nginx/Apache - Docker - Python - a bit of BIND I am currently working as Junior System Administrator at Verkligendata AB, Stockholm. Previously I worked as a Cloud Engineer at Scrollstack (my first full time tech job). I maintain all the infrastructure related to https://dgplug.org and https://foss.training. I am a PyLadies organizer at Stockholm and led the PyLadies efforts back in India. What do I want to learn? I am here to learn to contribute and manage large infrastructure. Especially Ansible, network stacks and monitoring. I am also wondering if I can work on [0]? Looking forward to meeting and learning from you all on IRC. [0] https://pagure.io/fedora-infrastructure/issue/10543 Cheers Anwesha

2 1

FMN Replacement Initiative Kick-off
by James Richardson 30 Aug '22

30 Aug '22

Hi Everyone, This is an email to bring everyone up to speed with the Fedora Messaging Notifications (FMN) Replacement initiative. *What is FMN?* FMN is a service which allows users to create filters on messages sent via the message bus in Fedora Infrastructure. Users can then forward these notifications to their respective email addresses and/or IRC profiles. *Why is it being replaced?* - Message Delivery Lag - In times of peak congestion on the message queue (e.g. during a mass rebuild) it can take days for messages to be delivered to users - The current version of FMN uses the deprecated fedmsg library to connect to our legacy, ZeroMQ-based message bus, instead of connecting to the new message bus which is based on AMQP. While messages are bridged between both systems, we eventually want everything to run natively on the new bus so we can decommission the old one. - UI/UX - From ad hoc discussions with the development community we learned that one of the major issues with FMN is its user interface. The workflow for creating new filters is complicated and confusing, and users have to define filters separately for different destinations (i.e. email and IRC). This is due to how the database is designed. *Design Plan* Write a fedora-messaging consumer that would triage incoming messages and add notifications to one queue per destination (email, irc, matrix). They would be on a FMN-specific vhost on the RabbitMQ server. Then write AMQP consumers for these queues to actually send the notifications. This would allow the IRC and Matrix notifiers to maintain a permanent connection to the IRC/Matrix server(s). This work requires all applications to use Fedora Messaging Message Schemas, because the triage component will rely on schemas to extract information from the messages. *Prospective Timelines* First Month - The development team has been onboarded - The backlog has epic level tickets created - Testing criteria is loosely defined for performance, i.e. what is the min/max acceptable time for receiving a notification Three Months - An update is sent to the lists on work underway - Infra leads have been invited to a review of the work to date - A firmer timeline for project delivery has been defined - There is testing criteria/benchmarking agreed to Six Months - The service is deployed in staging or its in production but it is not enabled for everyone yet - Testers are invited to onboard into the new service and help test performance - An outage period for cutover to the new service has been identified and planned if needed Nine Months - Hotfixes are applied *Team Members* Aurelien Bompard - Tech Lead Frontend & Message Consumer Nils Philippsen - Tech Lead Web API Backend Ryan Lerch - Developer & Frontend Designer James Richardson - Developer & Agile Practitioner If there are any questions/concerns/advice/opinions/etc please don’t hesitate to get in touch with us. Regards, James -- James Richardson Associate Software Engineer He | Him | His Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City jamricha(a)redhat.com <lgriffin(a)redhat.com> M: +353851970521 <+353877545162> IRC(preferred): jrichardson DM:jamricha @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig>

1 0

[Fedocal] Reminder meeting : Websites & Apps Team Meeting
by t0xic0der＠fedoraproject.org 29 Aug '22

29 Aug '22

Dear all, You are kindly invited to the meeting: Websites & Apps Team Meeting on 2022-08-30 from 15:00:00 to 16:00:00 UTC At https://meet.jit.si/fedora-websites-apps-meeting The meeting will be about: Weekly team meeting for the Websites & Apps Team. This is part of the [Websites & Apps Community Revamp Objective](https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Comm…. See [past discussion]( https://discussion.fedoraproject.org/t/planning-meeting-for-websites-apps-t…) to learn more about the Websites & Apps Team and how it came together. More information available at: [hackmd.io/Mxm2We3yTqKybLsdohadOA](https://hackmd.io/Mxm2We3yTqKybLsdohadOA?view) Source: https://calendar.fedoraproject.org//meeting/9990/

1 0

CPE Weekly Update - Week 34 2022
by Michal Konecny 27 Aug '22

27 Aug '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-34-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

2 1

planet
by Kevin Fenzi 24 Aug '22

24 Aug '22

Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it. Right now: fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople). To add a blog/rss feed you have to login there and edit your .planet file, then scripting pulls all those .planet files and tries to fetch all the feeds and then serves them up at http://fedoraplanet.org. It uses a app called 'venus' to do this. venus is written in very old python2 and very very dead upstream. We run into the following problems with it: * Sometimes it gets stuck and just stops processing until it's killed. * It's serving on a http site, which causes people to ask us to make it https, but that would just change the errors because many feeds it pulls are still http since they were added back before letsencrypt existed. * We have a handy 'website' field in our new account system, but aren't using it at all. * The .planet parsing is poor, any number of things can cause it to break. We have two open tickets on it: - https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto, a ruby based, but maintained thing) - https://pagure.io/fedora-infrastructure/issue/10490 ( planet not served via ssl) Which I am just going to close now. So, I can think of a number of options and would love everyone who has thoughts on it to chime in: 1. Do nothing. Venus "works" and .planet files are cool and retro. 2. Switch to pluto and use account system 'website' fields of contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there) 3. Switch to something better/bigger. I would think (although I don't know) that there might be something that would not only aggregate rss feeds for contributors, but perhaps mastodon/twitter/whatever also. 4. Planets are old and tired, just drop the entire thing. People can maintain their own rss lists. 5. Planets are old and tired, just drop the entire thing. But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever. 6. Switch to pluto as in 2, but also setup some curators. Have a 'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated. 6. Get someones (not it!) to take in all the twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something. 7. Your brilliant idea here! So, thoughts? this is not at all urgent, but we should end up doing something with it sometime. :) kevin

10 21

Freeze Break Request: add distro.builders to nameservers zones.conf
by Patrick マルタインアンドレアス Uiterwijk 24 Aug '22

24 Aug '22

Hi all, Could I get +1s for the following Ansible patch? This adds the domain distro.builders (used for tiny.distro.builders for the Fedora Minimization Content Resolver) to the nameserver zones configuration. This domain is being transferred to Red Hat/Fedora control. Thanks in advance, Patrick Patch: commit 3f79919102a8259fcf8f65d488231fc4aa680614 (HEAD -> add_distro_builder) Author: Patrick Uiterwijk <patrick(a)puiterwijk.org> Date: Wed Aug 24 10:01:49 2022 +0200 Add distro.builders zone to zones.conf Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org> diff --git a/roles/dns/files/zones.conf b/roles/dns/files/zones.conf index 3119c5b074..c87df89836 100644 --- a/roles/dns/files/zones.conf +++ b/roles/dns/files/zones.conf @@ -152,6 +152,11 @@ zone "192-255.169.211.140.in-addr.arpa" { file "/var/named/master/built/192-255.169.211.140.in-addr.arpa"; }; +zone "distro.builders" { + type master; + file "/var/named/master/built/distro.builders"; +}; + zone "epel.io" { type master; file "/var/named/master/built/epel.io";

3 2

PACKAGE SOURCES site: Can't add a user as admin.
by Jun Aruga (he / him) 23 Aug '22

23 Aug '22

Hi, I tried to add a user [1] to the rpms/htslib [2] project as "admin" on the PACKAGE SOURCES (src.fedoraproject.org). But clicking the "Add" button on the "Add user" page, I got the error message below, even when the user has the role "member" of the "packager"[1]. "This user must be in one of the following groups to be allowed to be added to this project: packager". Do you know how to add the user? Thanks. [1] https://accounts.fedoraproject.org/user/ron/ [2] rpms/htslib - Settings - Users & Groups - "Add user" - https://src.fedoraproject.org/rpms/htslib/adduser -- Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic See <https://www.worldtimebuddy.com/czech-republic-prague-to-utc> for the timezone.

2 2

[Fedocal] Reminder meeting : Websites & Apps Team Meeting
by t0xic0der＠fedoraproject.org 22 Aug '22

22 Aug '22

Dear all, You are kindly invited to the meeting: Websites & Apps Team Meeting on 2022-08-23 from 15:00:00 to 16:00:00 UTC At https://meet.jit.si/fedora-websites-apps-meeting The meeting will be about: Weekly team meeting for the Websites & Apps Team. This is part of the [Websites & Apps Community Revamp Objective](https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Comm…. See [past discussion]( https://discussion.fedoraproject.org/t/planning-meeting-for-websites-apps-t…) to learn more about the Websites & Apps Team and how it came together. More information available at: [hackmd.io/Mxm2We3yTqKybLsdohadOA](https://hackmd.io/Mxm2We3yTqKybLsdohadOA?view) Source: https://calendar.fedoraproject.org//meeting/9990/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2022