Dear CentOS enthusiast,
CentOS is more than just code. If you want to contribute in other non-code ways - documentation, design, promotion, events - we want to hear from you. See the "Contributing" section below for more details.
This month the infrastructure team has been working hard on getting Centos 8 and CentOS Stream into the CBS (Community Build System). On the 29th, Thomas announced that this work had been completed and detailed what still needs to be done. If you're interested in building packages against either of these targets, you're encouraged to read that mailing list thread thoroughly, and ask any questions you may have there.
Earlier in the month, a meeting was held in Boston including representatives from various parts of Red Hat, discussing what needed to be done internally to facilitate the cooperation between the Red Hat Enterprise Linux (RHEL) Engineering and QE teams, and the CentOS community. There too, plenty remains to be done, but we're making progress towards making this a true upstream of RHEL. We appreciate your patience as we make the many changes that are needed to make this a success.
If you're considering using CentOS Stream, either in production, or as a development platform, we'd love to hear from you. We particularly want to hear what we can do better to help you succeed, so that we can make this platform something that serves everyone's needs.
This month has seen a moderate number of updates/releases:
October was a quiet month for events, but we do have a couple of upcoming events that we want to be sure are on your calendar:
As you may know, SuperComputing is overwhelmingly powered by CentOS. We'll be at SuperComputing19 in Denver in just a few weeks, hanging out at the Red Hat booth to discuss your SuperComputing and HPC needs.
FOSDEM is one of the largest, and oldest, open source gatherings in the world. CentOS has had a presence there for many years, and we plan to be there again in 2020. FOSDEM is, as usual, the first weekend in February (Feb 1-2 2020) in Brussels Belgium.
CentOS expects to have a table in the main exhibitor area (we'll find out for sure in a couple weeks), and, from a content perspective, we encourage you to keep an eye on the distributions devroom, where content relating to CentOS, and other Linux distributions, will be presented.
Also, like every year, we plan to hold our CentOS Dojo on the Friday before FOSDEM - January 31st - at the Marriott Grand Place. Details are on the CentOS wiki. The call for presentations is now open. We want to hear what you're working on which may be of interest to the CentOS community. Have a look at last year's schedule for an idea of what kinds of talks we've run in the past.
The call for presentation closes on November 18th, so that we have time to build the schedule and promote the event a little more widely. So don't wait!
As with any open source project, there's a lot more than just code. 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.
We look forward to hearing from you, and helping you figure out where you can fit in.
Dear CentOS enthusiast,
If you'd like to help out with the process of putting together the newsletter, please see the Contributing section at the end. We're always looking for help!
The big news in September was the release of CentOS Linux 8, along with CentOS Stream. CentOS Linux 8 is exactly what you expected - a rebuild of Red Hat Enterprise Linux (RHEL) 8 - but CentOS Stream is a new aspect of the CentOS Project that needs a little more explanation.
CentOS Stream is a rolling preview of what will be in the next minor release of RHEL. CentOS Stream will be updated regularly (the exact cadence is still a work in progress) and will give you the opportunity to verify your code and workloads against what’s coming next.
The motivation for doing this is to provide a platform where people can develop against CentOS Stream, and, by doing so, be ready for market the day that the next minor version of RHEL ships. CentOS Stream will be developer beta level code (not alpha) containing features ready for validation to include in the next minor release of RHEL. Red Hat wants CentOS Stream to be a great experience for developers to target the next minor release of RHEL (released every 6 months). Code that is delivered to CentOS Stream is what Red Hat engineers intend to go into the next minor release of RHEL and will have gone through CI.
If you’re interested in building a project on Stream, we encourage you to look into the SIGs - https://wiki.centos.org/SpecialInterestGroup - which are a place to package and test on CentOS, using the Community Build System (CBS) and the CentOS CI. Bring your ideas to the centos-devel mailing list, and we’ll help you figure out the way forward.
Finally, note that this is still a work in progress. We hope to have regular updates to CentOS Stream within the next few months, but tooling for that does not exist yet, and so there will be a lot of manual processes at first. We appreciate your patience while we get things up and running.
We are working on a feedback mechanism that is going to evolve over time. CentOS Stream must have the ability to get feedback and suggestions to be successful. We will announce details as things solidify.
You can download CentOS Stream, as well as CentOS Linux, at https://www.centos.org/download/ and you can read more details on the centos-devel mailing list, at https://lists.centos.org/pipermail/centos-devel/2019-October/017922.html
We issued the following CEEA (CentOS Errata and Enhancements Advisories) during September:
We issued the following CESA (CentOS Errata and Security Advisories) during September:
We issued the following CEBA (CentOS Errata and Bugfix Advisories) during September:
The following releases also happened during September:
In September, we had a presence at the Webpros Summit (formerly the cPanel conference) in Atlanta, Georgia. The cPanel community are long-term supporters of CentOS, so this is always a fun event. It was also a great place for some early conversations about CentOS Stream as a place to develop and test products.
While there, Johnny Hughes gave an excellent presentation about the CentOS Linux 8 release, what's in it, and why it was a longer process than usual.
As usual, there's a number of events coming up where you can find members of the CentOS community.
October 28–30, in Portland, we'll be at LISA19, the\premier conference for operations professionals, where we share real-world knowledge about designing, building, securing, and maintaining the critical systems of our interconnected world. Come see us at the Red Hat booth with your CentOS questions and stories.
Then, in November, we'll be in Denver at SC19 - the international conference for high performance computing, networking, storage and analysis. Once again, come see us at the Red Hat booth. As usual, or main interest there is the always-awesome Student Cluster Competition, where tomorrow's HPC experts compete to build a supercomputer with off-the-shelf hardware and open source software ... and most of them choose CentOS. Supercomputing is #PoweredByCentOS!
Finally, I want to keep reminding you that we'll be doing another Dojo at FOSDEM, on January 31st 2020. Details will be coming soon to the CentOS Wiki. Think about what you might want to present about, and be sure to join us in Brussels!
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 (firstname.lastname@example.org) with ideas or articles that you'd like to see in the next newsletter.
We are excited to announce the release of CentOS 8, and of the new RHEL upstream, CentOS Streams. Details can be found on the CentOS-Announce mailing list.
We are pleased to announce the general availability of CentOS Linux 7 (1908) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1908, derived from Red Hat Enterprise Linux 7.7 Source Code.
Full details are on the centos-devel mailing list.
The one-day event, located on the campus of Boston University in the George Sherman Union Building, will feature talks on:
The event is free, but attendees should register for the event so planners can get an idea of attendance.
In the evening we’ll be gathering at a local watering hole for less formal discussions, accompanied by food and great local beers - location to be announced on the day of the event!
CentOS will continue its presence at DevConfUS with a booth and various talks, so even if you miss the Dojo, there’s still plenty of time to meet with folks working on CentOS. We look forward to seeing you soon!
The CentOS Atomic SIG has released an updated version of CentOS Atomic Host (7.1906), 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, or qcow2 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.
Today marks a new day in the 26-year history of Red Hat. IBM has finalized its acquisition of Red Hat which will operate as a distinct unit within IBM moving forward.
What does this mean for Red Hat’s contributions to the CentOS project?
In short, nothing.
Red Hat always has and will continue to be a champion for open source and projects like CentOS. IBM is committed to Red Hat’s independence and role in open source software communities so that we can continue this work without interruption or changes.
Our mission, governance, and objectives remain the same. We will continue to execute the existing project roadmap. Red Hat associates will continue to contribute to the upstream in the same ways they have been. And, as always, we will continue to help upstream projects be successful and contribute to welcoming new members and maintaining the project.
We will do this together, with the community, as we always have.
If you have questions or would like to learn more about today’s news, I encourage you to review the list of materials below. Red Hat CTO Chris Wright will host an online Q&A session in the coming days where you can ask questions you may have about what the acquisition means for Red Hat and our involvement in open source communities. Details will be announced on the Red Hat blog
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 May 30th, 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):