March 20, 2019

CentOS Atomic Host 7.1902 Available for Download

March 20, 2019 06:36 PM

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:

  • atomic-1.22.1-26.gitb507039.el7.centos.x86_64
  • rpm-ostree-client-2018.5-2.atomic.el7.x86_64
  • ostree-2018.5-1.el7.x86_64
  • cloud-init-18.2-1.el7.centos.1.x86_64
  • docker-1.13.1-91.git07f3374.el7.centos.x86_64
  • kernel-3.10.0-957.5.1.el7.x86_64
  • podman-0.12.1.2-2.git9551f6b.el7.centos.x86_64
  • flannel-0.7.1-4.el7.x86_64
  • etcd-3.3.11-2.el7.centos.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.

Upgrading

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.

Errata/Releases, March 19th 2019

March 20, 2019 02:11 PM

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 .

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:

 

March 05, 2019

Updated CentOS Vagrant Images Available (v1902.01)

March 05, 2019 08:39 PM

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.

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.

Downloads

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"
  end
end

Feedback

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.

Ackowledgements

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.

CentOS Pulse Newsletter, March 2019 (#1903)

March 05, 2019 07:49 AM

Dear CentOS enthusiast,

Another month into 2019, and we have a lot to tell you about.

CentOS is 15!

As you may have seen either at recent events, or on social media, we're getting ready to celebrate our 15th birthday! As part of that, Rich has been interviewing various people who were around in those early years, to get some of the back-story on how it all happened. You'll start seeing these interviews on the blog in the month of March.

This week, we have published an interview with Greg Kurtzer, who founded the project in the first place.

Later, we'll be publishing interviews with Karsten Wade, Manuel "wolfy" Wolfshant, and Mike McLean, with others to come.

If you would like to talk about your involvement in CentOS, please get in touch with Rich at rbowen@centosproject.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.

Releases and updates

February was a very busy month for errata and updates. The links below are to the release notes for each update.

Errata and Enhancements Advisories

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

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:

SIG Updates

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.

NFV SIG

There was presentation on NFV SIG at the CentOS dojo.

We hope to get fd.io vpp 19.01 release RPMs in mirrors before the end of February. Stay tuned.

More information on the NFV SIG, including how to get involved, may be found on their wiki page.

Opstools SIG

The opstools SIG has published their quarterly report to the CentOS Blog.

More information on the Opstools SIG, including how to get involved, may be found on their wiki page.

Virtualization SIG

The Virtualization SIG has published their quarterly report to the CentOS Blog.

More information about the Virtualization SIG, including how to get involved, may be found on their wiki page.

Events

FOSDEM was, of course, in February, but we reported on that in last months' newsletter.

This month, we'll be sponsoring FOSSAsia in Singapore! We'll have a CentOS table there, and we'll have participation from numerous of our favorite projects, including Ansible, ManageIQ, Fedora, and Dogtag.

We are ramping up towards the CentOS Dojo at ORNL, which is now just a month and a half away. We have published our speaker list, and the full schedule of talks should be up very soon. Register today to attend! (Registration is free, but due to the nature of the facility, you must register in advance to gain access through security.)

If you would like to host a Dojo, or have a suggestion for where we should have one, please get in touch with the CentOS Promo mailing list.

Other upcoming events are always listed on the events wiki 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.

 

March 04, 2019

Greg Kurtzer: Founder of the CentOS project

March 04, 2019 08:09 AM

As I’ve mentioned, as we approach our 15th anniversary, I’ve been talking with some of the people who were around in those early days, to get more of the backstory. (See our YouTube channel for the full interview.)

Last week, I spoke with Greg Kurtzer, who founded the Caos Linux project, which turned into the CentOS Project in 2002. I got an eye-opening story of how it all started.

In October of 2000, Greg, who was already an avid Debian GNU/Linux fan, joined an organization (LBNL) that was a Red Hat shop. (This was before Red Hat Enterprise Linux.) And, while generating packages for work, he decided that what was really needed was a community-managed distribution of RPM-based Linux, much like Debian existed for the dpkg crowd.

Now, in the early days of open source and free software, we had communities that were more defined by personalities than by technologies. Granted, that situation still exists today, but if you didn’t endure the flame wars of the late 90’s and early 2000’s, it can be a little hard to imagine just how bad it sometimes got.

With Caos Linux, Greg had an opportunity to set a new tone for the project as more welcoming, beginner friendly, and encouraging than was the norm at the time.

When Red Hat Linux became Red Hat Enterprise Linux, and the project could no longer use Red Hat Linux as the build system, they began to work with Rocky McGough who was already doing a rebuild of RHEL for his employer. (There were a number of these projects at the time.) He was changing roles professionally, and wanted the project to continue, and so agreed to merge with the work that Greg was doing. Rocky was, effectively, the first technical lead of CentOS. The name itself was coined by a participant in the UK, who will be mentioned again later.

The process was started by Greg to create a 501c3 non-profit entity - the Caos Foundation - which would host the CentOS Project. There was a framework being created to cover governance, funding, and organizing volunteer effort. Unfortunately, the individual who came up with the name ‘CentOS’ also owned the domain name, and declined to release it to the foundation as promised.

Meanwhile, when a RHEL-rebuild project called White Box Linux was discontinued, it became clear that what the community wanted was a free alternative to Red Hat Enterprise Linux. CentOS moved into that space, based on the work that White Box had done.

As CentOS was starting to gain popularity, word came to the project that Rocky had committed suicide. In addition to being very tragic, this presented certain technical difficulties to the project, since he was the technical lead at the time. In hindsight, it is a shame he didn’t get to see what the project would become in time, as the foresight may have prevented this tragedy.

Greg passed on the technical lead position to the individual in the UK who held the domain name, while Greg continued to manage the project, community, and governance side of things. Donations to the project started to come in to support the infrastructure and other needs of the project. And third-party vendors making a business around the project also began to appear and prosper. The project was growing rapidly, and donations to the project were growing rapidly.

From there, due to a number of situations not really germane to this article, Greg moved on, and the CentOS project, through a number of events, came to where it is today. We’ll explore some of these other transitions in upcoming interviews and articles.

Of particular interest to me during my interview with Greg, were his remarks about setting the tone in a project. Being welcoming, kind, and patient takes so little time, but creates a community that people want to participate in, are proud to be part of and which is sustainable for a long time, due to the ability of new participants to enter and feel ownership. I’ve published a separate, much shorter, video with just those remarks, which I’d encourage you take two minutes to watch, too.

March 01, 2019

CentOS Opstools SIG Quarterly Report

March 01, 2019 08:22 AM

CentOS Opstools SIG Quarterly Report
Dec 01, 2018 - Feb 28, 2019

Purpose

Provide tools and, documentation, recommendations and best practices for operators of large infrastructure.

Membership update

We need to be honest to see that contributions decreased over the time. Members moved on, and at the same time, we failed to attract new contributors.

Health and Activity

CentOS opstools packages are being consumed by OpenStack Kolla, and at the same time, for example also by oVirt.

During FOSDEM, we got in touch with collectd upstream. collectd is also integral part of the OPNFV Barometer project. While Barometer provides containers to test the project, the same can be achieved by using packages from CentOS-Opstools.

Architectual-wise, we are shifting from using sensu and fluentd. If anyone is interested in keeping them, it's the right time to step up.

The replacements will be using rsyslog and Prometheus. Currently, we are not building Prometheus under the opstools SIG; interested
persons are encouraged to step up here!

Issues for the Board

None at this point, but we should keep an eye on contributors.

February 27, 2019

CentOS15

February 27, 2019 08:12 AM

Happy birthday, CentOS!

15 years ago, the CentOS project started up in order to fill a gap left by a change in the way that Red Hat decided to market their product.

Many of the people that were involved in those early days are still involved today, although in different capacities than they were then. Over they years, their involvement has changed, due to their own changing job responsibilities, as well as the shifting technological landscape.

Over the next few months, as part of our celebration of our 15 year anniversary, I'm going to be talking with some of these people that were involved in the early days, as well as some that have joined later on, to talk about how and why people get involved in this project.

If you would like to tell your story, please get in touch with me at rbowen@centosproject.org and we'll schedule an interview.

February 25, 2019

CentOS Virtualization SIG Quarterly Report, March 2019

February 25, 2019 08:27 AM

Virtualization SIG quarterly report, Dec 1 2018 - February 28 2019

Purpose

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

https://wiki.centos.org/SpecialInterestGroup/Virtualization

Membership Update

We are always looking for new members.

Tomasz Baranski and Yuval Turgeman joined the SIG for oVirt project.

Releases and Packages

oVirt 4.2 reached end of life with the upstream release of oVirt 4.3. Upstream is planning 4.3.1 to be shipped live on February 26th, the SIG will rebase on that.

On Xen side, Xen 4.8 has been updated to 4.8.5-1

On libvirt side, latest upstream release 5.0 has been tagged for release

Health and Activity

The Virtualization SIG remains fairly healthy. All the projects within the SIG are updating regularly on biweekly meetings.

oVirt had a conference in Milan on November 16th 2018 and is planning a new conference in Rome this spring.

oVirt was also present at Devconf.cz and Fosdem.

Xen 4.10.2 is also available, and the dom0-enabled Linux kernel is at 4.9.127. Release candidate builds of Xen 4.12 are also available.

Issues for the Board

oVirt pushed a patch for having a CentOS appliance including oVirt Guest Agent in https://github.com/CentOS/sig-cloud-instance-build/pull/127

We've updated centos-release-xen to default to Xen 4.8 in the CBS repos.

February 18, 2019

Using buildah to build container images on CentOS

February 18, 2019 09:04 AM

In this post, we're going to talk about how to use buildah to build container images on CentOS.

buildah is a command line tool that facilitates building OCI compliant images. There's a plethora of information available around what buildah is on its GitHub landing page so we won't dive more into what it is. However, it's worth mentioning that buildah helps you build container images without having to run any daemon in the background, unlike the docker CLI tool which requires the Docker daemon to be running in the background.

Installing buildah

buildah is already available in the CentOS repos. All we need to do is:

$ yum install -y buildah
$ buildah -v
buildah version 1.5-dev (image-spec 1.0.0, runtime-spec 1.0.0)

buildah offers a number of features and options. To know about these, simply execute buildah on the command line or refer to its manual page (man buildah).

Building the container image

buildah can build a container image by referring the same Dockerfile that docker build refers to. Let's consider this simple Dockerfile for example. All it does is install the wget package:

$ cat Dockerfile
FROM registry.centos.org/centos/centos

RUN yum install -y wget && yum clean all

Now, build the container image named wget :

$ buildah bud -t wget .
$ buildah images
IMAGE ID             IMAGE NAME                                               CREATED AT             SIZE
2f254a4fff8d         registry.centos.org/centos/centos:latest                 Dec 17, 2018 05:07     210 MB
9b6563cfaff2         localhost/wget:latest                                    Jan 16, 2019 11:01     234 MB

You can use this container image with podman by doing:

$ podman run -it --rm wget bash

podman is a tool for managing pods, containers, and container images. Its website contains extensive detail about its capabilities and uses.

Use the container image with Docker

buildah also makes it possible to use the image thus built via the local Docker daemon. It's as simple as doing a buildah push:

$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

$ buildah images
IMAGE ID             IMAGE NAME                                               CREATED AT             SIZE
2f254a4fff8d         registry.centos.org/centos/centos:latest                 Dec 17, 2018 05:07     210 MB
9b6563cfaff2         localhost/wget:latest                                    Jan 16, 2019 11:01     234 MB

$ buildah push wget:latest docker-daemon:registry.centos.org/centos/wget:latest
Getting image source signatures
Copying blob sha256:b05580fca2f9aabb2d8fa975b29146c9147c8418e559f197c54a4fac04babb95
 200.47 MiB / 200.47 MiB [==================================================] 4s
Copying blob sha256:fa5e7b9f8f4d8f07f7af27cd06269ba16ba0f06cbacacc7c7e96a616da885cab
 22.82 MiB / 22.82 MiB [====================================================] 0s
Copying config sha256:9b6563cfaff28baa1075e86b60c502f85fc31b56bdb641d314a7c61d2e91fae8
 1.33 KiB / 1.33 KiB [======================================================] 0s
Writing manifest to image destination
Storing signatures
Successfully pushed registry.centos.org/centos/wget:latest@sha256:66f4c1c8378c7d9e22a0d3c9a0943739082dfeae3344e5f2b069e9c9ddf08271

$ docker images
REPOSITORY                        TAG                 IMAGE ID            CREATED             SIZE
registry.centos.org/centos/wget   latest              9b6563cfaff2        6 minutes ago       226 MB

Initially, the local Docker daemon storage had no container images. We did buildah push wget:latest docker-daemon:registry.centos.org/wget:latest to push the image to local Docker daemon's storage. Now doing docker images shows the image and can then be used with docker run

That's it

In this blog, we saw simple steps that need to be performed to install and use buildah to build OCI images which can then be pushed to local Docker daemon's storage. buildah can also push container images to the remote registry. It is highly recommended to read the documentation to know about more features and capabilities of buildah.

In a future blog, we will share how the CentOS Container Pipeline team managed to build container images on OpenShift using buildah.

February 14, 2019

Videos from FOSDEM Dojo now live

February 14, 2019 03:56 PM

Just a quick update - the schedule from the recent CentOS Dojo at FOSDEM has been updated to include the videos from each presentation.

Note: Three of the talks are missing video due to equipment failure.

February 07, 2019

CentOS Pulse Newsletter, February 2019 (#1902)

February 07, 2019 03:57 AM

Dear CentOS enthusiast,

Another month into 2019, and we have a lot to tell you about.

Releases and updates

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:

SIG Updates

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

Several of our SIGs published their quarterly reports this month:

Next month we hope to hear from:

  • Artwork
  • Cloud Instance
  • OpsTools
  • Public CI
  • Virtualization

Events

We started off February with a bang, with our annual CentOS Dojo at FOSDEM.  You can read a summary of that event on the CentOS blog. We will be posting video from the event on the CentOS YouTube channel as soon as possible.

We also had a table at FOSDEM itself. FOSDEM is a gathering of 6000 free/open source software enthusiasts at Brussel's ULB. Topics covered are everything from distributions to licensing to community to storage. Video from almost every session at the event is already available at the event website.

Next month, we expect to have a presence at FOSSAsia in Singapore.

And in April we are planning to hold a Dojo at Oak Ridge National Labs, in Oak Ridge Tennessee.

If you would like to host a Dojo, or have a suggestion for where we should have one, please get in touch with the CentOS Promo mailing list.

Other upcoming events are always listed on the events wiki 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.

 

February 06, 2019

Releases/updates on Feb 1

February 06, 2019 07:05 PM

On February 1st (last week) there were a large number of enhancements/updates released by the CentOS community:

 

Errata and Enhancements Advisories

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

Errata and Security Advisories

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

Errata and Bugfix Advisories

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

CentOS Dojo @ FOSDEM 2019

February 06, 2019 06:16 PM

On Friday of last week, we once again gathered in Brussels for our annual CentOS Dojo at FOSDEM.

14 speakers gave talks on a wide variety of topics, ranging from deeply technical, to community-centered, to a vision of what's coming in CentOS 8. The full schedule is on the event website, and the videos from the event will be posted on YouTube as soon as we can possibly get them up.

We had roughly 90 people in attendance at this event, which was about the same as last year.

At lunch time, we celebrated CentOS's 15th birthday with a lovely birthday cake.

(More pictures here.)

If you missed us in Brussels, don't worry. We have lots of other events coming up.

If you would like to host a Dojo, or have a suggestion of where we should run on, please don't hesitate to get in touch with us on the CentOS-Promo mailing list.

February 03, 2019

Updated CentOS Vagrant Images Available (v1901.01)

February 03, 2019 08:50 AM

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 January 28th, 2019.

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.

Downloads

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"
  end
end

Feedback

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.

Ackowledgements

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.

January 30, 2019

CentOS NFV SIG Quarterly Report

January 30, 2019 08:42 PM

NFV SIG Quarterly Report through February 1st, 2019

Purpose

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.

Membership Update

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.

Releases and Packages

fd.io VPP

The past quarter has been a slow one in terms of actual delivered packages. Our main active package, VPP has not been released since 1807. Upstream version 1810 requires dev-toolset 7.

However, recently dev-toolset-7 and all prerequisites have been built and-or cross tagged into the NFV SIG common. We are currently in the process of building vpp 19.01 for release and plan to have these packages ready in February.

To install latest release of VPP,

yum install centos-release-fdio

yum install vpp*

Health and Activity

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

including vpp.

At this point, the project is looking for a renewed focus. Perhaps, packages to facilitate containerization and kubernetes. Other ideas and sponsors are welcome.

Also, we have also been working towards several upcoming events.

On February 1st, we will have a presentation about NFV SIG at  CentOS Dojo at FOSDEM, in Brussels.

Issues for the Board

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

 

January 24, 2019

Promo SIG quarterly report, February 2019

January 24, 2019 03:37 PM

As per the SIG reporting guide, the Promo SIG offers its quarterly report for the period from Nov 1, 2018 through Feb 1, 2019

Purpose

The CentOS Promotion SIG exists to provide promotion, and consistent messaging, of CentOS, both at physical events and online.

Membership Update

In the reporting period, we have had participation from a handful of people. We are always looking for additional community participation in all aspects of this SIG, including, but not limited to, helping out at events.

Anyone interested in participating in the Promo SIG should subscribe to the mailing list.

Activity

The past quarter has been a slow one in terms of actual event participation.

We had a presence at the Supercomputing event SC18 in Dallas, Texas, where Rich Bowen interviewed some of the student cluster competition teams. Those videos may be seen on the CentOS YouTube channel.

We have also been working towards several upcoming events.

On February 1st, we will be holding the annual CentOS Dojo at FOSDEM, in Brussels. At the time of this writing, we have 125 people registered for the event. A followup event report will be posted here in the next 2 weeks.

In April, we are planning to hold a Dojo at ORNL, in Oak Ridge, Tennessee, USA. The schedule is coming together and we should be announcing more details immediately after FOSDEM.

Later in 2019, we plan to hold dojos at DevConf.US, and DevConf.IN. No details are available for either of these events, but should be announced in the next month.

Each month we publish the community newsletter. These may be read on this blog, and are listed in the wiki.

We are planning various things around the upcoming 15th anniversary of the CentOS project, including birthday cakes at various of our Dojos, and a series of interviews with people who have been around the project for many years. We hope to record some of these interviews at FOSDEM, and others both online, and at upcoming events during the year. If you would like to be interviewed, please contact Rich on the promo mailing list.

This has been a slow quarter for social media, as November and December often are. However, we continue to post content to Twitter, Facebook, LinkedIn, and Reddit. With the announced retirement of Google+, we have discontinued posting content there.

January 15, 2019

CentOS PaaS SIG Quarterly report

January 15, 2019 12:07 PM

Purpose

The CentOS PaaS SIG is working on delivering multiple PaaS Stacks that are built, tested and delivered into the CentOS Ecosystem for end user consumption, run as a service and also provided in various formats ( rpms, containers, images etc ) for other efforts in the CentOS Ecosystem, that can derive value from this content.

Releases and Packages

OKD 3.11 has released in this quarter and we keep working on maintaining the packages while the updates are coming from the main repository. We provide also the openshift-ansible package containing all playbooks to deploy OKD on CentOS environments.

To install openshift-ansible package, run the command:

yum install openshift-ansible

Biweekly meetings

The SIG decided to host biweekly meetings due to low traffic of information. We invite everyone to join the meeting and ask for help, improvements, and collaboration. Our meeting is biweeklyWednesdays at 17:00 UTC. You can check your timezone time with the command:

date -d "1700 UTC"

January 14, 2019

Updated CentOS Vagrant Images Available (v1812.01)

January 14, 2019 08:52 PM

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 January 1st, 2019.

Important changes

The centos/7 images use the XFS filesystem again (we had to temporarily switch to ext4 due to filesystem corruption involving qemu and XFS in 7.5.1804).

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.

Downloads

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"
  end
end

Feedback

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.

Ackowledgements

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.

January 08, 2019

CentOS SCLo SIG Quarterly report

January 08, 2019 03:21 PM

CentOS SCLo SIG Quarterly report

Purpose

Packaging and maintaining Software Collections packages,
providing the ability to install several versions of various software side by side.

Releases and packages

Several new software collections were provided:

Some older software collections were retired due to their upstream End-of-Life status.
If a collection you depend on vanished from the repositories,
it is advised to upgrade to a newer variant of that collection as soon as possible.
As a last resort, the retired and unsupported packages can be found at CentOS vault.

CentOS Pulse Newsletter, January 2019 (#1901)

January 08, 2019 02:41 PM

Dear CentOS enthusiast,

We wish you a happy and prosperous 2019, full of CentOS!

Releases and updates


December was a very busy month for releases and updates. The following releases and updates happened in December. 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 December:

Errata and Security Advisories

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

Errata and Bugfix Advisories

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

Other releases

The following releases also happened during December:

 

SIG Updates

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

Cloud SIG

Last month the Cloud SIG produced a detailed quarterly report, which you can read in a separate post. This kind of detailed report is what we'd love to see from other SIGs in the future.

Software Collections SIG

The Software Collections SIG has also published a quarterly report, covering their progress in the last few months.

Other SIG Reports

Due to so many people taking time off in December to spend time with friends and family, several other SIG reports are running a little late. Don't worry, they're on the way, and you can see them here, on blogs.centos.org, in the next week or two. Thanks for your patience!

Events

Upcoming events

Coming up in February, we'll be participating in FOSDEM, with a table in the expo area, as most years. Drop by for all your CentOS sticker needs, or to tell us about what you're doing with CentOS! You can find out more about FOSDEM on their website at https://fosdem.org/2019/.

And, on the day before FOSDEM starts, we'll be holding our annual CentOS Dojo, at the Marriott near Grand Place. We'll have a full day of technical presentations (two tracks!) and, of course, the always valuable hallway track where you can talk with other people in the CentOS community. Attendance is free, but we need you to register, so that we can plan. Details, the schedule, and the registration like, are all on the event website at https://wiki.centos.org/Events/Dojo/Brussels2019

There's a lot of other events around FOSDEM, too, that you might want to check out. These are loosely called the FOSDEM Fringe, and are listed here: https://fosdem.org/2019/fringe/

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.

 

January 02, 2019

CentOS Cloud SIG Quarterly Report

January 02, 2019 08:54 PM

01 September 2018 - 31 November 2018

Purpose

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

https://wiki.centos.org/SpecialInterestGroup/Cloud

Membership Update

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

The SIG agreed to replace the inactive SIG Chair, Kushal Das, with new chair Rain Leander, at the recent SIG gathering at CERN, in October.

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

RDO

Aug 27 - Aug 31 Rocky Release https://blogs.rdoproject.org/2018/09/rdo-rocky-released/

Interesting features in the Rocky release include:

  • New neutron ML2 driver networking-ansible has been included in RDO. This module abstracts management and interaction with switching hardware to Ansible Networking.
  • Swift3 has been moved to swift package as the “s3api” middleware.

Other improvements include:

  • Metalsmith is now included in RDO. This is a simple tool to provision bare metal machines using ironic, glance and neutron.

The full release notes are at https://releases.openstack.org/rocky/highlights.html

Sep 10 - Sep 14 Stein Release Project Team Gathering

Oct 22 - Oct 26 Stein-1 milestone

Health and Activity

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

In recent days, CloudStack has indicated an interest in once again participating in the SIG, with an eye towards providing CloudStack 4.11.2.0 rpms, and having more visibility in CentOS 8, in particular, once that is released.

Currently OpenStack group is focusing in preparing CentOS 8 support (E.g: python3, podman) through a fork of Fedora 28. This repository is used in upstream and downstream CI to reduce the gap as much as possible when CentOS 8 will be available.

Issues for the Board

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

Reminder: CentOS Dojo at FOSDEM just a few weeks away

January 02, 2019 05:09 PM

We're looking forward to seeing all of you in Brussels next month!

The annual FOSDEM CentOS Dojo will be happening, as usual, on the Friday
before FOSDEM starts - February 1st, 2019 - at the Marriott Grand Place,
just a few minutes walk from Grand Place.

We do ask that you register, so that we can plan for space, budget, and
coffee breaks. We are currently about two thirds full, so don't wait!

More details, including the full schedule of presentations, and the
registration link, are on the event website:

https://wiki.centos.org/Events/Dojo/Brussels2019 

See you in Brussels!

December 13, 2018

Fasttrack is back!

December 13, 2018 09:02 PM

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)

Pablo.

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

December 08, 2018

Updated CentOS Vagrant Images Available (v1811.01)

December 08, 2018 09:45 AM

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.

Downloads

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"
  end
end

Feedback

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.

Ackowledgements

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.

December 07, 2018

CentOS Atomic Host 7.1811 Available for Download

December 07, 2018 08:57 PM

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-0.11.1.1-3.git594495d.el7.centos.x86_64
  • 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.

Upgrading

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.

December 06, 2018

Using go-toolset on CentOS Linux 7/x86_64

December 06, 2018 01:30 PM

With golang now gone from the CentOS Linux 7 distro ( deprecated upstream ), the best way to get golang for your system is to get it from the SCL.

Firstly, enable scl itself :

yum install centos-release-scl

Then install the go-toolset-7 scl ( this brings in version 1.10.2 at the moment )

yum install go-toolset-7

In order to use it, interactively you can run the scl enable command, which would also involve spawning a new shell. Note that the /bin/bash can be replaced with the commmand or shell you want to work in :

$ scl enable go-toolset-7 /bin/bash
$ go version
go version go1.10.2 linux/amd64
$ which go
/opt/rh/go-toolset-7/root/usr/bin/go

If you want, like I do, want to just make this the default go for all our shells, add something like this to your .bashrc

source scl_source enable go-toolset-7

MAny thanks to the CentOS SCL SIG for shipping this go-toolset collection.

December 04, 2018

CentOS Pulse Newsletter, December 2018 (#1807)

December 04, 2018 08:06 AM

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.

Events

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.

 

November 26, 2018

Why your project should participate in a CentOS SIG

November 26, 2018 03:13 PM

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.

November 14, 2018

Student supercomputing is #PoweredByCentOS at SC18

November 14, 2018 03:45 PM

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.

 

 

November 09, 2018

OKD v3.11 packages now available

November 09, 2018 07:18 PM

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/

 


Powered by Planet!
Last updated: March 24, 2019 12:00 AM