Dear CentOS enthusiast,
Another month into 2019, and we have a lot to tell you about.
Yes, we've mentioned this before, but we're still pretty stoked about it. On the 15th, we celebrated our 15th birthday with a small group of friends in Oak Ridge, Tennessee, before our Dojo at Oak Ridge National Laboratories. You can see some of the videos from that event beginning to appear on our YouTube channel.
If you would like to talk about your involvement in CentOS, please get in touch with Rich at firstname.lastname@example.org You don't need to be one of the founders - just to have something interesting to say about your involvement, past, present, and future.
As we mentioned last month, there have been some significant changes to git.centos.org. The service was upgraded/migrated to Pagure. You can read details about the change, and instructions on using the new service on the mailing list archive. And further documentation is now in the wiki, at https://wiki.centos.org/Sources
If you have any questions or difficulties using the new service, please drop by either the centos-devel mailing list, or the #centos-devel IRC channel on Freenode.
We had another moderately busy month for update and releases.
We issued the following CEEA (CentOS Errata and Enhancements Advisories) during April:
We issued the following CESA (CentOS Errata and Security Advisories) during April:
We issued the following CEBA (CentOS Errata and Bugfix Advisories) during April:
SIGs - Special Interest Groups - are where people work on the stuff that runs on top of CentOS. We have recently started having SIGs report quarterly, so we have just a few of them each month, getting through the entire list every 3 months.
We have the following SIG reports this month:
The NFV SIG posted their report to the CentOS blog.
This is by no means a complete report but here are a few "juicy" notes
hopefully worth sharing!
Starting in May we'll have a new member in the Storage SIG: Francesco
Pantano, he'll start helping us with the maintenance of the
Ceph/ceph-ansible builds (and their deps).
We have in fact finally populated our Ceph Nautilus repo with a initial
Ceph Nautilus build and we also included RC builds of ceph-ansible;
please help us test both Ceph and the deployment tool itself enabling
the SIG repos by installing the new centos-release-ceph-nautilus package.
We're looking for help with the new builds test automation; ideally we'd
like to have automatic promotion into -release repos of the new builds
when these pass testing; if you can or are interested in helping us with
this effort please get in touch!
See you online.
In April, as mentioned above, we ran a CentOS Dojo at ORNL - Oak Ridge National Labs. The presentation slides are starting to get added to the event website. We expect to have the full video from the event within the next week or two.
I'm writing this newsletter from the Open Infrastructure Summit (formerly known as OpenStack Summit), in Denver. We joined our friends from RDO and Ceph, as well as our colleagues from Red Hat, to discuss all aspects of open infrastructure, especially OpenStack.
A high point included the gathering of some of the largest open science clusters on the planet, running their OpenStack/RDO clouds on CentOS
— RDO (@RDOcommunity) April 30, 2019
And, coming up, we're planning to run a CentOS Dojo in Boston, on the day before DevConf.US. The call for presentations is open, and we want to hear from you! Talks about anything you're doing in, on, or around CentOS is fair game. Submit your talks HERE.
We are always on the look-out for people who are interested in helping to:
Please see the page with further information about contributing. You can also contact the Promotion SIG, or just email Rich directly (email@example.com) with ideas or articles that you'd like to see in the next newsletter.
NFV SIG Quarterly Report through May 1st, 2019
The CentOS NFV SIG exists to support Network Function Virtualization (NFV) in CentOS. Specifically, the idea is to be a vehicle to provide packages for implementers of software networks on the CentOS platform.
In this reporting period, we have had little formal participation. However, there has been continued in NFV on CentOS and interest in deploying our packages on CentOS. We are always looking for additional community participation in all aspects of this SIG, including promoting, building releasing other packages for NFV.
Anyone interested in participating in the NFV SIG should subscribe to the generic CentOS mailing list.
The past quarter has been a somewhat slow one in terms of actual delivered packages.
However, we did release vpp 19.01.
The outlook for vpp 19.04 and 19.08 is TBD at this point.
There has been some renewed interest in dpdk packaging. At this point, there is no immediate plans to release recent DPDK in NFV SIG.
We would welcome a sponsor to work with the NFV SIG upstream community to bring recent dpdk packages into CentOS NFV SIG.
The health of NFV SIG could be better. It was originally perceived as the sponsor for getting OPNFV project into the CentOS distribution. However, subsequently OPNFV releases its own CD images. Subsequently it was primarily sponsoring building opendaylight packages which are still built as part of the upstream product CI.
Since Q1 2018 the project has been focused on building packages and dependencies for upstream fast data plane project, fd.io
In April, vpp 1901 has been released to mirrors and is currently available in build-logs.
At this point, the NFV SIG is continuing to look for a renewed focus. In particular, we are looking for packages to facilitate containerization and kubernetes. Other ideas and sponsors are welcome.
We have no issues to bring to the board’s attention at this time.
Today, CentOS turns 15 years old. It’s had hard times and good times, and gone through a number of big changes over those years. We feel that we’ve landed in a really great place, over the last 5 years, as part of the Red Hat family of projects, and we’re very excited about what’s coming with CentOS 8, and the years to come.
Right now, we want to look back at how we got where we are now. We did that by going back and talking with some of the people that were involved in those early years, as well as some that joined the project later on.
We started by talking with Greg Kurtzer, who was the original founder of the project. In this interview, he told us about the motivations for starting the project, as well as some of the community challenges that were faced in those first years.
Along the way, Greg had an opportunity to very intentionally set the tone of the community to be welcoming and tolerant. This was primarily because Greg had has some very negative experiences with some of the very hostile communities in those early years. We talked a little bit about those intentional changes in the second half of our interview.
Our next interview was with Manuel “Wolfy” Wolfshant, who was also involved almost from the beginning. He began as a user, and quickly moved to building packages, which he needed for work, but decided to share with the world. He also was then, and is now, very involved in user support in the forums.
That interview can be read on the CentOS blog at https://blog.centos.org/2019/04/centos15-wolfy/
While at FOSDEM, in Brussels, in February, I talked with two members of the community. Mike McLean, a contributor to the project, and the author of the Koji tool that is used extensively in CentOS and Fedora, talked about his contributions:
And Brian Stinson, a more recent addition to the community, talked about his work in the CI and infrastructure of the project:
Our community is very dependent on people that actually use CentOS in production, because they are the people who find the problems, and who have insight into changes that should be made. They also are our most valuable contributors to user support, because they’ve been there, and know how to fix things when they break. Jeff Sheltren is one of those people, and has been using CentOS since the very beginning. Over time, he’s become part of the centos-qa group that helps test and package new versions of the distribution.
And finally, we have an interview with Karsten Wade, who was very instrumental in bringing CentOS into the Red Hat family, and continues to act as the liaison between the CentOS board, and Red Hat, although his position has changed over the years as I (Rich Bowen) have moved full time into that community manager role.
In the coming months, we’ll continue to do these interviews. If you’re part of the CentOS community, we’d like to hear from you - how you got involved, and how your role has changed as you’ve gotten more involved over the years. Get in touch with Rich - firstname.lastname@example.org - and we’ll talk.
Happy Birthday, CentOS. And here’s hoping that the next 15 years are even better. Come see us at Red Hat Summit next month to hear about what’s coming in CentOS 8, and what’s next for our community!
For our next #CentOS15 profile, I spoke with Manuel "Wolfy" Wolfshant, who has been an active member of our community since the very beginning, shortly after we started working with the WhiteBox Linux community.
(You can see some of the other #CentOS15 interviews on YouTube.)
When Red Hat moved the business model from selling CDs to selling support, his company had a need to provide a Linux desktop operating system, and packages for it.
Wolfy says that his eye was caught by a news article about Johnny Hughes and the Mayor of Tuttle, Oklahoma, Jerry Taylor.
If you weren't around back then, I'll recap. Due to a failed server upgrade, the Mayor of Tuttle woke to find the generic Apache httpd welcome page, and the CentOS logo, on his city's website. He promptly emailed the CentOS project, threatening to turn them over to the FBI if they didn't undo their malicious hack of the site.
Johnny, being Johnny, responded calmly and respectfully, encouraging the Mayor to contact his IT department, and pointing him to resources to help get his site running again. Given this response, Mr. Taylor
got even angrier, and the conversation went downhill from there. But Johnny remained calm, polite, and professional, and helped guide the city IT department to a solution.
You can read more in the article from the Register at the time.
Impressed with Johnny's calm and helpful response, Wolfy went with CentOS, and has been a happy user for many years since that time.
His involvement in the project began with packaging drivers that were needed for machines in the office. It swiftly moved to other areas, including user support, translation, and starting the very active Romanian Linux user group, RLUG, which remains active today.
Over the years, he has worked on the release notes (for a time providing them in Romanian), packaging for Fedora, and the creation and maintenance of the minimal install kickstart during the CentOS 6 days.
He remains active in the IRC channel, on the mailing lists, and in the CentOS Forum, helping new users (and some experienced ones!) navigate their problems with the CentOS operating system. You can find him #centos-devel channel on Freenode IRC under the name 'wolfy', and on the centos-devel mailing list, answering user questions.
It's not a secret that the CentOS project has always been running on sponsored infra since the beginning of the journey. While over the years we sometimes lost some "sponsors", we are always happy to see new ones joigning us . That's especially true for the infra used to "seed" the CentOS distro and SIGs content to external mirrors, and even more in regions that are less covered.
While we have some nodes in North America and Europe, some other regions are less covered (if not at all). That's why we'd like to say thank you to Packet to have recently sponsored some bare-metal nodes that are now members of our msync network, including (but not limited) to regions like Asia (with one node in Japan !), Europe and America. Welcome !
The CentOS Atomic SIG has released an updated version of CentOS Atomic Host (7.1902), 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.
A substantial number of released/updates were announced on Tuesday, March 19th, and are listed below. For timely announcements of these updates, subscribe to the centos-announce mailing list, at https://lists.centos.org/mailman/listinfo/centos-announce .
We issued the following CEEA (CentOS Errata and Enhancements Advisories) during March:
We issued the following CESA (CentOS Errata and Security Advisories) during March:
We issued the following CEBA (CentOS Errata and Bugfix Advisories) during March:
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 February 28th, 2019.
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):