devel

devel@lists.centos.org

18 participants
4604 discussions

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

21 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 y Pere Campos pcampos(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 and Pere Campos pcampos(a)netwizzy.es. Best regards.

1 0

Stratis 3.2 Released
by Dennis Keefe 20 Jul '22

20 Jul '22

Hello all, The Stratis team is happy to announce that Stratis 3.2 has been released. Here are the release notes to Stratis 3.2: https://stratis-storage.github.io/stratis-release-notes-3-2-0/ Stratis 3.2.0 includes one significant enhancement, one bug fix, and a number of more minor improvements. Also, Stratis 3.2 also includes the features included in Stratis 3.1. Here are the release notes for Stratis 3.1: https://stratis-storage.github.io/stratis-release-notes-3-1-0/ Stratis 3.1.0 includes significant improvements to the management of the thin-provisioning layers, as well as a number of other user-visible enhancements and bug fixes. -Dennis Keefe

2 1

Storage SIG question
by Strahil Nikolov 20 Jul '22

20 Jul '22

Hi All, Does anyone know what will happen with the GlusterFS packages after Stream 8 EOL ?I'm wondering if the build system will keep building them for RHEL 8 or they won't be built anymore ? Best Regards,Strahil Nikolov

4 6

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

20 Jul '22

1 0

July board meeting recording and office hours
by Shaun McCance 19 Jul '22

19 Jul '22

Hi folks, I've uploaded the recording of last week's board meeting: https://youtu.be/2-okasyIv_Y If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, June 16, at 14:00 UTC. https://meet.google.com/nmy-babk-deh Email me directly if you need dial-in info instead. Thanks, Shaun

1 1

CentOS Hyperscale SIG meetup @ Dojo/DevConf.us 2022
by Davide Cavalca 13 Jul '22

13 Jul '22

Hello, The CentOS Hyperscale SIG will be holding an in-person meetup on August 16th, 2022 at Boston University. This is the same venue hosting CentOS Dojo on August 17th and DevConf.us on August 18th-20th. The meetup is open to everybody interested -- you don't have to be a member of the SIG to attend, and we'd welcome participation from anyone interested in this space. The event will be held from 9am to 5pm in the GSU conference room 310 at Boston University. While this is an in-person event, we will do our best to setup a conference bridge so that remote participants can attend and interact as well. Please register at https://www.eventbrite.com/e/centos-hyperscale-sig-meetup-dojodevconfus-202… to help with the event planning. Thanks! Cheers Davide

1 0

[Cloud SIG] Meeting Cancellation 07/14/22
by Joel Capitao 13 Jul '22

13 Jul '22

Hi everyone, The CloudSIG meeting planned at 1500 UTC on Thursday 14th July is cancelled. It will resume as normal on #centos-meeting channel at 1500 UTC on Thursday 11th August. In the meantime, you can add your topics in https://etherpad.opendev.org/p/centos-cloud-sig Regards, Joel

1 0

Board Nominations Requested
by Shaun McCance 11 Jul '22

11 Jul '22

** Please read this entire email before responding with nominations. ** We have a process, and the process is important. As per our governance docs: https://www.centos.org/about/governance/board/ Every six months, half of our directors are asked if they wish to continue in their seats or step down. This time, we will have one seat to fill. Tru Huynh has indicated to the board his intent to step down. Tru has been a part of this community for a long time, and we all deeply appreciate the work he's done both on the board and across the entire project. We are asking you, the CentOS community, for nominations for who should fill Tru's seat. Note that the vote on who will fill his seat is held by the board itself, but nominations are open to the entire community. If you would like to nominate someone (or self-nominate), please use this Google form: https://forms.gle/WsknUVnPL5zbWcSK6 Please DO NOT send nominations to this list. As this is not a public vote, we don't to give the impression of a popularity contest with public nominations. We also want to avoid any shaming if someone is nominated and is not seated, or chooses not to accept. I will ensure that each nominee is willing and able to serve, and the board will consider them and select the next director from the list. If you wish to nominate someone, you should consider the list of director requirements and recommendations listed at: https://www.centos.org/about/governance/director-requirements/ Thank you for your thoughtful consideration and participation in this process. -- Shaun, for the CentOS Board of Directors

5 9

Changes on CentOS CI and next steps
by Camila Granella 11 Jul '22

11 Jul '22

*TL;DR: CentOS CI is going hardwareless and if you wish your project remains using it, we need your opt-in by August 2022. There is a Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022> session happening on Thursday, June 17th, that will explain further technical details. * Hello everyone, As many of you know, since the beginning of this year we have been reevaluating the future of CentOS CI, as currently the hardware being used for it is out of warranty. This is due to the fact that CentOS CI came from community donations of hardware which were maintained in a best effort manner by our team. With no warranties, when the physical machine dies we have no means to replace it. Right now though, our hardware, due to a lack of warranty, will not be moved with the upcoming data center changes due to data center requirements to have in warranty hardware for supportability. We decided to take this opportunity to modernize our current infrastructure, pushing it to a hybrid cloud environment. Duffy CI will become the main tool from now on, so that we can support the CI workflow and best practices on cloud and for this reason, the current hardware infra will no longer be available soon. However, as an effort to continuously provide resources and support CI best practices for projects, our team is adapting Duffy CI so that we can maintain most of the characteristics of our current, physical-based offering. At the technical level, what does that mean for you, CI tenants? - A new Duffy API service will replace the existing one: while it will be running in compatibility/legacy mode with the previous version, you will need to adapt your workflow to the new API, but more details below - We will transition to AWS EC2 instances for the aarch64 and x86_64 architectures by default, with a (limited) option to request “metal” instances for projects requiring virtualization for their tests (like KVM/vagrant/etc) - We will keep a (very small) Power9 infra “on-premise” (AWS does not support ppc64le) for the ppc64le tests (available through a dedicated VPN tunnel) - The existing OpenShift cluster will be also decommissioned and a new one (hosted in AWS, so without an option to run kubevirt operator nor VMs) will be then used (you will have to migrate from one to the other) With that being said, tenants can start preparing for the changes to happen with the maximum deadline of the end of December 2022 wherein at this point, Duffy API legacy mode will be removed. You are required to opt-in if you and/or your team want to use Duffy CI. Projects will only be migrated if they reply to this email confirming that they wish to proceed. Worth knowing that not opting in means that your API key will not be migrated and so all your requests to get temporary/ephemeral nodes will be rejected by the new Duffy API. The maximum decommission deadline of the current hardware infrastructure is December 12th, 2022 and the new Duffy CI will go live in August 2022, so please, complete your migration process by the end of CY22. Reminders of deadlines and of the opt-in requirements will be sent monthly, but your confirmation of opt-in is required by August 2022. When approaching December, reminders about deadlines frequency will increase so that we can ensure effective communication throughout the process. Here are the steps in which we will migrate CI Infra: Phase 1 - Deploy Duffy V3 (August 2022) - Deploy in legacy/compatibility mode, so existing tenants (that opted in !) can still request duffy nodes the same way (like with 'python-cicoclient') : no change at tenants side, and exactly same hardware for tests (transparent migration) - New Duffy API endpoint becomes available, and tenants can start adapting their workflows to point to new API (new ‘duffy-cli’ tool coming, with documentation) - Bare metal and VMs options will be available already through the new API (x86_64, aarch64, ppc64le) Phase 2 - Hybrid Cloud (October 2022) - Legacy/compatibility API endpoint will handover EC2 instances instead of local seamicro nodes (VMs vs bare metal) - Bare metal options will be available through the new API only - Legacy seamicro and aarch64/ThunderX hardware are decommissioned - Only remaining "on-premise" option is ppc64le (local cloud) Phase 3 - Decommission (December 2022) - Legacy/compatibility API deprecated and requests (even for EC2 instances) will no longer be accepted - All tenants that opted in will be using only EC2 for aarch64/x86_64 and on-premise cloud for ppc64le OpenShift new deployment planning and timeline To be defined (deadline for planning and timeline: end of June 2022) Do not hesitate to reach out if you have any questions. It is worth knowing that there will be a dedicated session about the Future of CentOS CI infra at the next CentOS Dojo happening on June 17h (check Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022>). That session will be recorded and then available on Youtube but if you have any questions. Feel free to join the CentOS Dojo and reach out to us! Best regards, -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

3 3

CPE Weekly Update – Week 27 2022
by Michal Konecny 09 Jul '22

09 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: 4th - 7th 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-27-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 docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * Fas2 is scaled down to 0 instances since last week. Farewell! * Openshift3 is ready for retirement, will be taking it down later today * Got toddlers working in staging openshift * Email thread on infra-sig packages, please contribute * Koji hubs reinstalled with f36, and z/vm s390x builders upgraded to f36 * Business as usual items ### CentOS Infra including CentOS CI * Issue with mirrors and dnf being out of sync. PR merged today to fix * Mirror requests ### Release Engineering * A few rawhide compose issues, already fixed ## 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 ------- * Figured out the root cause of missing module components in CentOS Stream 8. Have a script to catch the cases, monitoring it. ## 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: -------- * Finally happy enough with our code, that we started to port it back into the flask-oidc library itself. * Working on a PR ## 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 (+92) packages from 2956 (+45) source packages * resolved "fails to install" bug for [xfce4-sensors-plugin-devel](https://bodhi.fedoraproject.org/updates/FEDORA-… * filed various "fails to install" bugs for epel packages * notable epel9 additions: * [chromium](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-002f30f0… * [python-paramiko](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0… (unblocks multiple other packages) 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