infrastructure April 2022

infrastructure@lists.fedoraproject.org

15 participants
20 discussions

planet
by Kevin Fenzi 19 Apr '23

19 Apr '23

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

13 44

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '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

10 12

Fedora Contributor Tee Shirt Giveaway
by Vipul Siddharth 19 May '22

19 May '22

Hey all, As we get ready to release Fedora Linux 36, another anticipated moment has arrived: the Fedora contributor tee shirt giveaway! Sending a huge “THANK YOU!!” to everyone who works to make Fedora the amazing community it is. The Mindshare Committee is excited to be able to share swag with our community to celebrate the latest release of Fedora Linux. Please visit the community blog post[0] to see how to claim yours! [0] https://communityblog.fedoraproject.org/fedora-contributor-tee-shirt-giveaw… On behalf of the Mindshare committee, -- Vipul Siddharth He/His/Him Mentored Project @ Mindshare | DEI advisor @ Fedora Council

3 2

CPE Weekly Update – Week 17 2022
by Michal Konecny 29 Apr '22

29 Apr '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) Week: 25th April - 29th April 2022 If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-17-2022/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-27-04-2022.pdf Update ------ ### Fedora Infra * Issues sending email from fedoraproject.org -> redhat.com. Finally got tls connection reuse working so we didn’t hit their limits. * FCOS apps (almost) all moved from ocp3->ocp4 clusters * Cleaned up after a bodhi bug left rawhide updates in limbo. * Very close to having resultsdb in ocp4 stg working, just some url adjustments left hopefully. * Anitya and the-new-hotness messaging schemas were moved to separate repositories https://github.com/fedora-infra/the-new-hotness-messages https://github.com/fedora-infra/anitya-messages ### CentOS Infra including CentOS CI * Deploying RHEL (like Fedora Infra) in infra is [now supported](https://pagure.io/centos-infra/issue/739) * [Duffy testing/fixes](https://pagure.io/centos-infra/issue/712) still ongoing * Openshift upgrade (fixing jenkins image and [sync issue](https://pagure.io/centos-infra/issue/728)) * Bussiness As Usual (new tags/mirrors changes requests) ### Release Engineering * F36 RC composes 1.1 on friday 1.2 yesterday * Discussion about where container images live and potential move to quay.io ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Prototyping CI actions for Stream 9 using Duffy system, awaiting onboarding from infra * New compose released * Upcoming: Reviewing Stream container and image build processes * Improvements to the CVE checker have been rolled out * Fedora ELN is being used as a prototype for SHA-1 removal in Fedora ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates ------- * Parallelize running provisioning/deprovisioning playbooks * More testing and minor fixes ## Package Automation (Packit Service) Goal of this initiative ----------------------- Automate RPM packaging of infra apps/packages Updates ------- * backlog is stocked with plenty of our apps for the time being, more to be added as needed * Expect emails, lots of emails * fasjson-client, fedora-messaging and datagrepper currently being worked on * currently able to build in copr, minus some hiccups * we are currently looking at the best way to version. what are the teams thoughts on moving spec files upstream? it makes everything cleaner in packit. thoughts on a postcard please ## Flask-oidc: oauth2client replacement Goal of this initiative ----------------------- Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: -------- * Currently finding all instances of oauth2client code in the current flask-oidc code, mapping functionality to whats available in the authlib library. ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 up to 2416 source packages (increase of 45 from last week) * qt5-5.15.3 update in CentOS Stream 8 and 9 has caused [update breakages for KDE users](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedor… on those distros (EPEL8 and EPEL9). Updated packages are being built as we speak. * Unblocked python-aiosignal by adding python-pytest-asyncio to EPEL9. * Unblocked several openstack packages by adding python-ddt to EPEL9. * Resolved python-aiohttp installation issue by adding python-async-timeout to EPEL9. * Updated GitPython in EPEL7 to resolve issue with cloning large repositories. * Bump release of python-cheetah in EPEL7 to fix upgrade path from python-cheetah in CentOS 7 Extras. * Updated incompatible updates policy to reduce minimum time in testing from 2 weeks to 1 week to match regular updates policy. Kindest regards, CPE Team

1 0

FBR: Add nb to PAGURE_ADMIN_USERS
by Nick Bebout 28 Apr '22

28 Apr '22

I was working on a ticket mattdm filed about some spammers in Pagure. I'd like to add myself to PAGURE_ADMIN_USERS and run the Pagure playbook. PR here: https://pagure.io/fedora-infra/ansible/pull-request/1048 nb

3 2

FBR: update openshift ssl certs
by Mark O'Brien 27 Apr '22

27 Apr '22

Hi All, The certs for our openshift 3 clusters in both stg and prod are out of date. I have created new ones and I have a PR here to update the name in ansible: https://pagure.io/fedora-infra/ansible/pull-request/1045# I will need to run the proxies playbook to deploy these as well. I have also updated the ocp stg certs which are due to expire next week. +1/-1's welcome Mark

2 1

AWS auto deletion
by Mark O'Brien 26 Apr '22

26 Apr '22

Hi All, We will be launching a lambda function on Friday of this week which will help with the auto clean up of resources no longer needed in the Fedora AWS community account. The first iteration of the script will focus on EC2 instances, AMIs, EBS volumes and EBS snapshots. It is an "opt in" service. To use it all you will need is to create a tag called "Delete" with an integer value. For example if you created the tag "Delete": "30" The resource would then be deleted once it reaches 30 days old. The delta for Deletion is from the day the image was created not when it is tagged. So if you were to tag an image that was months old with 10 it would be deleted on the next run of the script not 10 days from now. Along with this I will be doing a manual cleanup of old resources in the account. I will take caution when deleting and may reach out to some people who I think could still be using the resources. If you have any questions feel free to ask here or reach out on irc/matrix. My nick is mobrien Thanks, Mark

1 0

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

25 Apr '22

Dear all, You are kindly invited to the meeting: Websites & Apps Team Meeting on 2022-04-26 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 of April 18th – 22nd
by Lenka Segura 22 Apr '22

22 Apr '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/?p=10955 # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-20-04-2022.pdf Update ------ ### Fedora Infra * A fasjson not issuing certs issue fixed. * New Mote dev app deployed to stg ocp4: https://mote-mote.apps.ocp.stg.fedoraproject.org/ * Normal freeze processing ### CentOS Infra including CentOS CI * Duffy deployment tests (for CI) * BAU (new tags, mirrors requests) ### Release Engineering * Finally fixed rawhide compose breakage (look for a blog from Kevin about it, it was a fun one!) * Waiting for RC requests * Fedora 36 and 37 openh264 binaries are uploaded to Cisco CDN ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * T-functional suite tests are in progress and the team are reviewing before merging https://github.com/AdamSaleh/sig-core-t_functional/actions/runs/2195767298 * New kernel being built and general updates to C7 & c8s are being worked on * Integration tests for (internal only) B.A.L.D service being developed, which is in a proof of concept phase. Fragile front end prototype stood up. Not ready for visitors. * New compose of c9s has landed in mirrors ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates ------- * Deployment preparation and tests * Test Ansible role and extend/fix * Implement and test (de)provisioning playbooks with bare metal nodes * Work on support for single node (de)provisioning playbooks ## Package Automation (Packit Service) Goal of this initiative ----------------------- Automate RPM packaging of infra apps/packages Updates ------- * Board created here: https://github.com/orgs/fedora-infra/projects/12 * First tasks are to create lists of all viable applications, we’ll then cross-reference this with our critical-path list for our starting points ## Flask-oidc: oauth2client replacement Goal of this initiative ----------------------- Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: -------- * Working on getting flask-oidc dependency update `python-authlib` 1.0.1 [0] into rawhide [1] and f36 [2]. * Refactoring [3] Flask-OIDC after finding a deprecation in itsdangerous * Looking at testing in staging later this week [0] github.com/fedora-infra/flask-oidc/issues/3 [1] bodhi.fedoraproject.org/updates/FEDORA-2022-5aa0b83b14 [2] bodhi.fedoraproject.org/updates/FEDORA-2022-bf96df773c [3] github.com/fedora-infra/flask-oidc/issues/4 ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 up to 2371 source packages (increase of 93 from last week) Now has more source packages than CentOS Stream 9 * EPEL Steering Committee approved an incompatible upgrade of ImageMagick in epel8 (soname bump) in order to resolve 82 CVEs meetbot.fedoraproject.org/teams/epel/epel.2022-04-13-20.00.html Kindest regards, CPE Team

1 0

Re: Fedora Contributor Tee Shirt Giveaway
by Sumantro Mukherjee 22 Apr '22

22 Apr '22

On Fri, Apr 22, 2022, 16:49 Sayak Sarkar <sayak.bugsmith(a)gmail.com> wrote: > Cool Stuff store says that the promo code has already expired! :( > Yep it was 24 hrs only. > On Fri, 22 Apr 2022 at 08:49, Chris Murphy <lists(a)colorremedies.com> > wrote: > >> I'm getting: There are currently no products linked to this invitation >> code... >> >> --- >> Chris Murphy >> _______________________________________________ >> test mailing list -- test(a)lists.fedoraproject.org >> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > > > -- > Homepage: http://sayak.in > About Me: http://about.me/sayak_sarkar > Twitter: http://twitter.com/sayak_sarkar > Blog: http://sayaksarkar.wordpress.com > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure April 2022