May 25, 2020

[Video] CentOS Stream Contribution Workflow Demonstration

May 25, 2020 08:19 AM

(A presentation from Red Hat Summit)

In this video, we walk through the CentOS Stream contribution workflow, with an example contribution

See also for a quick overview of the contribution model.

See for more information about CentOS Stream


May 19, 2020

Deploying OpenShift 4 on bare-metal and disabling dhcp

May 19, 2020 10:00 PM

Recently I had to work with one of my colleagues (David) on something that was new to me : Openshift. I never really looked at OpenShift but knew the basic concepts, at least on OKD 3.x.

With 4.x, OCP is completely different as instead of deploying "normal" Linux distro (like CentOS in our case), it's now using RHCOS (so CoreOS) as it's foundation. The goal of this blog post is not to dive into all the technical steps required to deploy/bootstrap the openshift cluster, but to discuss of one particular 'issue' that I found myself annoying while deploying: how to disable dhcp on the CoreOS provisioned nodes.

To cut a long story short, you can read the basic steps needed to deploy Openshift on bare-metal in the official doc

Have you read it ? Good, now we can move forward :)

After we had configured our install-config.yaml (with our needed values) and also generated the manifests with openshift-install create manifests --dir=/path/ we thought that it would be just deploying with the ignition files built by the openshift-install create ignition-configs --dir=/path step (see in the above doc for all details)

It's true that we ended up with some ignition files like:

  • bootstrap.ign
  • worker.ign
  • master.ign

Those ignition files are (more or less) like traditional kickstart files to let you automate the RHCOS deploy on bare-metal. The other part is really easy, as it's a matter (with ansible in our case) to just configure the tftp boot argument, and call an ad-hoc task to remotely force a physical reinstall of the machine (through ipmi):

So we kicked off first the bootstrap node (ephemeral node being used as a temporary master, from which the real master forming the etcd cluster will get their initial config from), but then we realized that, while RHCOS was installed and responding with the fixed IP we set through pxeboot kernel parameters (and correctly applied on the reboot), each RHCOS node was also trying by default to activate all present NICs on the machine.

That was suddenly "interesting" as we don't fully control the network where those machines are, and each physical node has 4 NICs, all in the same vlan , in which we have also a small dhcp range for other deployments. Do you see the problem about etcd and members in the same subnet and multiple IP addresses ? yeah, it wasn't working as we saw some requests coming from the dhcp interfaces instead of the first properly configured NIC in each system.

The "good" thing is that you can still ssh into each deployed RHCOS (even if not adviced to) , to troubleshoot this. We discovered that RHCOS still uses NetworkManager but that default settings would be to enable all NICs with DHCP if nothing else declared which is what we need to disable.

After some research and help from Colin Walters, we were pointed to this bug report for coreos

With the traditional "CentOS Linux" sysadmin mindset, I thought : "good, we can just automate with ansible ssh'ing into each provisioned rhcos to just disable it", but there should be a clever other way to deal with this, as it was also impacting our initial bootstrap and master nodes (so no way to get cluster up)

That's then that we found this : Customing deployment with Day0 config : here is a simple example for Chrony

That's how I understood the concept of MachineConfig and how that's then supposed to work for a provisioned cluster, but also for the bootstrap process. Let's so use those informations to create what we need and start a fresh deploy.

Assuming that we want to create our manifest in :

openshift-install create manifests --dir=/<path>/

And now that we have manifests, let's inject our machine configs : You'll see that because it's YAML all over the place, injecting Yaml in Yaml would be "interesting" so the concept here is to inject content as base64 encoded string, everywhere.

Let's suppose that we want the /etc/NetworkManager.conf.d/disabledhcp.conf having this content on each provisioned node (master and worker) to tell NetworkManager to not default to auto/dhcp:


Let's first encode it to base64:

cat << EOF | base64

Our base64 value is W21haW5dCm5vLWF1dG8tZGVmYXVsdD0qCg==

So now that we have content, let's create manifests to create automatically that file at provisioning time :

pushd <path>
# To ensure that provisioned master will try to become master as soon as they are installed
sed -i 's/mastersSchedulable: true/mastersSchedulable: false/g' manifests/cluster-scheduler-02-config.yml

pushd openshift
for variant in master worker; do 
cat << EOF > ./99_openshift-machineconfig_99-${variant}-nm-nodhcp.yaml
kind: MachineConfig
  labels: ${variant}
  name: nm-${variant}-nodhcp
      config: {}
        tls: {}
      timeouts: {}
      version: 2.2.0
    networkd: {}
    passwd: {}
      - contents:
          source: data:text/plain;charset=utf-8;base64,W21haW5dCm5vLWF1dG8tZGVmYXVsdD0qCg==
          verification: {}
        filesystem: root
        mode: 0644
        path: /etc/NetworkManager/conf.d/disabledhcp.conf
  osImageURL: ""


I think this snipped is pretty straight-forward, and you see in the source how we "inject" the content of the file itself (previous base64 value we got in previous step)

Now that we have added our customizations, we can just proceed with the openshift-install create ignition-configs --dir=/<path> command again, retrieve our .ign file, and call ansible again to redeploy the nodes, and this time they were deployed correctly with only the IP coming from ansible inventory and no other nic in dhcp.

And also that it works, deploying/adding more workers node in the OCP cluster is just a matter to calling ansible and physical nodes are deployed in a matter of ~5minutes (as RHCOS is just extracting its own archive on disk and reboot)

I don't know if I'll have to take multiple deep dives into OpenShift in the future , but at least I learned multiple things, and yes : you always learn more when you have to deploy something for the first time and that it doesn't work straight away .. so while you try to learn the basics from official doc, you have also to find other resources/docs elsewhere :-)

Hope that it can help people in the same situation when having to deploy OpenShift on premises/bare-metal.

CPE Achievements during Q1 2020 (Jan-Mar 2020)

May 19, 2020 03:36 PM

Hi Everyone,

2020 has seen a lot of changes for everyone - understatement of the year right? One of these changes though has been how the Community Platform Engineering Team has decided to try adjust how they work. We are on an agile workflow journey and we began this year with quarterly planning, for the first time ever! We kicked off the start of the year working on some prioritised initiatives that we discussed as a review team during our first quarterly planning session. The review team included Brian ‘Bex’ Exelbierd, Paul Frields, Jim Perrin,Leigh Griffin, Pierre-Yves Chibon, Brian Stinson and Clément Verna.

The initiatives chosen to be worked on during Quarter One were:

  • FAS Replacement Login Phase 1 
  • Fedora Data Centre Move
  • CentOS Stream Phase 1 
  • CI/CD 

It was agreed that the CPE team would work on these from January - March 2020 as well as resourcing our sustaining team to support “lights on” work and Fedora & CentOS releases. 

And let us be the first to tell you, while it did not seem like it would be a monumental change from the outside from switching to  scheduling our work in advance rather than responding to ‘fire fire fire!’, it has been tricky to adjust to but we are getting there!

We had a Q1 celebration call hosted by our Agile Practitioner Sarah Finn to highlight the successes we achieved in that timeframe, and we were all a little surprised and a lot pleased with what we accomplished as a team 🙂

So, what did we achieve in this time?

CPE Sustaining team 

Team members: Clément Verna, Kevin Fenzi, Stephen Smoogen, Mohan Boddu

Michal Konecny, Vipul Siddharth, Tomas Hrcka, Petr Bokoc along with support from wider CPE Team/RH/Community as required.


  • Preparation for Data Center Move (Archives, Old Cloud retirement, Communication to Community)
  • Applications Update ( Bodhi, Anitya, mdapi, compose-tracker, fedscm-admin, python-cicoclient, …)
  • Fedora 32 Beta release infra and releng support
  • CentOS CI (Update of images used to run tests for Fedora)
  • Mbbox project start (Requirements, PoC, Dev Environment)

User Benefits:

  • Fedora 32 Beta release.
  • It is not too difficult to contribute to Fedora!

FAS Replacement Login Phase 1

Team members: Aoife Moloney, Aurelien Bompard, Rick Elrod (Jan- Feb), Ryan Lerch, Stephen Coady, James Richardson, Leonardo Rossetti along with support from wider CPE Team/RH/Community as required.

Achievements: : 

  • Registration page, user profile, user settings, user groups, groups list
  • 2FA & OTP authentication working
  • Fedora messaging is integrated
  • Users can reset their password when they have forgotten it
  • The FASJSON API is versioned and follows an OpenAPI spec
  • Theming support, with a Fedora and an OpenSUSE theme

Fedora Data Centre Move

Team members: Aoife Moloney, Stephen Smoogen, Kevin Fenzi along with support from wider CPE Team/RH/Community as required.

Achievements: : 

  • Minimum Viable Fedora offering defined
  • Future business growth for Fedora safeguarded in IAD2
  • COPR backups upgraded
  • Hardware budget approved and purchased 
  • Hardware inventory updated
  • Full Move schedule created and published
  • Impacted services list created and published

User Benefits:

  • Red Hat bought us some new stuff
  • New datacenter will provide better access to large cloud providers, and thus Fedora users using those providers.
  • Refreshed hardware should allow Fedora Infrastructure to meet growth needs for this year and beyond.
  • Planning and work should ensure outages for the datacenter move are as short as possible.

CentOS Stream Phase 1

Team members: Aoife Moloney, Brian Stinson, Fabian Arrotin, Johnny Hughes, James Antill, Carl George, Siteshwar Vashisht along with support from wider CPE Team/RH/Community as required.

Achievements: : 

  • Account creation in for Stream
  • Regular compose created & merged
  • Nightly composes running
  • Testing & QA suite running
  • List of packages available in Stream
  • Modules added to Stream
  • RPM signing tool written & implemented for CBS content in Stream
  • Workflow for contributor patches enabled
  • Stream is ahead of RHEL 8.1

User Benefits:

  • CentOS Stream releases ship like a tree and has nightly composes
  • Stream accounts are available on
  • QA and testing in Stream are finding issues quicker than in RHEL and CentOS Linux
  • 240+ packages are now available in Stream
  • There is a new signing tool written for CBS content


Team members: Aoife Moloney, Pierre-Yves Chibon, Nils Philippsen, Adam Saleh along with support from wider CPE Team/RH/Community as required.

Achievements: : 

User Benefits:

  • A backlog of ideas in the Fedora Infra and releng ecosystems can tackle to increase automation
  • The packager workflow is now monitored regularly and automatically
    • This will give us a way to measure the health of the packager workflow and in the long term potentially figure out the least reliable parts to improve them
  • Removing the changelogs and release fields from spec files allows for more automation around spec files and removes the two major sources of conflicts when doing pull-request on dist-git. This can be tested today in staging, allowing to gather more user feedback and experience before deciding on proceeding with this or not.

We have now had our second quarterly planning session for Q2, April - June, and if you want to check out what we are working on, stop by our taiga board to see our ‘in progress’ lane and read our blog post here. If you any questions regarding anything above or want to give us feedback, please reach out on our #redhat-cpe channel on IRC Freenode or mailing lists. 

And it is part for the course that when changes happen things get missed or overlooked, so this blog post is going out a little later than we would like, but we will try to have your next window wins published by the latest mid July. We just won’t say what year 🙂

Thank you everyone for your contributions to the above initiatives in our Q1, we had some great community engagement across our projects and we hope to have the same for the remainder of the year, because some things should never change 🙂

Take care everyone and see you around IRC!

May 18, 2020

[Video] CentOS Stream Contribution Model

May 18, 2020 08:51 AM

(A presentation from Red Hat Summit)

CentOS Stream is a rolling preview of the next minor version of Red Hat Enterprise Linux (RHEL), allowing you to try it out, and contribute changes into the RHEL development process. Carl George gives a brief overview of how that contribution model works.

See also for a walkthrough of a contribution. See for more information about CentOS Stream

May 15, 2020

Updated CentOS Vagrant Images Available (v2004.01)

May 15, 2020 06:40 PM

We are pleased to announce new official Vagrant images of CentOS Linux 6.10 and CentOS Linux 7.8.2003 for x86_64. All included packages have been updated to May 30th, 2019.

We are unfortunately not able to create images for CentOS 8.x om our build infrastructure at this time, but are working on this.

Known Issues

  1. The VirtualBox Guest Additions are not preinstalled; if you need them for shared folders, please install the vagrant-vbguest plugin and add the following line to your Vagrantfile:
    config.vm.synced_folder ".", "/vagrant", type: "virtualbox"

    We recommend using NFS instead of VirtualBox shared folders if possible; you can also use the vagrant-sshfs plugin, which, unlike NFS, works on all operating systems.

  2. Since the Guest Additions are missing, our images are preconfigured to use rsync for synced folders. Windows users can either use SMB for synced folders, or disable the sync directory by adding the line
    config.vm.synced_folder ".", "/vagrant", disabled: true

    to their Vagrantfile, to prevent errors on "vagrant up".

  3. Installing open-vm-tools is not enough for enabling shared folders with Vagrant’s VMware provider. Please follow the detailed instructions in
  4. Some people reported "could not resolve host" errors when running the centos/7 image for VirtualBox on Windows hosts. We don't have access to any Windows computer, but some people reported that adding the following line to the Vagrantfile fixed the problem:
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]

Recommended Setup on the Host

Our automatic testing is running on a CentOS Linux 7 host, using Vagrant 1.9.4 with vagrant-libvirt and VirtualBox 5.1.20 (without the Guest Additions) as providers. We strongly recommend using the libvirt provider when stability is required.


The official images can be downloaded from Vagrant Cloud. We provide images for HyperV, libvirt-kvm, VirtualBox and VMware.

If you never used our images before:

vagrant box add centos/6 # for CentOS Linux 6, or...
vagrant box add centos/7 # for CentOS Linux 7

Existing users can upgrade their images:

vagrant box update --box centos/6
vagrant box update --box centos/7

Verifying the integrity of the images

The SHA256 checksums of the images are signed with the CentOS 7 Official Signing Key. First, download and verify the checksum file:

$ curl -o sha256sum.txt.asc
$ gpg --verify sha256sum.txt.asc

Once you are sure that the checksums are properly signed by the CentOS Project, you have to include them in your Vagrantfile (Vagrant unfortunately ignores the checksum provided from the command line). Here's the relevant snippet from my own Vagrantfile, using v1803.01 and VirtualBox:

Vagrant.configure(2) do |config| = "centos/7"

  config.vm.provider :virtualbox do |virtualbox, override|
    virtualbox.memory = 1024
    override.vm.box_download_checksum_type = "sha256"
    override.vm.box_download_checksum = "b24c912b136d2aa9b7b94fc2689b2001c8d04280cf25983123e45b6a52693fb3"
    override.vm.box_url = ""


If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or in #centos on Freenode IRC.


I would like to warmly thank Brian Stinson, Fabian Arrotin and Thomas Oulevey for their work on the build infrastructure, as well as Patrick Lang from Microsoft for testing and feedback on the Hyper-V images. I would also like to thank the CentOS Project Lead, Karanbir Singh, without whose years of continuous support we wouldn't have had the Vagrant images in their present form.

I would also like to thank the following people (in alphabetical order):

  • Graham Mainwaring, for helping with tests and validations;
  • Michael Vermaes, for testing our official images, as well as for writing the detailed guide to using them with VMware Fusion Pro and VMware Workstation Pro;
  • Kirill Kalachev, for reporting and debugging the host name errors with VirtualBox on Windows hosts.

May 14, 2020

CPE Weekly: 2020-05-11

May 14, 2020 02:21 PM


The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here

GitForge Updates

* We are tracking our progress here (nothing new added yet, fyi)
* And the council are tracking the community issues in this ticket
* I have an Office hours IRC meeting slot on #fedora-meeting-1 @ 1300-1400 UTC every Thursday. Feel free to stop by and say hi! We can talk about Gitforge, or not 🙂 Note, this is an update to the meeting time from when this update was originally posted.

Data Centre Move

* Communishift is unfortunately offline until mid to end of June. The guys hit some unfortunate roadblocks which cost us a lot of time and energy. As we are starting to bring up hardware in IAD2 for the reduced Fedora offering next week, the hard but necessary decision was taken to pause bringing up CommuniShift in RDU-CC for now and come back to this once the  *slightly* more critical work is done or close to complete in IAD2.
* Thank you for your patience, this is a colossal undertaking for the team and your support and understanding is very much appreciated.
* Full amended schedule is here
* And updates are being posted here
* Again, as this project is currently being run by a two man team, we appreciate and thank you for your patience for delayed replies to tickets/requests/pings related to Fedora infra.

AAA Replacement

* The team have met with openSUSE and are supporting them when deploying Noggin
* Noggin UI improvements based on feedback have also been implemented
* Th2 team will begin to work on upstream code changes of existing apps to the FASjson api in their next sprint
* You can view the teams current, completed and backlog work here

Sustaining Team

* The team are using this dashboard to track their work
* They are also supportg the ELN work
* The ansible repo has also been moved to pagure!

* Mbbox Upgrade
* ssl fix is done
* The team are also working on CRD for koji-builder
* Work is being tracked here if you wish to view in more detail

CentOS Updates


* The team are working on
* Improving monitoring on CI agents
* Manual install of RHCOS bootstrap node on bare metal
* Importing EL6 Image for CICO cloud
* VMs migration from OpenStack to OpenNebula


* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and armhfp architectures. Including Cloud images (on - last week
* CentOS Linux 8.2 work is ongoing with compose level testing due to start soon

CentOS Stream

* The team are working through debranding CentOS Stream content from CentOS Linux
* Using CentOS Stream in the CentOS QA group to prep for 8.2

As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report.

Have a great week ahead!



May 12, 2020

[Video] What is CentOS Stream?

May 12, 2020 08:39 AM

(A presentation from Red Hat Summit)

CentOS Stream is a release from the CentOS Project. It’s an effort, along with the Red Hat Enterprise Linux (RHEL) engineering team, to increase transparency and collaboration around the RHEL development process. This video gives a little more detail about the what, why, and how of CentOS Stream

May 06, 2020

What’s coming up next in Fedora and CentOS infrastructure?

May 06, 2020 01:00 PM

As you may know, the Community Platform Engineering (CPE) team that helps manage both infrastructure for both Fedora and CentOS is trying to improve how the different initiatives or requests for changes we receive are planned and prioritized. This effort to improve has led us to look at planning our work in three-month windows. By planning, limiting, and focusing our work every three months, we can dedicate a substantial team around each initiative, driving it to completion before working on the next. Overall this helps us finish and deliver work faster.

The prioritization work involves the Fedora Council, the CentOS Board, a representative of the Red Hat Business Unit and the CPE team for each three-month window. Initiatives are considered against the team’s mission statement and weighed against each other to ensure that the most valuable initiatives are properly prioritized. This way of working  is quite new for us so any feedback on the overall process is greatly appreciated.

So, What’s coming up next (April - June 2020*)?

CentOS Stream (Phase 2)

In the next 3 months the team will be focusing on making CentOS Stream easier to consume and release. This means investing in automation of the packaging and compose processes. 

More information about this effort at :

Fedora Account System (FAS) Replacement (Phase 2)

This project is the second phase of the work that was started at the beginning of this year to replace FAS (which you may have heard referred to as “AAA”: Authentication, Authorization, Accounting). T first three months of the year were focused on building the web portal allowing users to register and manage their account. This phase will focus on the integration with other applications. Most of the work will be done in fasjson & fasjson-client.

More information about this effort at :

Fedora Data Centre Move

This is a big effort that in fact has already started and will continue for most of the next 3 months (current estimated end date for this is mid-July). The work will involve deploying critical infrastructure in the new data centre so that we can continue to build Fedora while the hardware is shipped from the old data centre. Then as the hardware arrives at the new location we will be working on redeploying the services and adding more capacity to that infrastructure.

More information about this effort at :

DNF Counting

This project will update and improve the current solution that gathers anonymous statistics about the number of installed Fedora systems by making use of the new DNF “countme” flag. This will help the project better understand how Fedora’s various offerings are used in the world, and give us better insight into the real-world lifecycle of our releases while taking great care to preserve our user's privacy. 

More information about this effort:

CentOS CI Infrastructure Phase 1

This work will allow us to update the current infrastructure used by from an OpenShift 3.x version to an OpenShift 4.x version. The goal of this work is also to build up more administration knowledge of OpenShift in the team as well as improving the performance and reducing the maintenance effort needed to run the current infrastructure.

More information about this effort:


The goal of this project is to make the current solution used to build rpms and modules for CentOS easier to maintain and update. The core of the work is to deploy koji and MBS using Kubernetes operators in order to manage the upgrade and deployment of new versions.

More information about this effort at:

You will find regular updates on our Taiga board relating to teams progress on each initiative. If you have any questions or if you want to know more about any of these initiatives or would like to contribute, please join our #redhat-cpe channel on IRC Freenode or visit the taiga links for more information.

In addition, a dedicated sub-team, the sustaining team, will continue to service the lights on operation work for CentOS & Fedora.

We recognize that this email/blog post is late, our 3 months window has started for a month already, as we said this is still a new process for us and we're still in the adjustment phase. Hopefully we'll do better in June!

May 05, 2020

CentOS Community newsletter, May 2020 (#2005)

May 05, 2020 04:07 PM

Dear CentOS enthusiast,

We hope you are all doing well and staying healthy, and, as always, thank you for being part of this great community.

In this edition:

  • News
  • Releases and updates
  • Events
  • SIG reports


After a great deal of work with Red Hat Legal, we are pleased to announce our new project licencing policy. This is an important step as we continue to move towards accepting more contributions in CentOS Stream  -

We're also delighted to welcome Pat and Thomas as new members of the CentOS Board of Directors - 

If you are involved in contributing to CentOS in any way, we ask that you take a moment to read the description of the work on SIG Authentication retooling -

CentOS Stream Updates:

CentOS Stream is working to get further ahead than in the past. Previously there were times when the content set of CentOS Stream reset to being ahead only with the Kernel and systemd. We recently pushed a batch of almost 100 source packages intended for the Red Hat Enterprise Linux 8.3 nightly development snapshots. Over the next period of time we expect to focus on pushing more batches into Stream until we're fully caught up with those nightly snapshots.

To give feedback on this content, you can open Red Hat Bugzillas directly against the CentOS Stream component.

CPE updates:

Our friends at CPE - Community Platform Engineering - have been posting weekly updates on their progress on the Fedora and CentOS infrastructure and engineering.

April 4th:

April 14th:

April 18th:

April 26th:

Releases and updates

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during April:

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during April:


Last week we “attended” Red Hat Summit, where we had a number of video presentations, and a well-attended “Ask The Expert” session with Brian Stinson about CentOS Stream. All of this content is available online. Go to (register for free and log in), then click “Explore” and you’ll see the Fedora/CentOS room there, with video and printed content about our projects.

We’ve also posted the videos to YouTube - - subscribe today to be notified when we post new content there.

Coming up, we have an AMA - Ask Me Anything - in the works for our Reddit community,  We don’t have a date confirmed yet, but we’ll be announcing it there, as well as to the other usual places - Twitter, Facebook, the Blog and the Forums - so subscribe to one or more of those places to find out when that’s coming.

We will soon be announcing our participation in DevConf.US, the annual developer conference. We intend to have a virtual CentOS Dojo as part of that event, and will be announcing our call for presentations soon.

SIG Reports

The SIGs - special interest groups - are where most of the interesting stuff in CentOS happens. They are communities packaging and testing layered projects on top of CentOS, and ensuring that they work reliably.

Cloud SIG Report


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

Membership Update

We are always looking for new members, especially representation from other cloud technologies.

No SIG members have been added in this quarter. However, the SIG membership list was updated on the SIG wiki page to reflect reality.

Releases and Packages


Aug 27 - Aug 31 Train Release

Interesting things in the Train release include:

Openstack Ansible, which provides ansible playbooks and roles for deployment, added murano support and fully migrated to systemd-journald from rsyslog. This project makes deploying OpenStack from source in a way that makes it scalable while also being simple to operate, upgrade, and grow.

Ironic, the Bare Metal service, aims to produce an OpenStack service and associated libraries capable of managing and provisioning physical machines in a security-aware and fault-tolerant manner. Beyond providing basic support for building software RAID and a myriad of other highlights, this project now offers a new tool for building ramdisk images, ironic-python-agent-builder.

Other improvements include:

Tobiko is now available within RDO! This project is an OpenStack testing framework focusing on areas mostly complementary to Tempest. While the tempest main focus has been testing OpenStack rest APIs, the main Tobiko focus would be to test OpenStack system operations while “simulating” the use of the cloud as the final user would. Tobiko’s test cases populate the cloud with workloads such as instances, allows the CI workflow to perform an operation such as an update or upgrade, and then runs test cases to validate that the cloud workloads are still functional.

Other highlights of the broader upstream OpenStack project may be read via

Jun 01 - Jun 05 Victoria Release Virtual Project Team Gathering

Health and Activity

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

Issues for the Board

We have no issues to bring to the board’s attention at this time.


[Video] What is CentOS?

May 05, 2020 08:36 AM

A presentation from Red Hat Summit: Community member Karsten Wade gives a quick overview of what the CentOS Project is.

May 04, 2020

CPE Weekly: 2020-05-02

May 04, 2020 02:25 PM


The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Check out our teams info here

GitForge Updates

* We are tracking our progress here (nothing new added yet, fyi)

* We are still doing a technical deep-dive with our own team on what we need from GitLab and will have a technical plan developed and publically available in the coming weeks - thanks again for your patience, this will take some time to map out.

* Fedora have also released a blog post

* And the council are tracking the community issues in this ticket

* We are looking at ways to engage closer with the community too so I will have an *optional* office hours slot on #fedora-meeting @ 1400-1500 UTC every Thursday. Feel free to stop by and say hi! We can talk about Gitforge, or not


* F32 released! Congrats to all those who helped make this such an awesome release

* Lenovo are releasing Fedora as a standard desktop offering!

* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and armhfp architectures, including Cloud images (on!

Data Centre Move

* Communishift is still out, est back online 11th May.

* Full amended schedule will be published week ending 8th May to hackmd & will be sent to the devel & infra lists.

* Connectivity is now in place in IAD2 and should be in place in RDU-CC over the weekend.

* In particular, a HUGE shout out to Stephen Smoogen who has been working all the hours in every day for the last few weeks/months to get this phase of the move operatoinal for the Fedora infrastructure - we would not be able to do this without you Smooge

* This is literally a two man team of Kevin Fenzi and Stephen Smoogen, who are carrying the weight of this infrastructure on their shoulders and are invaluable to the success of this multi-team and multi-month project, so thank you both.

* Given the pressures on the Infra folks, a general ask for patience if your ticket / request / ping takes a little bit longer to reply to

AAA Replacement

* The team will work with openSUSE to deploy FreeIPA + Noggin to deploy it in their infra before we do!

* This is really exciting and the team are looking forward to seeing how the solution works in another infrastructure!

* You can view the teams current, completed and backlog work here

Sustaining Team

* The team are using this dashboard to track their work

* Mbbox Upgrade

* Zuul CI set up is done

* Koji-hub TLS support added to CR

* Set up ReadTheDocs documentation - webhook missing for automatic build

* Identity container for testing

* Koji-builder CRD PR rebase - SSL authentication with koji-hub

* Refactor molecule test suite to share tests

CentOS Updates


* OpenShift upgrade

* OpenStack to OpenNebula migration scripts

* Ansible playbooks to manage the creation and bootstrapping of bare metal nodes with RHCOS

* Packaging work (fixing dependencies)

* Updated ci-user list on efforts we are putting for CI Infrastructure


* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and armhfp architectures. Including Cloud images (on -

CentOS Stream

* Congratulations to Brian Stinson on his excellent session of Ask The Expert, facilitated by Rich Bowen during Red Hat Summit - we hope you caught it, it was really good!

* Using CentOS Stream in the CentOS QA group to prep for 8.2 As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report.

Have a great week ahead!



SIG authentication retooling

May 04, 2020 06:05 AM

You may have seen the emails from Aoife about the work the Community Platform Engineering (CPE) team is doing around authentication tooling, and what that might mean for CentOS. Here’s a brief explainer for what’s happening.

The authentication software we use for SIGs (FAS or Fedora Account System) and a few other bits around the project will be EOL fairly soon. This is a 10+ year old, difficult to maintain software project with bugs that can’t be effectively addressed with its old code. The CPE team is writing a replacement for FAS that uses more of the standard distribution components, largely built around FreeIPA. This new tooling is intended to be an upgrade for use by anyone, but particularly Fedora and CentOS to replace both uses of FAS currently. There are a number of feature improvements and standardizations included in the new software, but in the end users shouldn’t notice any real impact in operation.

As we engaged with stakeholders including SIG chairs, the CentOS QA team, and other prominent community members, one issue became quickly apparent. We have many SIG contributors who push their work into both CentOS and Fedora, as well as Fedora’s EPEL repository. Having to work with separate auth systems makes it more difficult with automation, testing, and other parts of the contributor workflow. Because of this chance to improve the lives of our current and incoming contributors, our intention with the new authentication rewrite is for the CentOS and Fedora projects to share a single, unified authentication system. This would allow members of our communities who contribute in multiple places to do so via a single account, while having negligible impact on users who don’t. Group management, permissions, etc. will still be the purview of each project to manage as they see fit.

Fixing this gap between the auth systems the CPE team uses also solves some problems for the team itself. Sharing this system also encourages more cross-team work, which benefits both projects and communities (more hands). These communities are already sharing some resources, such as Fedora making use of the CentOS CI system. This work paves the way for easier resource sharing and management, which will cut down on the amount of duplicative work done across both infrastructures.

Over the next few months as the CPE team works toward its October implementation goal, you’ll see additional communication and messaging about the project. That doesn’t mean you need to wait to get involved though. If you’re interested in how we’re designing the auth, or want to participate in the development, please have a look at the git repository and see where you can help!

April 28, 2020

Release: CentOS Linux 7 (2003)

April 28, 2020 02:43 PM

We are very pleased to announce the latest release in the CentOS 7 series. The full release announcements may be seen on the centos-devel mailing list:

These releases were made possible due to the hard work of many people, and we thank all of them for their help as we move this platform forward.

April 27, 2020

New CentOS Project licensing policy

April 27, 2020 04:32 PM

Today the CentOS Project is rolling out a comprehensive licensing policy to document how licensing has been conducted normally in the Project, along with filling gaps that are crucial for being a contributor project. Your feedback and questions are welcome on the centos-devel mailing list. Please read the following for more detail and background.

One of the effects of adding CentOS Stream highlighted the fact we do not have any kind of clear policy about licensing contributions to the project. Obviously people have been contributing code and content to the project for a very long time, but none of those contributions went into the core Linux distribution. With CentOS Stream comes the need to manage a comparatively huge firehose of contributions needing clear guidelines and policies.

This gave us a chance to look at the state of the licenses the CentOS Project and its contributors put on code and content that originates in the project itself. Examples of this might be spec files for RPM packages, documentation on the wiki, or contributions to the branding of the project itself.

Presenting clear statements about how content and code is going to be licensed is a standard part of any open source project. The introduction of CentOS Stream has just raised the visibility of not having a licensing policy. The Board of Directors feels this policy better serves the needs of contributors and users.

An important purpose of this licensing policy is to provide a Default License--we’ve selected the MIT license--and a clear notice of attribution to the project under the MIT license. This Default License is used when a contribution does not have a license attached or is not destined for a repository that is already licensed, e.g. has a LICENSE file.

Otherwise, contributions are under the license of whatever is covering the rest of the content and code base--when you contribute to a software project repository, you put the contribution under the same license as the rest of the content and code in that repository.

This is also an opportunity to upgrade the version of our wiki license to CC BY-SA 4.0 for anything going forward; it is backward compatible with existing 3.0 content. This is a clean upgrade and improvement for the Project.

The CentOS Board of Directors received advice and drafting from Red Hat Legal in crafting this policy.

Your questions about this policy are welcome; the best place to discuss is the centos-devel mailing list.

April 20, 2020

CPE Weekly 2020-04-18

April 20, 2020 01:00 PM


The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Check out our
team's info here

GitForge Updates

We are still actively engaging with the Fedora Council and have not
made any further progress with this project. We are focusing on
ensuring we have captured the most granular of requirements before
further engaging with GitLab by rereviewing what we have gathered so
far and requesting more specific technical clarifications on some.
We are also as a team discussing the best way to track the updates on
this project publicly and hope to have something published early next
week. We will send an email to the devel list as soon as we have
agreed and created this.
Thank you for your patience and engagement with us thus far.

Fedora Updates

* Fedora 32 release: RC 1.3 was tested this week
* Go/No-Go meeting happened on Thursday 16th April - decision:No Go

Data Centre Move

* Please note Communishift is now down and is en route to the
datacentre in RDU-CC.
* We have a list of affected services that will be in effect from May
25th - July 1st (est) as part of the full datacentre move. You can
view that list here
* As always, please view our public schedule here for more a more
detailed overview

AAA Replacement

* The team officially kicked off phase two of the project development today.
* They are going to look at applications that currently use the FAS
client to change their codebase to the FASJSON client post production.
* The team are also working on adding a python library to the API so
that this maps to python objects easily.
* They are also working on API endpoints, specifically to be able to
retrieve the open-api specification in JSON format & provide a health
endpoint for monitoring tools.
* Our work is publicly tracked here if you want to find out more


* rpmautospec is available for testing in staging, find more info here

Sustaining Team

* The team are looking at creating a ticket dashboard for tickets and
have reused most the fedora-gather-easyfix code base to work on this

* Some cool stats about tickets from the infra repo here
* Mbbox:
* Review koji-hub CRD PR

Starting to play around with koji-ansible collections for releng work (here).
Automation of the openh264 packages.

CentOS Updates


* CentOS CI - stable with 0 downtime
* 7.8 QA tree is being tested by CentOS QA folks

CentOS Stream

* The team are working on having Stream be publically consumable in
the coming months, with SIG enablement so watch the devel lists for
more technical updates as and when they are announced!

As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.

Have a great weekend!



April 14, 2020

CPE Weekly: 2020-04-14

April 14, 2020 12:30 PM

# CPE Weekly: 2020-04-14

Hi All,

Apologies for the delayed weekly mail, I enjoyed a lovely four-day
weekend with my family over Easter which was important and didn't get
around to sending this email.

The upside is you get two emails from me this week instead

The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here

GitForge Updates

* Initial conversations have started with GitLab to investigate
options and weight them against more refined requirements to make sure
we reach the best possible outcome
* We are still engaging with Fedora Council
* We are also engaging with the CentOS board too
* And we are looking at ways to have open conversations/Q&A sessions
in public forums too as we move through this journey.

Fedora Updates

* F32 release first go/no-go meeting is scheduled for this week to
review the estimated release date of 21st April
* Calendar for meetings here
* F32 release schedule here

Data Centre Move

* CommuniShift is now down until May 8th est. to facilitate the data
centre move that has now officially begun.
* Please see our list of affected
* Our first few sets of hardware have been deracked and are awaiting
collection from PHX2 this week.
* Please check our schedule here - we are on Week 06

AAA Replacement

* The team are planning phase two of the replacement which will target
UX/UI improvements,


* rpmautospec
* Call for testers has been sent to the devel-announce list:
* Documentation is also being refined on:
* How it works
* What are its peculiarities
* How to opt-in
* What is working and what isn't yet
* What remains to do before this gets pushed to production
* Thank you for your feedback!

Sustaining Team

* Mbbox Upgrade
* The team are making good progress on the koji-builder & koji-hub
* They also have resolved the issue with PVC in the mbox-operator
* We are now looking into CI support and the work that this will involve
* Bodhi
* Investigation database lockups, seems related to celery worker
not completing their tasks
* Working on a 5.3 release
* Releng
* fedscm-admin 1.0.13 released
* Future openh264 composes will use ODCS, script is added to releng repo
* Infra
* The daily standup the team has has helped a lot with managing
infra tickets - they are down to 99 tickets!
* Mass update of stg and prod
* Please note you may experience some Kojira slowness
* New review-stats application deployed -

CentOS Updates


* CentOS CI is stable and all working fine
* Investigation for cloud vms addition to cico is also underway
* RHEL 8.1 batch update 07-Apr

CentOS Stream

* We have now ~200 packages built in CentOS Stream & we expect a few
hundred more to become available to us soon!
* The team are also still working on general compose config, koji tag
& housekeeping

As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.

Have a great weekend!




Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road

April 07, 2020

Welcome to our new Board members!

April 07, 2020 06:33 PM

The CentOS community, along with the Governing Board, is pleased to welcome two new members to the Board. Effective 8th April 2020, Thomas Oulevey and Patrick Riehecky will be joining the project leadership. (See also KB's announcement on the centos-devel mailing list.)

I spoke with Karsten Wade, who is a board member, about how the board selection and appointment process works:

"This is our first time doing this, and in planning it out, it quickly became apparent we didn't give ourselves a detailed roadmap back in 2014 with the new Project governance. The guidance was simply that the Board decides for itself who sits on the Board, candidates must have a body of work that benefits the CentOS Project and recognition as a leader in the community already, and we should review the make-up of the Board on a regular basis.


It turned out that such minimal guidance can be useful for remaining flexible, but it also meant we had to gut-check ourselves at every turn that we were following some kind of best practices. In the end, this time, we knew who we wanted and we just kept working things until we get there.


One of the activities of the Board in this coming year is going to be improving self-documentation, which I think will be a natural outfall requirement from the open goals refresh we're starting now that Thomas and Patrick are onboard. Our intention is to define CentOS leadership criteria as part of an open discussion process with the community. In the end, that is the true gift we gave ourselves back in 2014--the ability to operate in good faith under a set of governing principles that were good enough and the flexibility to evolve those principles when the time is right."

The two new Directors bring a wealth of experience and technical background to the table. They are also notable in that they come from two organizations which are actively involved in contributing to the project, and so they understand real-world interests and concerns.

Thomas Oulevey works in the Controls group within the CERN Beams department. As a system engineer he contributes his Linux knowledge to improve the exploitation of the Accelerator complex and technical infrastructure. Thomas has been contributing to CentOS since 2012, as a member of the infrastructure team. He helped to bootstrap few Special Interest Groups, helped the QA team with reports, and now mainly design and improve the Community Build Service.

Pat Riehecky works at Fermi National Accelerator Laboratory. He is part of the Scientific Linux team and works on systems that perform Data Acquisition for various experiments at Fermilab. Officially Pat began working with the CentOS Community when Fermilab decided to use CentOS 8 as its EL8 base platform.

We're particularly pleased to enter this period of greater transparency around the CentOS Project with two new directors from outside of Red Hat, to broaden our perspective, get more industry input, and amplify the voice of the community in our decision making process.

Please join us in welcoming Thomas and Pat.

CentOS Community newsletter, April 2020 (#2004)

April 07, 2020 01:58 PM

Dear CentOS enthusiast,

I hope you are all well. I know that this is a very difficult time for all of you, and that you likely have other things on your mind than CentOS, so I'll try to make it interesting this month.

In this edition:


We have had a fairly busy month in the CentOS project, with some exciting new developments on the contributor front.

Early in the month, Fabian announced a new CBS/SIG signing process. If you are in a SIG, or contribute in some other way, you'll want to read all about the updates to the workflow, which should make things a lot easier for you. And just a few days ago they announced that it was live, and tested, and ready for you to use. If you have questions, you should drop by the #centos-devel IRC channel.

Back in January, we talked about the decision of a Git forge platform. The CPE - Community Platform Engineering - team, which does a lot of the infrastructure work for Fedora and CentOS, listed requirements for selecting a platform that Fedora and CentOS could agree on, for shared collaboration. That decision has now been made, and you can read up on all the details in our blog post from the end of last week.

Over the past few months, areguera and others have been working on updates to our primary website, and a few days ago announced a staging website where you can see the progress of that project. See for how the new website is proposed to look, and take your comments (or, better yet, your contributions) back to the centos-devel mailing list.

The process to propose changes to the logo and our visual identity continues, and you should see THIS THREAD (and particularly responses thereto) for updates to how that process is going.

And I want to draw attention to the thread about Unshipped -devel packages in CentOS 8 and CentOS Stream which may address a concern that many of you have had in recent months.

Every week for several months now, Aoife Moloney has been posting the CPE Weekly to the centos-devel mailing list, keeping us appraised of what's going on in the Community Platform Engineering team to support the work of the CentOS project. This covers major projects like the data center move, and the AAA project, as well as daily CI/CD status and other smaller ongoing maintenance efforts. I strongly encourage you to read that each week, for some background on what's involved in keeping a project of this size moving along.

Finally, I want to make mention of the amazing work that's doing on in the Supercomputing community - much of which is powered by CentOS and Red Hat Enterprise Linux - to combat the corona virus using the power of HPC to simulate and test possible vaccines and cures. And if you want to participate in this effort with your spare CentOS computing power, have a look at the Folding@Home project which harnesses your spare CPU cycles to power the complex simulations of virus protein molecules.

Releases and updates

Errata and Enhancements Advisories

We issued the following CEEA (CentOS Errata and Enhancements Advisories) during March:

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during March:

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during March:

Track CentOS 8 and CentOS Stream package updates at


As you may already know, the upcoming Red Hat Summit has been converted to a virtual experience. What you might not know is that it is free to register for it. We'll be there, with video content, live "ask the expert" sessions, and a virtual "booth" chat room where you can drop by and ask questions, or learn about what we're working on.

The virtual event will be April 28-29, at Afterwards, all of the CentOS content we produce will also be available on our YouTube channel.

Beyond Red Hat Summit, we are carefully monitoring the coronavirus situation, and will decide on future events once the danger has passed. We're looking into how we can put on some virtual events over the coming months, particularly in cooperation with our friends in the Fedora project. If you're interested in participating, please do let us know.

Our in-person events are still very important to us, and we want to do more of them, not fewer. But we also have no interest in putting our community at risk. So, stay healthy, and stay tuned.

SIG Reports

CentOS SIGs - Special Interest Groups - are the lifeblood of the CentOS project, and the best place to get involved. These groups work on specific topics or technologies on top of CentOS. You can learn more about SIGs, and see which ones are currently available, at
Most SIGs hold periodic meetings on the #centos-meeting IRC channel, on Freenode, where they discuss what they're working on, what challenges they are facing, and where help is needed. Minutes are posted publicly after the meeting, so you can catch up on what was discussed.
The schedule for these meetings is posted at


April 04, 2020

CPE Weekly 2020-04-04

April 04, 2020 03:18 PM


The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Check out our teams
info here

GitForge Updates

*There has been a lot of discussion this week on the devel and infra
lists about the decision to move to GitLab in the near future.
Firstly, let us apologize again to the communities for our drop in
communication between the requirement collecting phase and the
decision making phase. As we have said before, it was in no way, shape
or form an intentional lapse of communications. However we do
recognize that it was still nonetheless a decision that was not made
in public, and for that we can only now offer our apologies for this
mistake and learn a hard lesson from it.

We do want to let you know that we deeply appreciate the requirements
you have given us and would like to ask you to continue engaging with
us while we are moving through our next steps with GitLab.
While the discussions on the lists are deeply emotional, they are
still incredibly valuable to us to truly comprehend the importance of
our next steps in ensuring we make the right choices in the coming

Now more than ever, your guidance is needed to make sure we achieve
the best possible result for you and our team from this decision.
CPE management and I, our team's product owner, are also actively
engaging with the Fedora Council and soon the CentOS Board to make
sure that ALL of the developments and progress between us and GitLab
are publicly available.

We have a long way to go in this process and your feedback on our
progress will be vital to make sure we remain on course.

We hope in time you can understand our decision was made in good
intent for the betterment of both our team and the communities we
serve, and we hope to still be able to rely on you all as peers and
friends for feedback and guidance during this journey.*


* CentOS CI is stable with 0 downtime!

* RHEL 7.8 released this week too!

CentOS Stream

* qt5, go-toolest (module), container tools (module) are updated to
their 8.2 versions

* We are also looking at easier automation of koji tags

Fedora Updates

* Final Freeze starts 7th April 2020 @ 1400 UTC

* Pagure 5.9.1 release pushed to both staging and

* the-new-hotness configuration was updated

* Michal Konečný has been working on mapping the fedora infrastructure
applications, his project, (which sounds really cool and useful!) can
be found here

Data Centre Move

* Please note Communishift will be down from 13th April - 8th May to
facilitate the first shipment wave of our datacenter

* We are also still on track to switch to a reduced Fedora offering
from 25th May until est. 1st July\*.

* For a list of services we are planning to have available during this
window, please see mail thread in archive

* We will not have staging available so we will not have capacity to
review or deploy new or upgraded features and applications during this

* As always, please view our public schedule here for more a more
detailed overview

* We found a password, we do not know whose it is, but we have turned
it into the lost and found.

AAA Replacement

* First development phase complete & the team worked through 57 tickets in total

* The codebase was sent to our team first for demo and we will be
using feedback to develop the portal further

* During phase two we would like to change some codebases in existing
apps, and write documentation on how to upgrade applications to
redirect to the new API

* We would like to roll this request for feedback out to some
community maintainers during this phase too for another iteration on
the service and documentation

* Our work is publicly tracked here so please stop by and
check out the progress we are making, and what we are looking at
working on next


* Monitor-gating is still running in production and giving us some
data about the health of the packager workflow:

* For example, these are the statistics between Monday and Wednesday:
39 messages retrieved
prod.monitor-gating.multi-build.end.failed -- 7
prod.monitor-gating.multi-build.end.succeeded -- 2
prod.monitor-gating.multi-build.start -- 10
prod.monitor-gating.single-build.end.failed -- 3
prod.monitor-gating.single-build.end.succeeded -- 7
prod.monitor-gating.single-build.start -- 10

* rpmautospec 0.0.1 through 0.0.10 have been released and deployed in staging

* We got two builds to go through fine, from the same commit,
getting two different NEVR and an auto-generated changelog

* However, for this to happen, we had to tweak a couple of things
on the builder which is not really ideal/acceptable, so we moved a
part of the processing inside the chroot where the SRPM will be built,
which solved the main issues we faced

* To be done: Make tagging (latest) existing builds a separate
operation executed outside the build root, to avoid having to talk to
Koji inside it.

* In other words: Stay put, we're getting there!

Sustaining Team

* Mbbox

* The team have made some progress on koji-builder CRD

* The team are also working on Bodhi 5.3 with few improvements and bug
fixes from 5.2.

* The team had a reboot and Update cycle this week.

* The team are also discussing ideas around a releng bot to help
process the tickets that require manual interventions.

* They also add more updates to compose-tracker

* And started playing with odcs on new

As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.

Have a great weekend!



March 28, 2020

CPE Weekly: 2020-03-28

March 28, 2020 03:21 PM


The Community Platform Engineering group 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.

For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.


* ppc64le and aarch64, 8 and 8-stream nodes now available in cico for
tenants to checkout. -- Email sent to ci-user list

* New signing for SIGs (through live this week!

CentOS Stream

* Qt5.12 pushed in response to an internal request
* NetworkManager re-imported

Fedora Updates

* Freeze is over!

* New version of pagure (5.9.0) has been released and deployed in
staging and on

* Document being worked on about how to onboard new CI systems in
Fedora - this is a work in progress!

Request for Review

* Fedora magazine: Article proposals about Silverblue rebase to F32

* Packit integration in the-new-hotness

* KeepassXC flatpak issue

Data Centre Move

* Communishift will be unavailable from 2020-04-13 until 2020-05-08

* Check out our detailed move shedule here

* Covid-19 has seen restrictions added to the data centres we are
moving from and to, however we are unaffected as of yet for the move.

* If or when our timelines become affected, we will inform you
immediately of any outages, downtimes, etc a delay could cause.

* Thank you for your understanding at this particularly uncertain and
worrying times.

AAA Replacement

* We are nearly complete in our phase one development!

* Below are some of the features the team have developed since
beginning the project in mid-Jan

* UI where people register and login

* Add groups function

* Change personal details

* Enroll OPT

* Reset password

* View group owner details

* Use a search engine

* Our next steps in this project is to demo to the team for feedback
and then continue to develop CentOS authentication, more user focused
features, request for more feedback and test, test test!


* Monitor-gating is now running in production and has already caught a
couple of issues with bodhi (both in stg and in prod)!

* Rpmautospec

* This is in review as a Fedora package:

* Work progressing on Koji tagging plugin (post-build), full use
case support for bumping releases

* The team hope to deploy this in staging soon!

Sustaining Team

* Mbbox

* Some progress on CRD for koji-builder and koji-hub components
has been made this week

* Bodhi 5.2.2 released

* Some issues with celery tasks & rawhide monitoring has been
super useful with this.

* Compose Tracker enhancement

* Tagging issues have been resolved

* Ability to ping maintainers

* Fedora Minimal Compose

* Odcs-backend-releng01 has been provisioned to enable testing

GitForge Decision

* After evaluating over 300 user stories from multiple stakeholders we
have aligned on a decision for the Gitforge that CPE will operate for
the coming years. We are opting for Gitlab for our dist git and
project hosting and will continue to run with community

* Check out our GitForge decision on the Fedora Community blog

* And at the CentOS blog page

* Keep an eye out for mails in the coming months to the devel lists as
we plan transitions and next steps with GitLab

* We would like to express our sincere thank you to all who
contributed requirements to us!

As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.

Have a great weekend!



March 27, 2020

Git Forge decision

March 27, 2020 05:01 PM

After evaluating over 300 user stories from multiple stakeholders we have aligned on a decision for the Gitforge that CPE will operate for the coming years. We are opting for Gitlab for our dist git and project hosting and will continue to run with community assistance.

Analysis and recommendation:

A lot of comments and concerns were raised about the suitability of Github as a forge of choice. The preference from all stakeholders (Fedora, CentOS, RHEL, CPE)  is that Github is not a contender and not a preference, with that in mind, we have decided to not analyse it as an option and respect the wider wishes of our stakeholders. Therefore the rest of this analysis focuses on Pagure versus Gitlab as our choice.

Looking at the user story list, we have a picture of a standard set of practices that users expect to have from a Gitforge. The basics of storing code, accessing it, merging, forking and the traditional git workflow are satisfied by both Forges under investigation. 

A key requirement coming to us is security. The need for HTTP/S pushes, the need for more stringent branch control via protected and private branches is a key operating requirement of the CentOS stakeholders. The need to interface with internal and external users in a private capacity whereby embargoed content can be worked on in private is a necessary requirement. 

Another key requirement is usability and accessibility. It is clear that our current forge solution is used as a mixture of ticket tracker, work planning, code repository and storage of documents and other artifacts. The barrier to usage needs to be low to attract drive by users and a strong representation was made for the need to have more accessible ways to interface with the system from a GUI to a command line client.

Developer centric needs came from multiple sources. Integrations with daily workflow, integrations within the IDE, integrations in an always ready and always on approach (SLA requirements were high) as well as the ability to use the forge as a means to improve the codebase (auto notifications of issues, interactive PR reviews etc.) and way of working by providing analytical output was also raised.

A big factor in a decision here needs to be both the immediate usability to meet stakeholder needs that includes an immovable deliverable for CentOS Stream which CPE must deliver by the end of the year. 

Another major factor is the stability, availability and responsiveness of the platform chosen. While no Forge meets the full suite of requirements, the issue of stability, availability and some of the richer features that were requested are currently not available in Pagure. Gitlab provides the most feature rich experience out of the box and the recommendation of the CPE Management is to opt for Gitlab as our chosen Forge for dist-git and general project hosting. For we want to offer it to the community to maintain. CPE would provide power and ping and the rest of it will be up to the community willing to do the work. If no-one steps up to pick the maintenance of, it will be a candidate application to sunset. Some top level requirements which helped us arrive at this decision:

  • There is a need for CentOS Stream to integrate with a kernel workflow that is an automated bot driven merging solution (merge trains). This allows for richer CI capabilities and minimizes the need for human interaction
  • Gitlab provides subgroups allowing for more granular permissions for repos
  • Gitlab allows for project planning capability which could make multiple trackers such as Taiga redundant, allowing for the planning and tracking to reside within the repo. It would enrich the current ticket based solution that Pagure has evolved into for some groups
  • 24/7 availability in an SLA model and not hosted by the CPE team freeing up resourcing and removing the need to staff a dedicated team for a Gitforge SLA which would necessitate a follow- the- sun Ops model and a heavy investment in stability and observability of the Pagure solution.

The opportunity cost to invest our finite resources into bringing Pagure up to the minimum standard that we require by the end of the year would mean feature starving both Fedora and CentOS for the next 18-24 months as we strive for the optimal standard. As a team, we spend 40% of our available resources on keeping the lights on day to day with a very small amount of that improving our technical debt situation. We are spending 30% of our team on delivering CentOS Stream. The available bandwidth for the team is not at a point that we could safely and with confidence deliver the required features to make Pagure work as our Forge of choice. It additionally would have a longer term impact with our lights on work needing to expand to move Pagure to an SLA, tilting our resourcing plan for that body of work towards 60% of our capacity. We feel this is not a responsible decision that we can make as the inward investment in a Forge is not something that we can do at the expense of planned initiatives that are on our backlog. Some of them include a better packager workflow, more investment in CI/CD to remove CPE from manual work and empower the community to do more things in our infrastructure, more observability and monitoring of our infra and services, movement of services towards the Cloud to make use of a modern tech stack and that's before we consider immovable service progression that we simply have to undertake, for example, the new Auth / AAA system.

However, we do not want to abandon Pagure and our plan going forward is thus.

  1. Offer the maintenance of to anyone in the community interested in leading it.
  2. Engage with Gitlab on the possibility of a SaaS offering so that CPE can attain key requirements of uptime, availability and throughput as well as ensuring tooling integrations (such as Fedora Messaging among others) are preserved. Legal considerations with respect to control of code will be our first discussion point with them enabling us to make a SaaS Vs self hosted decision.
  3. Keep Pagure running with our oversight while we analyse a sunset timeline which will give a minimum of 12 months notice once we have a plan firmed up. We will fix blocker bugs, address critical vulnerabilities and keep the lights on in the same manner that we have committed to over the last 14 months where Pagure has not been a staffed and supported initiative.
  4. Where possible, when we have to update our tooling, we will attempt to refactor our tooling to be forge agnostic, allowing our Communities the choice of storing their code on Gitlab or continuing to use
  5. Watch closely for collaboration with other Communities on Pagure and provide them with guidance and oversight to help the Pagure Community grow. We recognise that this is a growing and unique ecosystem and we genuinely want to see it succeed and will do our best to support it in that capacity. To that end we will publish the roadmap difference between Pagure and Gitlab to allow the Community to focus on feature enhancements to bridge that gap.
  6. Facilitate our Communities and assist them in standing up a version of Pagure that can be driven and maintained by the Community allowing a pure Open Source principles approach for those who seek it.

We recognize how difficult a decision this is and we empathize with the emotional attachment to Pagure. It is why we want to have a mutually beneficial approach to ultimately allow Pagure to grow and flourish and allow our community members to setup and work with any Forge they wish. This ultimately allows the CPE team to focus on adding value to a greater scale of initiatives  . This approach allows us to focus on value added services and initiatives that will benefit a large percentage of our communities instead of focusing on a singular foundational service which would ultimately consume our finite resourcing and limit our impact on both Communities.

-- Jim and Leigh

March 18, 2020

CentOS 8 and CentOS Stream updates, and

March 18, 2020 04:10 PM

Over the past few weeks we've gotten questions on various forums - email, Twitter, IRC, and so on - about why there are no mentions of CentOS 8 updates, or CentOS Stream updates, on the centos-announce mailing list.

For those not familiar, centos-announce is were we tell you about security and bugfix updates that have been released. And, if you look at the archives, you'll notice that everything refers to CentOS 6 and CentOS 7.

This is not because nothing's happening with CentOS 8 or CentOS Stream. It has more to do with the tooling that generates those mailing list posts, which is all automated.

As was discussed in this blog post, many of the scripts that work fine with 6 and 7 don't work with the new 8 flow, and one of those is the script that produces the mailings that go to centos-announce. And with everything else that the team has been working on, it just hasn't (yet) been a priority to fix that.

This doesn't mean, however, that you have to fly blind. There is a service that lists all of the new packages that are flowing - what's in them, and what was changed. That service is and it provides RSS feeds of what's been updated.

A typical entry might look like:

Thu, 27 Feb 2020 16:44:39 GMT: ppp-2.4.7-26.el8_1.x86_64

ppp - The Point-to-Point Protocol daemon

The ppp package contains the PPP (Point-to-Point Protocol) daemon and
documentation for PPP support. The PPP protocol provides a method for
transmitting datagrams over serial point-to-point links. PPP is
usually used to dial in to an ISP (Internet Service Provider) or other
organization over a modem and phone line.

Change Log:

Tue, 25 Feb 2020 GMT - Jaroslav Škarvada <> - 2.4.7-26
- Fixed buffer overflow in the eap_request and eap_response functions
  Resolves: CVE-2020-8597

Tue, 04 Dec 2018 GMT - Jaroslav Škarvada <> - 2.4.7-25
- Fixed some issues found by coverity scan
  Resolves: rhbz#1602665

Tue, 20 Nov 2018 GMT - Jaroslav Škarvada <> - 2.4.7-24
- Split out the network-scripts
  Resolves: rhbz#1608377


It shows what was updated, and a few of the most recent changes to that package.

Each repo that we're pushing content to has its own RSS feed.

For those of you who don't enjoy reading raw RSS files (and, really, who does?) I've written a little bit of python for my own convenience, which you're welcome to use. This script - - parses all of those RSS files (comment out the ones you don't care about) and tells you what changed since the last time you looked at it. Output is captured in text and html formats for your perusal.

March 16, 2020

CPE February Updates

March 16, 2020 06:53 PM

CPE - Community Platform Engineering - is the engineering group within Red Hat which does a lot of the behind-the-scenes work that makes the CentOS and Fedora projects possible.

CentOS Stream Project Update 2020-02-28

We would like to welcome you all to our first blog update on the CentOS Stream initiative. Over the course of this initiative, we will share regular updates on our plans, our progress and our deliverables. The CentOS Stream team is currently working within a Scrumban framework broken down into two week blocks. This allows the PO and team to plan and prioritise work for each block allowing stakeholders to gain updates on progress, plans and deliverables each fortnight. Each fortnight, stakeholders will review the block deliverables and provide feedback to be taken into consideration when planning the next block. Ensuring that CentOS Stream is delivered in line with changing requirements and expectations as the project build progresses.

The CentOS Stream team has made significant progress throughout February where their focus was on the cornerstone foundational build phase. Block 1 and 2 (2020-02-03 to 2020-02-21) delivered:

  • Nightly composes:
    • Reports are being generated internally for now until a bug fix has been resolved
  • CentOS QA can consume composes and the test suite can now run against both Stream and Linux
    • This has also caught three issues that would have made it to downstream otherwise
  • The module for Stream this week is PHP:7.2
    • This is ahead of 8.1 in RHEL
  • Accounts in are created

Block 3 deliverables were identified and are currently in progress. See below:

  • Push to Git process being developed
  • Scaffolding up to watch brew tags
  • Python:3.8 is expected to be the next module for Stream*
    • This is dependant on a bootstrapping task relating to upstream updates that come from CentOS Linux to Stream
    • Information gathering with package maintainers on package lists around debranding/rebranding for future upstream & downstream use

AAA: FAS replacement project update 2020-02-28

The month of February was a very busy month for the CPE AAA team and community contributors working on this initiative. Great progress was made in the development phase of the AAA: FAS replacement build. Sprint 2 and 3 resulted in the completion of multiple user stories which added user functionality to join groups, change email address and password, disable account, database access along with putting a mapping solution in place for users moving from the current FAS to the new FAS (potential name incoming!). We also came to the end of developing our wireframes and mapping our user experience flow. Unit tests were carried out regarding password controller and the current codebase.

We received great support from the wider CPE team as well as Patrick Uiterwijk to allow us progress with user stories by gaining permissions and merging PR’s for the integration of CentOS CI. Christian Heimes assisted us greatly with sharing his knowledge regarding FREE IPA and answered numerous questions to allow us to move forward.

Sprint 4 began on Thursday the 20th of February. This sprint will focus on development tasks which will include working on FAS Json, Free IPA, API, Fedora Messaging integration, continuous deployment to stage environment, developing a secure coding tool to ensure code adheres to best practice, as well as continuing working on user functionality user stories. Please see our github board here to view current activity.

We also received some sad news since our last update, that we are losing a team member, Rick Elrod, as he moves on to pastures new with the Ansible team. Rick provided an excellent POC for AAA which is leaving us in good shape to continue on as planned. Thanks Rick and we will hopefully still see you around as a contributor going forward. We also welcomed a new team member Leonardo (Leo) Rossetti who joined at the start of Sprint 4 and has already hit the ground running. Leo is currently working on our FAS JSON user stories.

Regarding delivery of AAA, we may look at a phased release , this current phase focus is on the development of AAA to be delivered by 3/31/20. It is looking likely that the deployment of AAA will happen in a later phase due to requiring System Admin assistance. We are likely to gain this on the completion of the Colo Move (which is our planned data center move), approximately in mid April. We are inquiring to see if deploying to staging is possible within this phase to allow for a long testing period. I will provide an update on this in our next blog. The integration of CentOS will be worked on within an additional phase following the completion of AAA centric stories for Fedora.

On a final note, I would like to commend the CPE AAA team on their collaboration and productivity throughout this initiative even in the face of unknowns, team changes, cross team dependencies and other challenges, they continued to proactively work together and find solutions to keep this initiative moving forward.

We welcome all feedback, thoughts and contributions as we progress through this project. Please feel free to comment on any issue to log your thoughts.

  • For more information regarding outstanding issues, please see here.
  • To view our current scrum board, please see here.

Fedora Data Centre Move Project Update 2020-02-28

Hi Everyone,

As you may or may not be aware, last year Red Hat made the decision to move data centers in 2020.

The lease on the current data center in Phoenix was due to expire in 2020 and Red Hat negotiated a better lease with a provider in Northern Virginia.

This data centre is home to Fedora servers.

So, what does this mean for you as a Fedora user? Very little we hope!

The Community Platform Engineering team have been working closely with Red Hat IT to plan logistics, and other 'fun stuff' to make sure this move is successful and as undisruptive to everyone as possible.

During this planning phase, we identified a need to have a minimum viable fedora offering in place during some key dates to facilitate the move, and allow for the shipment of hardware that is integral to Fedora Infrastructure without halting development - or a whole infrastructure!

Here is the link to the discussion that was sent to the public lists in case you missed it on what a Minimum Viable Fedora would look like:

The CPE team will be refocusing on this problem to begin technical development of this offering so we are ready to deploy it at the appropriate time.

But for now, here is a very high level view of the Data Centre move outline, and how it will impact you:

The Community Platform Engineering Team will move in two 'waves'

Wave 1

  • Week beginning April 13th, the CPE team will move an initial batch of servers from Phoenix, Arizona -> Northern Virginia
  • This will not affect the Fedora 32 release aimed for late April.
  • However, during the period of 20th March - 3rd of July we would ask you to observe an 'infra-freeze', meaning no new applications deployments and all code changes reviewed by the sysadmin team before deployment.
  • During April 20th - May 20th, the Community Platform Team will be working on bringing up a minimal viable Fedora solution for continuity of important services in Fedora for development
  • Between May 20th - June 1st, the CPE team will bring the new temporary offering up and redirect services to this instance while the main servers for Fedora are brought down and ready to be shipped.

Wave 2:

  • Between June 1st - 15th, The Community Platform Team will ship all remaining hardware from the Phoenix Data Centre to the new one in Washington.
  • Between May 20th - July 3rd, Fedora services will run on the Minimum Viable Fedora offering to facilitate a successful move of equipment across country!
  • As equipment arrives in the new datacenter, the CPE team will be bringing back services on the new networks and equipment. As with all major moves there will be delays and changes we will only see as we get the services back.
  • We are hopefully, and quietly confident, that we will be able to resume Business As Usual (BAU) in Fedora Infrastructure, and have Fedora up and running in early July.

Expected Effects during Move:

There will be a very limited number of builders during this time frame.

  • Builds will be slower.
  • Composes will be slower.
  • Services like koschei will be turned off.
  • Services will be 'cramped' with less resources than usual.
  • Searches in koji and other tools will be slower.
  • Some applications like badges, voting and calendaring may not be available at all.
  • Tickets will be slower to resolve. Most CPE engineers will be focusing on rebuilding services in the new center so other requests not involved with that will be put on the backlog.


As we move through this project, our dates may change, both for the better and sometimes for the worst so please take the above dates as a *fairly good* estimate for now.

We will be including as many real-time updates on the data center move in our weekly emails to the infra and devel lists.

And while we are planning for as little disruption as possible, there may be downtime during this move so we will endeavor to get ahead of it with messaging out to you all for awareness.

We would finally like to thank you all for your understanding and most of all your patience during the key dates of April 20th - July 3rd so that we can facilitate a successful move.


Please don't hesitate to reach out to us with your questions and we will do our best to answer all the ones we know, and follow up on the ones we don't!

March 11, 2020

Minutes for CentOS Board of Directors 2020-02-12

March 11, 2020 07:54 AM

On 2020-02-12 the CentOS Board of Directors met and discussed several ongoing efforts across the Project.

The opening discussion was around the new work to evolve the project logo and branding identity being conducted in open channels. Overall the Directors really liked the direction the effort is going and were quite pleased with the open nature of the process. What is needed to bring a conclusion and present a final design for the Board’s approval is the completion of the open design discussion and decision process to be conducted in centos-devel.

As the Board is working on adding new Directors and improving governance and transparency, there is an open discussion around the possibility of having a face-to-face meeting of the Board in 2020. This ideally would include an additional day of interactions with other project leadership. One idea floated was to conduct this prior to the CentOS Dojo being planned at CERN in October 2020. At the time of this writing, it is unknown if this Dojo will be affected by COVID-19 related or other travel restrictions.

On another topic, in addition to the focused resources of the Community Platform Engineering (CPE) team that supports the CentOS Project in technical ways, Karsten gave a brief explanation of how the Community Architects from the Red Hat Open Source Program Office (OSPO) are in support of the project, specifically Rich Bowen on the community side, Brian Exelbierd on the business interaction side, and Karsten Wade on the strategic and visionary side.

From the Brussels Dojo, Karsten gave a report out about how he had a meeting room for one-to-one discussions with community members. These discussions were an invitation to talk about what works and doesn’t work for users and contributors around the project; an open office hours to hear out anything. It also served to help get an idea of how and why people use CentOS as a platform. This work is to help inform the CentOS 2020 open goals discussion now underway.

In support of these efforts, the Board came to the following decisions, resolutions, and agreements:

  1. Logo redesign
    1. AGREED:  Board is requesting Tuomas to lead the discussion on centos-devel toward creating the final /branding redesign proposal for the Board to give final approval on. This process should follow an open decision process of inviting participation, hearing out other ideas, and taking and incorporating feedback on the existing design ideas into the final plan. All this can be done over a reasonable time period of four to eight weeks, so that a decision can be reached that has an opportunity to include voices from across the community.
  2. Board face-to-face
    1. AGREED:  Board will watch the travel situation with an eye toward deciding yay/nay on the face-to-face as the June timeframe approaches.
    2. ACTION:  Board will request RIch Bowen to coordinate with the Board Secretary on plans for adding meetings around the CERN Dojo.
  3. Consent items
    1. Adopt minutes from 2020-01-08 meeting
    2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019.
  4. Rolling (last from 2020-01-08):
    1. Any other topics aka What other things do you want on our master initiatives list?
    2. Stepping-up our meeting norms
    3. Transparency initiatives

Present at the meeting:

  • Ralph Angenendt
  • Jim Perrin
  • Mike McLean
  • Karsten Wade (Secretary)
  • Johnny Hughes

March 05, 2020

CentOS Dojo at Facebook postponed

March 05, 2020 06:19 PM

Due to the change in the status of Red Hat Summit, we have made the decision to postpone the CentOS Dojo at Facebook to a later date. Many of our potential speakers, as well as many of our attendees, had travel plans that were dependent on attendance at Red Hat Summit, and without that event happening they are no longer able to travel.

If you have already registered for the event, we encourage you to stay registered, so that we have an easy way to contact you about event updates through Eventbrite.

We do still plan to hold an event at Facebook, but, due to the current corona virus situation, we are holding off on making any firm plans until the danger has passed.

We thank you for your patience and understanding, and hope to see you when we reschedule.

March 03, 2020

CentOS Community newsletter, March 2020 (#2003)

March 03, 2020 05:00 AM

Dear CentOS enthusiast,

For the past several months, the focus has been on FOSDEM, as usual this time of year. Now that FOSDEM is behind us, it's time to turn our attention to the upcoming Dojo at Facebook, and Red Hat Summit. We'd love to see you at one of these events. (or both!) The call for presentations is open for the Dojo, and we're looking for presentations about anything you're doing on top of CentOS. More details below.

In this edition:


The CentOS team is pleased to announce that we have updated the kernel, kmod-kvdo, vdo, createrepo_c, and drpm packages in CentOS 8 Stream. These updates have already been published and are propagating out to the mirror network now.

You can read more about that in the CentOS-Devel mailing list archive.

UPDATE: Due to the change in status of Red Hat Summit, we have decided to postpone the CentOS Dojo at Facebook. Please keep checking back for updates.


Releases and updates

We had a fairly typical month of releases and updates:

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during February:

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during February:


We have a full schedule of events shaping up for this year - both events that we are producing, as well as larger events at which we will have some kind of presence. Come see us:

  • FOSSAsia, March 19-21, Singapore. Details
  • CentOS Dojo at Facebook, April 24th, Menlo Park, California. Details
  • Red Hat Summit, April 27th - 29th, San Francisco, California. Details
  • Texas Linux Fest, May 1-2, Austin, Texas. Details
  • ISC HPC (Supercomputing), June 21-25, Frankfurt, Germany. (Tentative)
  • September 2020 - Dojo at ORNL/UTenn - (Tentative)
  • CentOS Dojo at CERN, October 23rd, Meyrin, Switzerland. Details

SIG Reports

The SIGs - special interest groups - are where most of the interesting stuff in CentOS happens. They are communities packaging and testing layered projects on top of CentOS, and ensuring that they work reliably.

Virtualization SIG

From the oVirt perspective:

- Preparing for oVirt 4.4.0 GA which will support execution on CentOS Linux 8 / CentOS Stream with Advanced Virtualization rebuilt from RHEL.
- Produced Advanced Virtualization builds for Virt SIG and Cloud SIG consumption
- Presented several sessions at DevConfCZ (slides available from , video not yet available as far as I can tell) and Fosdem (presentation and videos available from ) in January 2020
- New members joined the SIG for helping with oVirt: Miguel Barroso (oVirt Networking), Danilo de Paula (Advanced Virtualization)
For Xen:
- Updated kernel 4.9.212
- Made official policy for updating default Xen versions; soon to move to Xen 4.12
- Investigating possibility of joining efforts with Xen Made Easy in maintaining kernel, packages
- Still waiting for CentOS 8 CBS

OpsTools SIG Quarterly Report

01 December 2019 - 29 February 2020.

This report also includes reporting for the Messaging SIG, which is marked explicitly, where it's appropriate.


Provide tools for second day operations for operators of large infrastructure.

The Messaging SIG is providing infrastructure for sending messages like RabbitMQ or Apache QPID.

The OpsTools SIG depends on deliverables of the Messaging SIG. CentOS Opstools builds were consumed by OpenStack Kolla; we would need CentOS 8 builds to move forward, or we'd loose CentOS based container images.

We are interested in getting the builds integrated in OpenStack and to finally have builds CI tested.


As we are coming up on several Dojos, it's worth reminding you that you can step up to host or plan (or both) a dojo in your part of the world. While most of our Dojos are at research institutions (CERN, ORNL) or located alongside other major events (FOSDEM, Red Hat Summit), Dojos are intended to be local gatherings, and so we rely on you to tell us where we should run them.

If you're curious what's involved in running a Dojo, you're in luck. We've been working on a comprehensive playbook to document the various steps, so that you can pick it up and run your own event. It's not done yet, but it's getting there.

Want to run a Dojo? Get in touch with the centos-promo mailing list at

And, as always have a look at the many opportunities for contribution on the 'Contribute' page on the wiki.

Request for members

Many of us have observed that many beginners want to contribute to the CentOS project but after seeing such a huge project they refrain from even starting.

We request the developers or maintainers currently working on the CentOS to create a wiki page or a simple guide on how and what to begin with or a basic tutorial with weekly tasks to facilitate new contributors.

Many people are willing to help in this if this gets initiated.

This will surely give a boost to new innovative ideas by people all around the globe brainstorming for an optimization or improvement.

Get in touch with the centos-promo mailing list at

February 18, 2020

FOSDEM Dojo, post-event survey

February 18, 2020 08:07 PM

At the end of each CentOS Dojo we have an attendee survey. While these never have the response rate I'd like, they do produce interesting data that help us improve future events.

Here's the results from the survey from the Dojo in Brussels, 2020

Q1: I use CentOS for ...

17 responses
76.5% Running services at work
41.2% Software development (professional)
41.2% Running services at home
11.8% My desktop computer
5.9% Software development (personal, hobby)

Q2: I came to this event from:

64.7% Elsewhere in Europe
23.5% Elsewhere in the world
11.8% Brussels

Q3: Talks were ...

88.2% About right
11.8% Not technical enough

Q4: I would like to see more content about:

  • Specific CentOS topics, many talks were not very CentOS related and were then duplicated at the nearby FOSDEM
  • Microsoft's activities to dominate the market
  • CentOS internals
  • id management. Integration with active directory
  • Cloud and storage
  • Containers
  • How to get involved and where is help required
  • How to contribute to CentOS
  • New features in new releases, process of preparation new releases

Just one remark on this last item: We can only schedule talks that are submitted, and for this event, in particular, we had very few submissions. So take this last item as a hint of what kind of talks we'll be looking for next time.

Thank you to everyone that participated in the survey. Your feedback is very helpful!

February 12, 2020

CentOS Dojo at Facebook, April 24th. CFP open now.

February 12, 2020 02:33 PM

We will be holding a CentOS Dojo at Facebook, Menlo Park, (San Francisco area) on April 24th. This is the Friday immediately before Red Hat Summit, so you can tack a few extra days on the front of your Summit trip and see how CentOS is used at Facebook.

Details of the event are available at

The Call for Presentations is now open. We're looking for technical talks about stuff that is in and on CentOS. You can see examples of the content we have run in the past at

88% of our attendees in Brussels said that the content was about right, while 12% said it was not technical enough, if that helps set your expectations of what talks to submit.

The CFP closes on March 15th, and space is extremely limited, so don't wait. Get your talk submissions in now.

Agenda for CentOS Board of Directors meeting 2020-02-12

February 12, 2020 07:24 AM

  1. Do Directors have any questions or concerns about the process being followed to update the CentOS Project logo? Full story in this blog post by Tuomas Kuosmanen;
    1. Specific design concerns should be handled on centos-devel or in the design repo discussion.
  2. Having a face-to-face Board and/or leadership meeting in or near Paris in Summer 2020. What month might be good for Directors?
  3. Directors and other Project leaders are invited and encouraged to collaborate with the now four community architects from Red Hat working in/around the CentOS Project: Rich Bowen, Brian Exelbierd, Tuomas Kuosmanen, and Karsten Wade.
  4. Report out from Karsten on the Board interview/working session room at the Brussels CentOS Dojo.
  5. Consent items
    1. Adopt minutes from 2020-01-08 meeting
    2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019.
  6. Rolling (last from 2020-01-08):
    1. Any other topics aka What other things do you want on our master initiatives list?
    2. Stepping-up our meeting norms
    3. Transparency initiatives

February 06, 2020

CentOS Community newsletter, February 2020 (#2002)

February 06, 2020 04:59 PM

Dear CentOS enthusiast,

After a slowdown over the past few months, the year is off to a busy start. I'm getting the newsletter out a little later than usual, due to having spent last week in Brussels, at FOSDEM. More about this below.

Special thanks go to Aman Gupta, who stepped up to help with the newsletter this month. If you are interested in helping us write the monthly newsletter, please do get in touch. And see the section below on other ways you can contribute to the CentOS community.



Those of you who are following CentOS Stream progress will have noticed that updates are starting to flow. dnf update to get those updates, which are a preview of the next release of Red Hat Enterprise Linux. We continue to work on the tooling, as discussed in this email thread, and others on the CentOS-devel mailing list.

Please also see the thread about the choice of git forge solution which will be run by the Red Hat CPE team on behalf of the CentOS community. Your input is valuable in that decision.

The January Board meeting agenda has been posted to the blog:

We've had a number of blog posts in recent days that you'll want to be sure to read:

Releases and updates

On January 19th, CentOS Linux 8.1.1911 was released. You can read the release notes here. Also, have a look at the longer-term roadmap for this, and our other CentOS releases.

Errata and Enhancements Advisories

We issued the following CEEA (CentOS Errata and Enhancements Advisories) during January:

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during January:

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during January:

Other releases

The following releases also happened during January:

Events, CentOS Dojo, and FOSDEM

The last few weeks have been very busy ones. We had representation at in Brno, Czech Republic, and at FOSDEM, in Brussels, Belgium, as we do most years. DevConf is an event by developers, for developers, and so there's always a big turnout of CentOS fans there. We had a standing-room-only presentation about CentOS Stream, and the video of that session (as well as all of the others) will be available in the next week or two. Watch our Twitter for that video.

In Brussels, we also ran a one day CentOS Dojo, as we have every year for a decade. We had about 110 in attendance, and some great content. We're starting to publish the video on YouTube, and the talk slides are all published to the event page. There's also a full detailed event report on the blog.

Upcoming events

We have a very full schedule of events coming up for the year, which you can always seen listed on the Events page in the wiki.

Follow us on Twitter for announcements as these events shape up over the coming weeks.

Host a Dojo

If your University, company, or research organization, wants to host a CentOS Dojo, we would love to hear from you. You'll need a space where 100-200 people can attend technical talks, and someone who is able to work with us on logistics and talk acquisition. We'll help promote the event, and work with you to craft the schedule of talks. Drop us a note on the CentOS-Promo mailing list - - with your proposal.

SIG Reports

The SIGs - special interest groups - are where most of the interesting stuff in CentOS happens. They are communities packaging and testing layered projects on top of CentOS, and ensuring that they work reliably.

The CentOS Promo SIG has published their quarterly report on the blog.

The AltArch SIG has published new notes about CentOS 8.

The Cloud SIG and the Software Collections SIG, held SIG update sessions at the recent CentOS Dojo in Brussels. Their slides are on the event page, and the video will be posted shortly.


We look forward to hearing from you, and helping you figure out where you can fit in.

You could spend months, or even years, planning a first contribution to a code base. Or you could start small, work your way up, and make that awesome contribution today. As with any open source project, there's a lot more than just code.

If you aren't well versed in programming, then start with the documentation. Why? Well, it is a great way to get a feel for the process, and all projects need better documentation. Pick a part of the project that you use, and look at the documentation to see if there's a way that you can improve it.

It’s less about the actual value you added to the project, and more about entering the OSS community and contributing whatever you can to help the community, If you’re a maintainer, help a newcomer make their first PR! Or help them to work on the documentation.

If you want to get involved, but you're not a programmer or packager, there's still a ton of places where you can plug in.

  • Design - Graphic and design elements for the product itself, the website, materials for events, and so on, are always a great need. This is true of any open source community, where the focus on code can tend to neglect other aspects. Indeed, right now there's an ongoing project to update the CentOS logo and visual identity.
  • Events - While CentOS has an official presence at a few events during the year, we want a wider reach. If you're planning to attend an event, and want to represent CentOS in some way, get in touch with us on the centos-promo mailing list to see how we can support you.
  • Promotion - The Promo SIG does a lot in addition to just events. This includes this newsletter, our social media presence, blog posts, and various other things. We need your help to expand this effort.
  • Documentation - Any open source project is only as good as its documentation. If people can't use it, it doesn't matter. If you're a writer, you are in great demand.

If any of these things interests you, please come talk to us on the centos-devel mailing list, the centos-promo mailing list, or any of the various social media channels.

The community needs dedicated people who are willing to help the community grow. Start contributing today!

Powered by Planet!
Last updated: May 25, 2020 04:15 PM