July 2022 - devel - lists.centos.org

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redactions, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

Alternate Images - Proposed SIG
by Troy Dawson 04 Aug '22

04 Aug '22

Following the CentOS "Setting up a new SIG"[1] instructions I am opening a new topic about creating a new CentOS SIG. I have initially filled out several sections that are in other SIG pages. These are all open for discussion. Goals: The Alternate Images SIG's goal will be to build and provide alternate iso images for CentOS Stream. What is in Scope: - Live Images (Previously known as LiveDVD, LiveCD) -- Examples: --- Live Desktops (KDE / GNOME / XFCE / Mate ) --- Live Rescue - Alternate Install Images -- Examples: --- Minimum install iso (doesn't need the network, but almost as small as the boot.iso) --- KDE install iso (has epel enabled, and packages to install a working kde desktop) - Repo's that are compatible with CentOS Stream, and follow the Fedora licensing policy. What is not in Scope: - Containers - Raw / QCow / AWS - Iso images that are bigger than 4 Gig. (This number can be adjusted after the SIG is formed) - Repo's that are not compatible with CentOS Stream, or do not follow the Fedora licensing policy. Collaboration: We plan on working with various Desktop SIG's, the Fedora minimization team, and any other group that wants custom iso's. Deliverables: - Documentation along with configuration (kickstarts and scripts) that will allow members to create their alternate images. - Alternate images in a publically downloadable area -- Images will be rebuilt, or retired, a minimum of every three months. Leadership: I (Troy Dawson) will be the initial Lead of the SIG. After (or while) the SIG is formed we will decide if we want a co-chair leadership and/or how often the leadership is elected. Troy Dawson [1] - https://wiki.centos.org/SpecialInterestGroup#Setting_up_a_new_SIG

8 15

CPE Weekly Update - Week 30 2022
by Michal Konecny 29 Jul '22

29 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: 25th July - 29th 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-30-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-27.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * New Fedora Media Writer release (mostly translation fixes) 5.0.2 * Rabbitmq cluster instability last week due to both ocp3 and ocp4 clusters running monitor-gating and them obsoleting each other over and over. ;( * Worked around redhat.com SPF issue by accepting email from redhat.com, expanding fedoraproject.org alias and sending it right back out through redhat.com mx to deliver. ### CentOS Infra including CentOS CI * Preparing duffy.ci migration ([now announced for next week](https://lists.centos.org/pipermail/ci-users/2022-July/004582.html)) ### Release Engineering * F37 Mass rebuild finished ## 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 ------- * Imported c8s modules into the new mbs. * CentOS Linux 7.9 ISOs are respun ## 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 6986 (+378) packages from 3137 (+54) source packages * Backported fix for CVE-2021-21419 to EPEL8's [python-eventlet](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0… * Retired several rawhide branches of EPEL-only packages * Updated KDE (5.24.6) is available in epel9-next and epel8-next testing. * Will not go out to regular epel until RHEL 8.7 and 9.1 * Working on an EPEL survey that will go out in August ## 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 ------- * Basic repo structure in place (Python + JS side), more boilerplate work ongoing * Fedora-messaging schemas checkup commenced Kindest regards, CPE Team

1 0

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

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

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

24 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

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

23 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

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

22 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

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

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

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

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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2022