The CentOS Board of Directors is delighted to welcome two new directors - Davide Cavalca and Josh Boyer - to the Board.

Please join us in welcoming them, and thanking them for their willingness to dedicate some of their time to the endeavor of steering the CentOS Project.

Once again, we thank outgoing directors Karsten Wade and Carl Trieloff for their years of service.

(Yes, we're a little late this month. Sorry about that.)

Dear CentOS Enthusiasts,

Here's what's happening around the CentOS community lately.

CentOS Linux 8.4 Released

We are pleased to announce the general availability of the latest version of CentOS Linux 8. Effectively immediately, this is the current release for CentOS Linux 8 and is tagged as 2105, derived from Red Hat Enterprise Linux 8.4 Source Code. More details are available at

CentOS Stream Q&A at LISA '21

At the recent USENIX/LISA conference, Mike McGrath and Gunnar Hellekson hosted a Q&A session for discussion of what's happening in CentOS Stream, and other related topics around the CentOS community. The video is available on YouTube, and we welcome your further questions, which you can bring to any of our mailing lists or other public forums.

Topics discussed include proposed special interest groups (SIGs), the downstream rebuild projects, the various Free RHEL offerings, and many other things.

IRC Moving To Libera.Chat

Due to recent changes in the management of the Freenode IRC network, the CentOS project has decided to move our IRC presence off of Freenode over to the new network. The CentOS community continues to maintain a number of IRC channels for simple text-based discussion of a variety of topics around the project.

There are many IRC clients available, or, if you prefer, you can connect with the web client which Libera provides.

CPE Is Hiring

The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give.

CPE is hiring new talent to come work full time on Fedora and CentOS. You can read more details in their blog post, (two of the positions are already filled) or apply directly here:


Special Interest Groups (SIGs) are probably the most exciting part of the CentOS project, where people come together to do interesting things on top of the CentOS platform. There's been a lot of SIG activity in recent months, with new SIGs being proposed and approved.

SIG Process Review

Over the last few weeks we have been collecting feedback from SIG participants about the existing SIG process, and ways that we can improve it and make it more transparent and accessible to a wider audience.

The notes from that exercise are in THIS blog post, and will be the basis of some policy rewriting that the Community Architect will be doing over the coming months. If you're interested in being involved in that process, please watch the centos-devel mailing list for more information once that process starts.

Virtualization SIG

- upstream released 4.4.6 based on CentOS Stream 8
- oVirt within VIrt SIG released builds to CentOS Stream repos
- oVirt Spring 2021 survey results available: showing good adoption of CentOS Stream and growing interest in new distributions based on RHEL 8.

OpsTools SIG


Provide tools and documentation, recommendation and best practices for operators of large infrastructure.

Membership update

Sadly, we did not attract new volunteers to contribute to the SIGs purposes, but at the same time, we didn't loose any.


After initial euphoria setting up the SIG and getting to work, we can now observe a kind of settlement. We are still working on the upgrade of collectd to version 5.12. At the same time, and a bit related, collectd upstream has a CI issue we can not fix at the moment. Thus, there was a mirror organisation created and work is ongoing to establish a working CI there.

There is also an interest in investigating in loki as tool to allow multi-tenant log aggregation.

Following the lead of the CentOS project itself, we have switched our IRC channel over to

Issues for the board

Nothing to report.


Proposed: Kmods SIG

There's a proposal for a kmods SIG that will come before the Board of Directors next month. The proposal is now in the wiki, and available for your comments.

The kmods SIG will focus on providing kernel modules currently not available in CentOS Stream. If you have comments about the proposal, or want to volunteer to be involved, please bring your comments to the thread on the centos-devel mailing list.

New: CentOS Stream Feature Request SIG

In the May Board meeting, the CentOS Stream Feature Request SIG was approved, and they had their first meeting to discuss how things are going to work. The SIG exists to serve as a gate for feature requests that are first developed in CentOS Stream from contributors who wish to request these features to be included in future RHEL releases.

If you are interested in being involved in this SIG, or if you have changes that you are interested in getting in to either CentOS Stream or future RHEL releases, plan to attend the next meeting, which will be at 16:00 UTC on Tuesdays.

Rebuild Community News

Our friends in the Alma project recently announced their AlmaLinux OS 8.4 release.

And you can read the news from the Rocky Linux project HERE.

Get Swag

Want CentOS swag? We've got shirts at HelloTux, and caps and shirts at the Red Hat Cool Stuff Store.

Release for CentOS Linux 8 (2105)

We are pleased to announce the general availability of the latest 
version of CentOS Linux 8. Effectively immediately, this is the 
current release for CentOS Linux 8 and is tagged as 2105, derived 
from Red Hat Enterprise Linux 8.4 Source Code.

As always, read through the Release Notes at:  - these notes
contain important information about the release and details about some
of the content inside the release from the CentOS QA team. These notes
are updated constantly to include issues and incorporate feedback from

Updates, Sources, and DebugInfos

Updates released since the upstream release are all posted, across all
architectures. We strongly recommend every user apply all updates,
including the content released today, on your existing CentOS Linux 8
machine by just running 'dnf update'.

As with all CentOS Linux 8 components, this release was built from
sources hosted at Sources will be available from in their own dedicated directories to match the
corresponding binary RPMs.

Since there is far less traffic to the CentOS source RPMs compared with
the binary RPMs, we are not putting this content on the main mirror
network. If users wish to mirror this content they can do so using the
reposync command available in the yum/dnf-utils package. All CentOS
source RPMs are signed with the same key used to sign their binary
counterparts. Developers and end users looking at inspecting and
contributing patches to the CentOS Linux distro will find the
code hosted at far simpler to work against. Details on
how to best consume those are documented along with a quick start at:

Debuginfo packages have been signed and pushed. Yum configs
shipped in the new release file will have all the context required for
debuginfo to be available on every CentOS Linux install.

This release supersedes all previously released content for CentOS
Linux 8, and therefore we highly encourage all users to upgrade their
machines. Information on different upgrade strategies and how to
handle stale content is included in the Release Notes.

Note that older content, obsoleted by newer versions of the same
applications are trim'd off from repos like extras/ and centosplus/


We produced the following installer images for CentOS Linux 8

# CentOS-8.4.2105-aarch64-boot.iso: 677838848 bytes
SHA256 (CentOS-8.4.2105-aarch64-boot.iso) = 106d9ce13076441c52dc38c95e9977a83f28a4c1ce88baa10412c1e3cc9b2a2b

# CentOS-8.4.2105-aarch64-dvd1.iso: 7325042688 bytes
SHA256 (CentOS-8.4.2105-aarch64-dvd1.iso) = 6654112602beec7f6b5c134f28cf6b77aedc05b2a7ece2656dacf477f77c81df

# CentOS-8.4.2105-ppc64le-boot.iso: 722780160 bytes
SHA256 (CentOS-8.4.2105-ppc64le-boot.iso) = 4a83e12f56334132c3040491e5894e01dfe5373793e73f532c859b958aeeb900

# CentOS-8.4.2105-ppc64le-dvd1.iso: 8484990976 bytes
SHA256 (CentOS-8.4.2105-ppc64le-dvd1.iso) = 9cfca292a59a45bdb1737019a6ac0383e0a674a415e7c0634262d66884a47d01

# CentOS-8.4.2105-x86_64-boot.iso: 758120448 bytes
SHA256 (CentOS-8.4.2105-x86_64-boot.iso) = c79921e24d472144d8f36a0d5f409b12bd016d9d7d022fd703563973ca9c375c

# CentOS-8.4.2105-x86_64-dvd1.iso: 9928966144 bytes
SHA256 (CentOS-8.4.2105-x86_64-dvd1.iso) = 0394ecfa994db75efc1413207d2e5ac67af4f6685b3b896e2837c682221fd6b2

Information for the torrent files and sums are available at

Additional Images

Vagrant and Generic Cloud images are available at:

Amazon Machine Images for Amazon Web Services are published by ID into a
number of regions. A table of AMI IDs can be found here:

Getting Help

The CentOS ecosystem is sustained by community driven help and
guidance. The best place to start for new users is at

We are also on social media, you can find the project:
on Twitter at  :
on Facebook at :
on LinkedIn at :

And you will find the core team and a majority of the contributors on
irc, on in #centos ; talking about the finer points of
distribution engineering and platform enablement.


This release was made possible due to the hard work of many people,
foremost on that list are the Red Hat Engineers for producing a great
distribution and the CentOS QA team, without them CentOS Linux would
look very different. Many of the team went further and beyond
expectations to bring this release to you, and I would like to thank
everyone for their help.

We are also looking for people to get involved with the QA process in
CentOS, if you would like to join this please introduce yourself on
the centos-devel list

Finally, please join me in thanking the donors who all make this
possible for us.

Enjoy the fresh new release!

Johnny Hughes

Quorum and started at :05

Directors in attendance were:

  • Jim Perrin
  • Tru Huynh
  • Pat Riehecky
  • Mike McLean
  • Brian Exelbierd (Red Hat Liaison)
  • Thomas Oulevey (Secretary)

Others in attendance:

  • Rich Bowen (Community Manager, Chair)
  • Amy Marrich
  • Alfredo Moralejo
  • Josh Boyer
  • Davide Cavalca
  • Paul Isaac’s

Topic:  CentOS Stream Feature Request SIG approval

  • The SIG was approved. Closing issue [#33].

Topic: Departure of Board members and Board nominations

  • Cleaning up accesses from old board members. Tracking progress in [#44].
  • 6 nominations received. Nomination process is still open. Board is happy to keep the nomination process open for a few more weeks.
  • Candidates will be contacted in advance before names are published. Interview with the board will follow.

Proposal: Monthly meeting with the community to discuss board meeting outcome

  • Monthly meeting, scheduled for the week after a board meeting, where board members can discuss the meeting with the community
  • Approved, Rich will check the best format (IRC, other ?) and propose a timeslot.

Reviewed issues :

Adjournment at :38

Thank you to everyone who responded to my call for feedback on the SIG process. A few people responded on-list. More people responded off-list. I’ve summarized common complaints, and in a few cases provided comments verbatim - especially when they already went to a public list.

Please see the centos-devel mailing list for further discussion of what happens next.

The following areas were identified by one or more people as pain points in the SIG process.

Purpose of SIGs

Several people said that we do a poor job of communicating what SIGs are for, what should be a SIG, whether something should be a SIG or part of EPEL, and, in general, what the value of a SIG is.

When SIGs were introduced, they were meant to provide an incubator for projects in the CentOS space and also to provide infra/space to give projects a chance to CI test within CentOS, i.e "how does your project work on CentOS?" Has that focus been dropped? If not, would it be a good idea to reinforce the message?

We need to make it clear that Red Hat still has an interest in CentOS. That message would also be valuable for [Red Hat employees]. CentOS is an important place to put Red Hat’s “upstream first” message into action, but this often gets ignored.

Proposal process

Almost everyone said that the proposal process was vague and opaque.

It is unclear what the board is looking for in a proposal. While there is a template - - examples of good proposals, and what kind of specific things the board will look for, would make this process easier.

Access to the wiki to post the initial proposal is a bit of a chicken-and-egg - that is, without a SIG, who has authority to edit a wiki page for the SIG?

The deliberation/discussion of the proposal should happen on-list, not hidden/secret in board meetings. This will also give other potential projects insight into what they should be thinking about in their proposals.


Several people said that onboarding was confusing and undocumented, and seemed to assume you already know what you’re supposed to do.

Note: Several people specifically called out Fabian Arrotin as being extremely helpful in this setup process, with the caveat that he may not scale if we start getting more SIGs onboarding.

The “what’s next” after a SIG has been approved is very unclear. Once approved, what is the process for getting resources set up?

In the past, the SIG onboarding was often gated on one person, and getting their attention was difficult. This should be better with the new Infra sig.

One of the biggest hurdles is the repo setup (deciding on the cbs/koji setup, naming, setting up repositories for mirrors, etc). If you have never touched koji before, this is going to be tough for you. We need much better onboarding documentation for beginners, along with recommended best practices.

If you’re not a Red Hat “insider,” there’s a good chance that your SIG proposal will be ignored, or at least not given priority. The onboarding for [several SIGs] too more than a year - not because it was controversial, but because nobody prioritized it.

Ongoing communication

A number of respondents commented from the contributor side, about the lack of information/communication from SIGs.

The SIG wiki page says that quarterly reporting is required, but the majority of SIGs do not report, and there is no consequence for failing to report.

It is very difficult to find out from the SIGs themselves what opportunities there are for involvement. One respondent replied “I'd like to be more deeply involved in the [name] SIG. It's always a surprise to me how much I push to be a part of the group and how little opportunity there is.”  SIGs need to be much more proactive in what volunteer opportunities there are.

Some SIGs have weekly meetings, some monthly, and some never meet. This is very frustrating to people who want to get involved in the SIGs, but don’t know where to start.

Having an easier, documented way to contact a SIG with questions or offers of help is needed. Right now, we have out-of-date wiki pages with inaccurate lists of SIG members, and no way to contact them even if it was accurate.

SIG wiki pages must be updated with current information. They should also have a standard format, so that basic required information is always available.

Developer Experience

Several developers complained that they were just expected to know what to do, and not provided much guidance or advice as to how to proceed.

Clearer documentation (or pointers to documentation elsewhere) about package building, and how to set up a CI environment.

It would help if every SIG had the same buildroot setup, so that you know what to expect, and moving from one SIG to another was easier. This will increase cross-SIG engagement.

Developer experience on and CBS. Notably:

- the lack of a working PR workflow: and

- the way the lookaside works:

- hard to discover clone URLs:

- support for modularity in CBS:

The PR workflow in particular is problematic -- right now we rely on SIG members pushing directly to the repos, which makes code review difficult. It's also a blocker for external contributions (as, though one can technically put up a PR, there is no way to actually merge it).

I would love to have something closer to the workflow in Fedora. specifically:

- allow SIG members to review and merge PRs onto their branch

- kick off scratch builds on PRs to get signal

We need a way for  SIGs to publish structured documentation on, akin to the "quick docs" model that Fedora uses.

Missing -devel subpackages (I know this has been discussed a lot and fix is in progress).

I'd like to build, tag and push release rpms (as centos-release-openstack). In CentOS7 we could build and tag by ourselves (although it needed infra action to push). In CentOS8 we need to rely on CentOS infra to build and publish them in extras repos.


TL;DR: #centos and #centos-* are moving to

Over the past few days, there has been some upheaval on the Frenode IRC network, resulting in a number of the staff members quitting and starting a new IRC network. I don't wish to explain all the details here, but you can read more at which also links to other sources.

The various ops have discussed the situation, and we intend to migrate all of the various #centos-* channels from Freenode over to over the coming days.

This will take time, since libera is still spinning up, and some servers are moving from one network to the other.

As libera is still in the early stages of setup, you may have significantly more timeouts/disconnects, netsplits and other issues for now. Until the new network is fully stable, we'll all continue to be present in the Freenode channels.

Please bring further questions to the IRC channels, which you can join on

The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give.

See our wiki page here for more information:

We are hiring new talent to come work full time on Fedora and CentOS. The following positions are now open:

  • LATAM-based Associate / Engineer level, perfect for someone new to the industry or someone early in their career. We are looking for an infrastructure focused hire.

  • Associate / Engineer level in India. This is more a software engineering / DevOps focused role, perfect for graduates or people early in their career.

  • EMEA-based Associate Manager. We are looking for a people focused Manager to join our team to help with the people management workload. This is perfect for aspiring managers looking to move into their first management role or for anybody early in their people management career.

Please note that due to a constraint in how the jobs system works, a single country is nominated for the advertisement. Please kindly ignore that, two of the roles are available in the geographical regions outlined above.

We are looking forward to meeting you and hopefully working with you soon!

Hello, friends,

It's been another busy month in the CentOS Project, so we'll get straight to the news:

CentOS Stream News

Last week, Brian Stinson announced some updates on the progress towards CentOS Stream 9 on the centos-devel mailing list.

This included the availability of Stream 9 packages on Gitlab, and a koji instance where you can watch package build activity.

And on Thursday we announced that the CentOS Stream 9 compose infrastructure is available at if you want to try out very early builds of CentOS Stream 9.

If you're interested in contributing to CentOS Stream, you should start by registering for a Gitlab account.  We're in the process of updating the contributor guide, and that should be posted soon. Follow the centos-devel mailing list, and @CentOS on Twitter, to be the first to find out the next updates.

CentOS Dojo, May 13-14

The schedule for the upcoming CentOS Dojo is now posted. We'll be featuring two days of technical presentations around the CentOS project and community, including an "Ask me anything" session with the board of directors.

Other sessions include:

Thursday, May 13

  • New authentication platform for CentOS and SIGs
  •  What's new in FreeIPA 4.9
  •  Contributing to the CentOS Stream Kernel
  •  CentOS Stream on Desktop or: How I Learned to Stop Worrying and Love LTS
  • Hyperscale SIG update

Friday, May 14th

  • Board AMA
  • Keeping track of CentOS infrastructure deployments with Ansible and ARA
  • Thinking About Binary Compatibility and CentOS Stream
  • CentOS Stream CI: current state and future plans
  • Hands-on building an AMI pipeline using CentOS Stream 8 and cloud-init

Complete schedule and abstracts are available on the event site. The event will be online, and you will need to register (Free!) on the event website to attend. See you there!

@CentOSProject is now @CentOS

For the past few years, there have been two separate Twitter accounts for CentOS project news - @CentOS and @CentOSProject - and this has led to some confusion. We're pleased to announce that we've consolidated at @CentOS. If you were already following @CentOSProject, you've been automatically moved over to the @CentOS account. The @CentOSProject account will remain as a placeholder just pointing over to the official account.

Meanwhile, if you were following @CentOS to hear from Karanbir Singh, our long-time project lead, that account has been converted to @KaranOrg, where you can follow KB's technical musings and other thoughts around his work and life.

Board nominations open

As you may have seen in the April board meeting minutes, two directors have decided not to run for the upcoming board term. Both of these directors - Karsten and Carl - have served on the board for 8 years, and we have appreciated their service and dedication to the project.

That leaves two seats to be filled in the upcoming term. As per our governance documents, the board selects replacement directors. But the community is asked for nominations for these seats. If you're thinking of someone you think would be a good board member, or if you'd like to nominate yourself, please have a look at the requirements and responsibilities of a director, to see if this is something you (or the proposed candidate) would be willing to commit to. Then, submit your nomination via this Google Form. Thanks!

We're excited at the prospect of bringing new members, with new enthusiasm, to the board, even as we say a fond farewell to long-serving directors, and we look forward to your nominations.

Code of Conduct

We have been working with the Fedora project to draft a new code of conduct, and this was announced a few weeks ago. We expect to implement our version of it shortly after Fedora publishes theirs. We intend to take their final version and make necessary edits (ie, replacing 'Fedora' with 'CentOS' and other related changes) and are therefore waiting until they are done with all proposed edits. We welcome your comments on the centos-devel mailing list over the coming weeks as we prepare to make this change.

Red Hat Summit

Last week we were at Red Hat Summit, Red Hat's annual convention. CentOS had a steady stream of visitors in the CentOS/Fedora booth - thank you to all of you who came and talked with us.

There were a couple of sessions specifically about CentOS Stream - two "Ask the expert" sessions where attendees could ask their burning questions around CentOS Stream. These were very similar sessions, presented twice to make them convenient for people in different time zones. These were recorded, and you can watch them now, with free registration on the Summit platform.

CentOS Stream: Building an innovative future for enterprise Linux

If you have further questions about CentOS Stream, we encourage you to bring them to the centos-devel mailing list, or any of our various social media presences.

SIG reports

CentOS Special Interest Groups are smaller efforts around particular topics or technologies, to produce content on top of the base CentOS operating system. This month we have reports from a few of our SIGs.

Messaging SIG


Provide a unique source for messaging related packages. These packages are consumed e.g by the Cloud SIG or the OpsTools SIG.

Membership Update

We had talks with the RabbitMQ maintainers to get RabbitMQ packages included and updated.


Other than that, the nature of this SIG is to provide ... for other SIGs. The churn is not as big as in other SIGs.

Storage SIG

Repository Status and Updates

GlusterFS 9 was released; the glusterfs-9.1 bug fix update is available.

Ceph Pacific/16 was released; the ceph-16.2.1 bug fix update is available (c8 and c8s).

Bug fix updates to NFS-Ganesha (including libntirpc), Ceph Octopus/15, Ceph Nautilus/14 (c7 and c8), and Gluster 8 are available.

Ceph Pacific, GlusterFS 8 and GlusterFS 9, and NFS-Ganesha 3 (including libntirpc) packages are now built for CentOS 8 Stream. The associated release packages for those will land in CentOS 8 Stream soon.

Group Status and Actions from meeting

The storage sig meeting is moved to #centos-meeting2

Ceph Pacific is now available and can be consumed by other projects:

The OpenStack TripleO CI now consumes cephadm Pacific for both released and pending content -

Links and other general informations

Meetings agenda


Quorum and started at :05

Directors in attendance were:

  • Karanbir Singh (Chair)
  • Johnny Hughes
  • Jim Perrin
  • Tru Huynh
  • Karsten Wade
  • Pat Riehecky
  • Mike McLean
  • Brian Exelbierd (Red Hat Liaison)

Others in attendance:

  • Rich Bowen (Community Manager, stand-in Secretary)
  • Amy Marrich
  • Alfredo Moralejo
  • Matthias Runge
  • Josh Boyer
  • Davide Cavalca
  • Paul Isaac’s
  • Aoife Moloney
  • Brian Stinson

A welcome was given to guest Josh Boyer, representing RHEL engineering interests.

Topic: Board reappointment, and nomination of new directors

  • Open discussion should take place on public lists, with clear expectations that the vote happens in the board meeting, but that discussion, and nominations, are welcome from the community
  • Discussion of staggering (6 month offset for half of the directors) vs 12 months?
  • Two directors have indicated a desire to step down - Karsten Wade and Carl Trieloff - and need to be replaced. Their term as Directors will end effective April 30th, 2021.
  • Consideration: Maintaining the tension between “new blood” and continuity of leadership.
  • As we take this to the community, we need to be abundantly clear *what* we are asking of them, but early transparent discussion is preferred where possible.
  • Action: Discussion of how we address it if/when someone steps down. Interim board members to maintain above the minimum number of seats? Rich to write up proposals for solutions, to present to the board.
  • Board sentiment is not in favor of an “interim” member class, further differentiating between different directors.
  • Action: Proposal for “emergency election” for replacing a board member who steps down out of cadence. (Rich to add to above proposals.)

Discussion of development packages not provided in CentOS Stream: Red Hat is keenly aware of the desire to make buildroot packages available in the CentOS Stream project. Progress has been made on plans to enable this in some manner in CentOS Stream without requiring changes to Red Hat Enterprise Linux. The team is currently working to resolve some technical issues.

Discussion of CentOS Stream SIG proposal. and General support, but will take this to the mailing list and commit to timely response to this request.

Adjournment at :00

On 2021-03-10 the CentOS Board of Directors met to discuss ongoing business.

A  proposal to discuss the re-appointment of Directors has been presented by Karsten Wade. The document will be reviewed and it will be then proposed for approval during the next meeting. (More info on the governance updates in issues #22 and #24).

Rich Bowen, annouced that a new online Dojo is planned on May 13th and 14th 2021. All the details can be found at :

No other issue has been discussed this month, and updates will be amended to tickets if necessary.