Once upon a time, there was a repository called fasttrack, and it used to get low priority updates before going through all the usual checks.

Eventually, that repo was deprecated, we couldn't delete it without breaking compatibility, so it just stayed there, empty and silent.

A few days ago, a bug appeared in bind, that was giving headaches to many people, we had a fix and wanted to give the users an option without waiting for the official build, so we decided to bring fasttrack back to life.

What will it be for?
Well, exactly for cases like this, simple fixes that the CentOS QA team or community members come up with, and helps users while they wait for the official solution.

How do I enable it?
sudo yum-config-manager --enable fasttrack
Then run yum update as usual.

What are the steps?
1) Submit your bug in https://bugs.centos.org/
2) If you have a patch, or a reference to the program's bug tracking system, add it to the bug.
3) This is the most important step, "Be patient!!!"
4) If all goes well, and we like the patch, we'll create a temporary build and point you to it in the bug entry.
5) You'll have to install and test that this build works.
6) If not done already, submit a bug in https://bugzilla.redhat.com/ and point it to the one created in CentOS.
7) Once all of this is done, we'll sign and push it to the fasttrack repo for everybody to use.

Please keep in mind that this repo is for "temporary" fixes, until Red Hat comes up with the real solution.

If you have any problems, please report back through the usual channels (irc, forums, Bug Tracker, Mailing Lists, etc)


Update: Added steps. all this is WiP at the moment.

2018-12-12: We published new Vagrant images, v1811.02, fixing CentOS bug 15552 (wrong permissions on file /etc/sudoers.d/vagrant cause visudo -c to report an error, which can result in problems with Puppet).

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

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 https://github.com/mvermaes/centos-vmware-tools
  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 http://cloud.centos.org/centos/7/vagrant/x86_64/images/sha256sum.txt.asc -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|
  config.vm.box = "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 = "https://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-Vagrant-1803_01.VirtualBox.box"


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.

The CentOS Atomic SIG has released an updated version of CentOS Atomic Host (7.1811), an operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host.

CentOS Atomic Host includes these core component versions:

  • atomic-1.22.1-26.gitb507039.el7.centos.x86_64
  • cloud-init-18.2-1.el7.centos.1.x86_64
  • podman-
  • docker-1.13.1-84.git07f3374.el7.centos.x86_64
  • etcd-3.2.22-1.el7.x86_64
  • flannel-0.7.1-4.el7.x86_64
  • kernel-3.10.0-957.1.3.el7.x86_64
  • ostree-2018.5-1.el7.x86_64
  • rpm-ostree-client-2018.5-2.atomic.el7.x86_64

Download CentOS Atomic Host

CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki.


If you’re running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command:

# atomic host upgrade

Release Cycle

The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they’re rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them.

Getting Involved

CentOS Atomic Host is produced by the CentOS Atomic SIG, based on upstream work from Project Atomic. If you’d like to work on testing images, help with packaging, documentation – join us!

You’ll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel mailing list if you’d like to discuss the direction of Project Atomic, its components, or have other questions.

Getting Help

If you run into any problems with the images or components, feel free to ask on the centos-devel mailing list.

Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

Dear CentOS enthusiast,

Can you believe it's December already? Here's what's been happening in the past month at CentOS.

Releases and updates

The following releases and updates happened in November. For each update, the given URL provides the upstream notes about the change.

Errata and Enhancements Advisories

There were no CEEA (CentOS Errata and Enhancements Advisories) during November.

Errata and Security Advisories

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

Errata and Bugfix Advisories

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

SIG Updates

SIGs - Special Interest Groups - are where people work on the stuff that runs on top of CentOS.

Virtualization SIG

We have two new member for Virt SIG: yuvalt and tomo

Upstream released oVirt 4.3.0 alpha on November 26th

Initial manual testing with 7.6 CR repo enabled are passing, waiting for CentOS 7.6 to GA.

Upstream preparing a first release candidate for 4.2.8, should go out on November 28th, GA is planned in January.
oVirt 4.3 is going to switch to GlusterFS 5, waiting to get it released along with CentOS 7.6.

We are working with OpsTools SIG to get ready for collectd 5.8.1, also coming with CentOS 7.6.

Waiting on CentOS infra for having an appliance shipping ovirt-guest-agent, hopefully with CentOS 7.6 GA.

Why your project should participate in a CentOS SIG

Last week we published an overview of Why your project should participate in a CentOS SIG. If you're involved in any open source project, and want it to have more exposure and better testing on CentOS, the SIGs are designed specifically for you. Join an existing SIG, or propose a new one that better fits your project.

The CentOS Container Pipeline Project

Did you know that CentOS Container Pipeline project offers an automated way of building CetntOS based containers? All you need to do to get started is add details about your open-source project to the container-index repository The service picks things up from there and rebuilds your container image every time you push a commit to the specified branch!

The team recently revamped the service architecture to be based on OpenShift. The service is hosted on CentOS infrastructure but can be easily deployed in your own infrastructure.

The project also scans container images for rpm, pip, npm and gem package updates; capabilities of resulting container; and integrity of RPM data. You can also leverage parent-child relationship to trigger a build of child image(s) whenever its parent image gets updated!

Got questions? Contact the team on 'container-apps' channel on Mattermost.


Recent events

In November, we had a small presence at SuperComputing 18 in Dallas. While there, we talked with a few of the teams participating in the Student Cluster Competition. As usual, student supercomputing is #PoweredByCentOS, with 11 of the 15 participating teams running CentOS. (One Fedora, two Ubuntu, one Debian.)

Our congratulations go out to the team from Tsinghua University, who won this year's competition!

Upcoming events

In December, we'll be at the Red Hat booth at Kubecon in Seattle. Drop by for all of your CentOS sticker needs.

Coming up next year, we have two Dojos in the early part of the year that you'll want to be at.

In Europe, we have our annual Dojo at FOSDEM. It will be held at the Grand Place Marriott on Friday, February 1st, 2019. Registration is free, but we do need you to register, so that we can adequately plan. The schedule, details, and registration, are available on the event web page.

And, in North America, we have just announced our upcoming Dojo at Oak Ridge National Labs, on Tuesday, April 16th, 2019. Initial information, and the call for presentations, is on the event web page.

Contributing to CentOS Pulse

We are always on the look-out for people who are interested in helping to:

  • report on CentOS community activity
  • provide a report from the SIG on which you participate
  • maintain a (sub-)section of the newsletter
  • write an article on an interesting person or topic
  • provide the hint, tip or trick of the month

Please see the page with further information about contributing. You can also contact the Promotion SIG, or just email Rich directly (rbowen@centosproject.org) with ideas or articles that you'd like to see in the next newsletter.


When thinking about the CentOS Project, it’s natural to think of the Linux distro and how it makes operations and administration easy through sane package integration and management.  If you are an open source software project, though, how is the CentOS Linux platform useful to you beyond the operating system?

This is where SIGs come in.

Special Interest Groups (SIG) are smaller groups within the CentOS community that focus on a small set of issues, in order to either create awareness or to focus on development along a specific topic.

For example, the Cloud SIG produces packages for cloud infrastructure projects such as OpenStack and Cloudstack. And the Storage SIG produces packages for software defined storage projects, such as Gluster and Ceph.

Other SIGs, such as the Promotion SIG and the Artwork SIG, focus on non-technical aspects of the CentOS distribution, and are other ways to get involved in the life of the community. These SIGs are a topic for another day.

There are a number of reasons that your open source project might want to engage with a CentOS SIG.

CI and Packaging

The most important service that the CentOS Project provides to your project is the CI and packaging tools. These are described in the SIG Guide, along with other tools and resources that are available to SIGs.

By using the CentOS CBS (Community Build System) you can ensure that your project not only works flawlessly on CentOS, but also doesn’t have any conflicts with other projects that are providing packages for CentOS.

With help from the larger CentOS community, and other projects within your SIG, this relieves you of the need to be a CentOS expert yourself.

Easier to install on CentOS and RHEL

The primary output of a SIG is a repository of packages. This makes it easier for users of CentOS to install and use your project, with a simple ‘yum install’, and ensure that they’ll get all of the necessary dependencies with no additional effort on their part.

Community of like-minded developers

Other projects in your same subject area are often faced with similar problems. The SIG is a great place to solve those problems together, whether they are CentOS specific, or more generally applicable to your problem space.

Promotion of your project to CentOS users

Each time you push a release, this can be promoted to the CentOS community through our various social media channels, mailing lists, forums and newsletter. This expands the reach of your project to an audience who isn’t on your project promotional channels. This can be a real boon to smaller projects, as well as to projects that are very developer focused and don’t have much user/operator outreach.

A place for your users to address platform-specific issues

Problems that people have with your project are often actually problems with the platform on which they’re running them. Perhaps they don’t understand how services work on CentOS, or aren’t familiar with the configuration nuances that are specific to CentOS. Having a place where users can ask these questions, and get authoritative answers, can take a lot of the support burden off of your regular community, who, while deeply familiar with your project, maybe aren’t so familiar with the idiosyncrasies of CentOS.

I'm at SC18 - the premiere international supercomputing event - in Dallas, Texas. Every year at this event, hundreds of companies and universities gather to show what they've been doing in the past year in supercomputing and HPC.

As usual, the highlight of this event for me is the student cluster competition. Teams from around the world gather to compete on which team can make the fastest, most efficient supercomputer within certain constraints. In particular, the machine must be built from commercially available components and not consume more than a certain amount of electrical power while doing so.

This year's teams come from Europe, North America, Asia, and Australia, and come from a pool of applicants of hundreds of universities who have been narrowed down to this list.

Of the 15 teams participating, 11 of them are running their clusters on CentOS. There are 2 running Ubuntu, one Running Debian, and one running fedora. This is, of course, typical at these competitions, with Centos leading as the preferred supercomputing operating system.

The teams are given a variety of projects to work on before they get here, and then there is one surprise project that is presented to them when they arrive. They have 48 hours to work on these projects, and the winner is selected based on benchmarks and power consumption.

You can read more about the competition, and about the teams participating, on the SCC website.



We would like to announce that OKD v3.11 rpms been officially released and are available at http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/. [1]

OKD is the Origin community distribution of Kubernetes.

In order to use the released repo [1] we have created and published the rpm (contains the yum configuration file) [2] which is in the main CentOS extra repository. The rpm itself has a dependency on the centos-release-ansible26 [3] which is the ansbile 2.6 version rpm built by CentOS Infra team.

Should you decide not to use the centos-release-openshift-origin3* rpm then will be your responsibility to get ansible 2.6 required to by openshift-ansible installer.

Please note that due to ongoing work on releasing CentOS 7.6, the mirror.centos.org repo is in freeze mode - see https://lists.centos.org/pipermail/centos-devel/2018-November/017033.html [4] and as such we have not published the rpms to http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ [5]. Once the freeze mode will end, we'll publish the rpms.

Kudos goes to CentOS Infra team for being very kind in giving us a waiver to make the current release possible.

Thank you,
PaaS SIG team

Reference URLs:

[1] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
[2] http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-openshift-origin311-1-2.el7.centos.noarch.rpm
[3] http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansible26-1-3.el7.centos.noarch.rpm
[4] https://lists.centos.org/pipermail/centos-devel/2018-November/017033.html
[5] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/


We are pleased to announce the (tentative) schedule of talks for the
upcoming CentOS Dojo in Brussels, which will be held on the day before
FOSDEM - February 1, 2019 - at the Grand Place Marriott.

Details, and the schedule, are now available at
https://wiki.centos.org/Events/Dojo/Brussels2019 (Schedule subject to

Registration is free, but we need to know how many people are coming,
for catering and space purposes. You can register today at:

See you in Brussels!

Dear CentOS enthusiast,

Here's what's been happening in the past month at CentOS.

Releases and updates

The following releases and updates happened in October. For each update, the given URL provides the upstream notes about the change.

Errata and Enhancements Advisories

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

Errata and Security Advisories

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

Errata and Bugfix Advisories

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

SIG Updates

SIGs - Special Interest Groups - are where people work on the stuff that runs on top of CentOS.


We have been focused on VPP and pre-requisite packages required to build VPP.

OVS and DPDK are available in Cloud SIG but can also be made available in NFV SIG on request.

Current projects are enabling building of VPP 1810 which requires toolset7 and some additional build dependencies.

Storage SIG

Luminous is the current latest major version of ceph maintained by the SIG

We have very recently promoted in this repo the very first version of ceph-ansible which supports ansible 2.6 (previously it would only work with 2.4 and 2.5)

There isn't and probably there won't be a repo for the mimic version

There will be a repo for the nautilus version instead, which will be the first ceph version supporting centos 8

Get involved with the SIGs!

At the recent SIG gathering at CERN, we discussed at some length how to get more people, and more projects, involved in the SIG process.

A SIG is a place for related projects to gather, to work together to get their products packaged, tested, and distributed in CentOS. For example, the Cloud SIG has representatives from OpenStack and Cloudstack, producing packages of their code.

Unfortunately, many of our SIGs have only one project represented. For example, the Storage SIG is primarily Gluster, while the Virtualization SIG is primarily oVirt. We'd like to expand these to include more projects, both to increase the diversity of project availability on CentOS, and because these projects are often solving similar problems, and can cooperate on them.

Which brings us to you. There are so many ways that you can get involved in the SIG process, no matter what your skills and interests.


The primary output of a SIG is a package repository, and so creating those packages tends to be where the main focus of a SIG rests. If you like to create packages, or want to learn how, this is your place to get involved.


While there's extensive process around automated testing of the packages, there's no substitute for actual human testing, to find the edge cases, ensure that things are working correctly, and catch things for which there's no automated testing yet. And creating those tests are a great way to ensure that problems don't reappear in the future.

Promotion and outreach

We want the CentOS SIGs to represent the enormous diversity of the open source landscape itself. We want the Storage SIG to represent not only the hugely popular software defined storage solutions everyone has heard of, but also the smaller communities with more niche use cases. We want the PaaS SIG to represent all of the various PaaS projects.

This takes outreach to the projects themselves, and to the users of those projects, to persuade them of the value of being involved in the SIG process, and then to help onboard them into that process.

It also takes improvement of our documentation to make it more accessible to people who aren't already familiar with how this all works.

And it takes enthusiastic people to produce materials for use at events, and then staff those events to explain to beginners how to get involved.

We even have a separate SIG for this - the Promotion SIG - which focuses on getting the word out, and helping to onboard people when they arrive. And the Artwork SIG is responsible for creating artwork for use both in the distribution, and on our various websites, to make the entire experience more visually appealing.

Get involved!

If you want to get involved in a SIG, or to start a new one, come join us for the SIG meetings on the #centos-devel channel on Freenode IRC. Have a look at the list of active SIGs, and see if there's one that interests you. Or look at the proposed SIGs and see if there's something you can do to get them bootstrapped.


Recent events

October was a very, very busy month for CentOS events all over the world.

CentOS was a sponsor of Ohio LinuxFest, in Columbus, Ohio. OLF is an annual event, drawing most of its attendees from Ohio, and surrounding states. The first day of the event has in-depth technical tutorials, while the second day draws more of a hobbyist audience, including a number of highschool students. As such, it’s a great opportunity to talk about CentOS and Fedora. Our friends from Fedora shared our space with us, and we had a number of great conversations with our fans, as well as talking with a number of local businesses who run their operations on CentOS, Fedora, and RHEL.

Later in the month, we held our second annual CentOS Dojo at CERN. There were around 100 people in attendance, and presentations ranged from science to technical to community. We started the day with a presentation from CERN about how they use CentOS, OpenStack, and Ceph in their investigation of the secrets of the universe. We then heard from a number of our SIGs (Special Interest Groups) about what they’re working on, and how people can get more involved. You can watch the video from each presentation by clicking on the paperclip icon next to the individual items in the event schedule listing.

On the day before the Dojo, we had a smaller gathering of our SIGs. There was discussion about the upcoming changes to the Git infrastructure - a conversation that was started at this event last year. Various SIGs reported on what they’ve been working on over the last few months. And there was discussion about how we can get more contributors involved in the SIG process. (See the SIG Updates section of this newsletter for more about this.) Watch the centos-devel list for more discussions around these topics.

During the week of October 22nd, a few of us were at Open Source Summit in Edinburgh (the event formerly known as LinuxCon. Here, too, we had great interactions with people from all levels of involvement, from people running massive server farms to kids running CentOS at home.

And finally, in the last week of the month, we had a sponsor booth at LISA in Nashville, once again shared with our friends from Fedora. LISA - Large Installation System Administration Conference - is one of the oldest software conferences in the world, going back to 1987.

If you are aware of any events in November where CentOS has (or should have!) a presence, please don’t hesitate to announce it on the centos-promo mailing list so that we can help you promote it. Or, you can add it directly to the upcoming events page.

Upcoming events

The next big event for the CentOS community is FOSDEM, and the CentOS Dojo immediately before FOSDEM. We will be announcing the schedule for this event today or tomorrow - as soon as the speakers respond with confirmation of their attendance. See you in Brussels!

Contributing to CentOS Pulse

We are always on the look-out for people who are interested in helping to:

  • report on CentOS community activity
  • provide a report from the SIG on which you participate
  • maintain a (sub-)section of the newsletter
  • write an article on an interesting person or topic
  • provide the hint, tip or trick of the month

Please see the page with further information about contributing. You can also contact the Promotion SIG, or just email Rich directly (rbowen@centosproject.org) with ideas or articles that you'd like to see in the next newsletter.


The videos from the recent #CentOSDojo at #CERN are now available on the CentOS YouTube channel. If you have time for only one, be sure to watch the first video, which talks about the challenges that CERN has with the enormous amount of data they produce every day in the LHC.

Also recommended, Fabian's discussion of the coming (and already in place!) changes to the CentOS Git infrastructure.

[UPDATE: The videos which were previously updated were truncated, and we're looking into fixing that. meanwhile you can view the video on the event schedule by clicking the paperclip icon next to each talk title.]