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.
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
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.
config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
config.vm.synced_folder ".", "/vagrant", disabled: true
to their Vagrantfile, to prevent errors on "vagrant up".
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]
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
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" end end
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):
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:
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:
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.
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.
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.
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/. 
In order to use the released repo  we have created and published the rpm (contains the yum configuration file)  which is in the main CentOS extra repository. The rpm itself has a dependency on the centos-release-ansible26  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  and as such we have not published the rpms to http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ . 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.
PaaS SIG team
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!
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.]