CentOS Community Newsletter, August 2022

Friday, 26, August 2022 shaunm Newsletter No Comments

August 2022 Newsletter

Project News

Dojo at DevConf

CentOS hosted a Dojo at DevConf.US in Boston. This was our first return to hosting in-person events, and we tried to include remote participants with a YouTube live stream. Thanks to everybody who joined us in Boston or online. We appreciate feedback on how we can improve hybrid events. The recordings will be published soon.

SIG Reports

Each month, we publish a rotating selection of quarterly reports from our Special Interest Groups. This month includes reports from the Cloud and Storage SIGs.

Cloud SIG


Packaging and maintaining different FOSS based Private cloud infrastructure applications that one can install and run natively on CentOS.


Membership update

The OKD (OpenShift community edition) team contacted the Cloud SIG in order to know whether they could join our effort. Their contributors are looking for the best way to provide OKD along with SCOS (CentOS Stream CoreOS) images. As OKD and SCOS onboard into the community, it was suggested one of the contributors fill the vacant CloudSIG co-chair position.

Releases in the most recent quarter


Yoga is still the latest release. RDO community is about to package the next release named “Zed” in a couple of weeks, which will be supported on CentOS Stream 9 only. As a reminder Yoga is used as a transitive Openstack release with CentOS Stream 8 and 9 support, in order to be able to migrate the OS from one to another.

Health and activity

The Cloud SIG remains fairly healthy. However, it is still, for the most part, a monoculture containing only OpenStack.

Storage SIG

Package updates since the last report:

Note: Dependencies for Ceph Quincy (17) and earlier that are not in CoreOS, CBR/PowerTools, or AppStream are provided by the Storage SIG. Starting with Ceph Reef (18) those dependencies will be provided by EPEL instead. This includes Apache Arrow (libarrow), Apache ORC (liborc), and a rather lengthy list of other packages. This will simplify building dependencies by only requiring that they be built in one place. Many developers and end users also tend to prefer EPEL, and enable EPEL by default, and this will reduce or outright eliminate conflicts between packages in EPEL and packages in the Storage SIG. And no, Ceph itself will not be in EPEL; it will remain solely in the Storage SIG.

Following are the updates for Samba:

Issues reported:

Leave a Reply

Your email address will not be published. Required fields are marked *