devel

devel@lists.centos.org

18 participants
4604 discussions

Planned outage : Duffy CI infra migration phase 1 on August 1st
by Fabian Arrotin 27 Jul '22

27 Jul '22

As previously announced in June (see https://lists.centos.org/pipermail/ci-users/2022-June/004547.html and also https://www.youtube.com/watch?v=aqgs-3NnRmA) we'll migrate existing Duffy API service to the new Duffy v3, starting with Phase 1 . Migration is scheduled for """"Monday August 1st 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-08-01 07:00 UTC') The expected API downtime will be under the 60 seconds (DNS TTL). Worth knowing: - new duffy api (in legacy mode) has currently less available nodes, but that will be resolved during the day (see below) - we'll have to wait ~6h (default maximum "lease" time for a test node) to be able to let new duffy api reinstall older seamicro nodes and so be available in the new duffy v3 pool (transitioning from old to new duffy pool) - currently running jobs will continue so to work, but when you'll hit new duffy api endpoint (DNS switch) to "return nodes" it will just answer that session doesn't exist (new one) but it's safe to ignore As soon as new duffy API is available you'll already be able to switch your workflow to new the Duffy API and so use the new features. Tenants/users documentation about how to interact with Duffy is available on https://sigs.centos.org/guide/ci/ (see the Duffy part of that documentation) That means that switching to EC2 nodes will be directly possible. During the day we'll tune the duffy nodepool configuration based on usage metrics. IMPORTANT remark : *only* projects/tenants that opted-in in the last 45 days are currently migrated (api and ssh keys), so if you haven't (yet), you can still opt-in, otherwise all your requests for duffy ephemeral nodes will be declined by new duffy api service next monday. In case of troubles, both Pedro (nick phsmoura) and myself (nick arrfab) will be also present in the #centos-ci irc channel on irc.libera.chat the whole day. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 19
by jlmartinez＠netwizzy.es 26 Jul '22

26 Jul '22

Hola, Estaré fuera de la oficina así que para cualquier cuestión por favor, dirígete a María José de Vicente mjdevicente(a)netwizzy.es. Muchas gracias y un saludo. Hello, I will be out of the office. Meanwhile, please contact María José de Vicente mjdevicente(a)netwizzy.es. Best regards.

1 0

Question on absence of SHA1 in OpenSSL 3.0/Centos 9 stream.
by Nickolay Olshevsky 25 Jul '22

25 Jul '22

Hi, Having SHA1 support removed from the OpenSSL in Centos 9 stream, it is still displayed in the list of supported digest, via CLI `openssl dgst -list` and via library API calls like `EVP_get_digestbyname()` and `EVP_MD_do_all_sorted()`. However, in some cases it would be desirable to know whether particular OpenSSL installation supports SHA1. So, the question - is it done this way by intention and I should look for some workaround, or it is something to get fixed in further package updates? Thanks! -- Best regards, Nickolay Olshevsky o.nickolay(a)gmail.com

2 1

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 18
by jlmartinez＠netwizzy.es 25 Jul '22

25 Jul '22

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 17
by jlmartinez＠netwizzy.es 24 Jul '22

24 Jul '22

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 16
by jlmartinez＠netwizzy.es 23 Jul '22

23 Jul '22

1 0

Wireguard and c8S headache - ?
by lejeczek 23 Jul '22

23 Jul '22

Hi guys. I asked wireguad's devel and the author explained the troublesome case of wireguard & c8S - without me going into depth of that - do you guys know how to get Wireguard work in 8 Stream? With "official" way with copr from "jdoss/wireguard-tools" module remains broken for last two kernel versions. many thanks, L.

6 7

KDE EPEL Roadmap
by Troy Dawson 22 Jul '22

22 Jul '22

After a lot of discussions, testing, trials, errors, patching and more testing, we have worked out the next phases of our KDE EPEL Roadmap. As a reminder, we are trying to do updates just once a year, corresponding with minor RHEL releases. This gives us the stability that Enterprise users expect, but with updates that will allow us to keep up with security / bugs / features. Current Versions: RHEL 8.6: Plasma 5.23.3 - kf5 5.88 - qt 5.15.2 RHEL 9.0: Plasma 5.23.5 - kf5 5.90 - qt 5.15.2 Next Versions: RHEL 8.7: Plasma 5.24.6 - kf5 5.96 - qt 5.15.3 RHEL 9.1: Plasma 5.24.6 - kf5 5.96 - qt 5.15.3 CentOS Stream 9 - The update to these new versions is currently in epel-next-testing. It should be in stable early next week. CentOS Stream 8 - The update to these new versions should be in epel-next-testing next week. It should be in stable in two weeks. For RHEL 8 this will probably be the last major update for Plasma. It will continue to stay on 5.24, which is an LTS release. The libraries in RHEL 8 are just too old for the newer Plasma's. Troy Dawson

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 15
by jlmartinez＠netwizzy.es 22 Jul '22

22 Jul '22

1 0

CPE Weekly Update – Week 29 2022
by Lenka Segura 22 Jul '22

22 Jul '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: 18th - 22nd of July 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-29-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-2022-07-20.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * New version of FMN released - removal of python-fedora requirement and all FAS2 calls * (almost) all builders reinstalled with f36 and bvmhosts moved to RHEL9 or Fedora36. There’s a few arm buildhw’s to be done after the mass rebuild. * FMN (py2) caught up finally, still needs fas2. Looking to switch to FMN (py3) soon. * Some recent rabbitmq / fedora-messaging cluster problems. Gave it more memory and hopefully it’s happy again. * Finally got *.fedoraproject.org ssl cert working with “FUTURE” encryption. * 5 new aarch64 machines and ½ new shelf of netapp storage arriving soon. ### CentOS Infra including CentOS CI * Mirror requests * Duffy migration tasks * Business as usual ### Release Engineering * Mass rebuild starts later this morning (Wed 20th) unless any last minute delays. ## 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 ------- * A Stream 8 compose has been pushed to correct some repoclosure issues with the kernel * Lots of PTO ## Package Automation (Packit Service) Goal of this initiative ----------------------- Automate RPM packaging of infra apps/packages. Updates ------- * Datagrepper is with packit * Mirrormanager2 in progress ## 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: -------- * Pull request is in https://github.com/fedora-infra/flask-oidc/pull/8 * Worked through the comments/suggestions from Aurelien * NEED EXPERIENCED TESTERS (to help write tests, need to update existing tests, scenario is complex, mocking out Ipsilon responses etc feel free to join) ## 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 is up to 6608 (+266) packages from 3083 (+127) source packages * Sponsoring of new packagers with interest in EPEL * Add python-tenacity to resolve ansible-lint fail to install bug * Notable package additions: * keepassxc * asciinema ## FMN replacement Goal of this initiative ----------------------- FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC. The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper. Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether. Updates ------- * Early days - pre-planning talks done today * Scoping/research/fact finding from the arc investigation https://fedora-arc.readthedocs.io/en/latest/fmn/april2022/index.html * Possibility of using Vue instead of React on frontend, typescript vs javascript also a possibility, FastAPI for the backend API Kindest regards, CPE Team

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel