HOWTORHEL 8

RHEL 8 Resources

RHEL 8 Console

Red Hat announced the general availability of Red Hat Enterprise Linux 8 (RHEL 8) at Red Hat Summit on 7 May 2019.

The following page attempts to bookmark RHEL 8 resources that might be useful for sysadmins that are looking forward to deploying this release.

Official Documentation

Supporting Blog Posts

May 2029

RHEL 8 will be supported for 10 years. That’s right, the same Operating System you install today will continue to receive updates until May 2029! Deploy today and know you will be covered for the future.

6 Month Update Cycle

Minor releases are planned for release every six months, rather than the somewhat ad-hoc 6-9 month releases we have experienced in the past. This should be a good thing and help with planning. Red Hat is simplifying the RHEL product phases from four to three: Full Support, Maintenance Support, and Extended Life Phase. For additional details, see:

About RHEL 8

Red Hat Enterprise Linux 8 (Ootpa) is based on Fedora 28, upstream Linux kernel 4.18, systemd 239, and GNOME 3.28

Satellite 6 Support

RHEL 8 clients should be able to communicate with the upcoming Satellite 6.5 release. Packages should be there in the 6.5 Tools repo.

Spacewalk Support

Although you cannot run Spacewalk on RHEL8, Spacewalk 29 supports RHEL 8 clients. From the Spacewalk 29 release notes:

Spacewalk server is now capable of syncing and distributing of Red Hat Enterprise Linux 8 Beta content.

https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes29

However, note the following caveat which was posted on Reddit:

you should be to manage RHEL 8 systems pretty well, only issue I see is that in case you’re using modularity feature, spacewalk might be suggesting you incorrect updates (as the modularity logic is not implemented there).

https://www.reddit.com/r/redhat/comments/blv8au/is_spacewalk_able_to_manage_rhel_8_systems/

Ansible

At first glance, it looks as though there is a problem with the repository that has been configured on RHEL 8 installations. Note the package count of zero in the ansible-2.8-for-rhel-8-x86_64-rpms repository.

[root@unixsysadmin #] yum repolist
Updating Subscription Management repositories.
Last metadata expiration check: 1:01:28 ago on Sat 11 May 2019 09:11:43 AM BST.
repo id repo name status
ansible-2.8-for-rhel-8-x86_64-rpms Red Hat Ansible Engine 2.8 for RHEL 8 x86_64 (RPMs)          0
rhel-8-for-x86_64-appstream-rpms   Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 4,903
rhel-8-for-x86_64-baseos-rpms      Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs)    1,939

You may recall that in RHEL 7, Ansible was available in the Extras Channel, but then deprecated (https://access.redhat.com/articles/3359651).

For RHEL 8, you will need an Ansible Engine subscription. Note that the repository for Ansible 2.8 is setup as of the RHEL GA release date, but 2.8 is due to be released on 16 May. See https://github.com/ansible/ansible/commits/devel/docs/docsite/rst/roadmap/ROADMAP_2_8.rst and https://www.reddit.com/r/redhat/comments/bmmkhn/rhel8_where_is_ansible/
Alternatives to this include waiting for community releases of Ansible to appear in EPEL 8 (see later in this post) or run pip3 install ansible if you can’t wait for an RPM release.

Puppet

Packages for Puppet can be found at https://yum.puppetlabs.com/puppet/el/8/x86_64/

EPEL 8

RHEL 8 is new, give the team some time! Developer mailing list thread: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/BBPR7WKUMOYGLANPB7DBXNQNJZPPIGWD/

Universal Base Image

Moving to containers is seen as a big step forward in security. However, the supply chain around the container becomes very important. Rather than one O/S running on your server, you’ll now have many containers running from potentially many different sources. How can you ensure your base image comes from a reputable source? Historically, users have used Apline Linux, Fedora, Ubuntu or Centos as a base as they were readily available. Now however, all users (a Red Hat customer or not) can take a base image from Red Hat: Introducing the Red Hat Universal Base Image

The Red Hat Universal Base Image is available to all developers with or without a Red Hat Enterprise Linux subscription, providing a more secure and reliable foundation for building enterprise-ready containerized applications. Applications built with the Universal Base Image can be run anywhere and will experience the benefits of the Red Hat Enterprise Linux life cycle and support from Red Hat when run on Red Hat Enterprise Linux or Red Hat OpenShift Container Platform.

https://www.redhat.com/en/about/press-releases/red-hat-enterprise-linux-8-every-enterprise-every-cloud-every-workload

There are three images available – ubi (208 MB), ubi-minimal (90 MB) and ubi-init (223 MB)

The following graphic gives a good comparison of the UBI versions: https://www.redhat.com/cms/managed-files/styles/wysiwyg_full_width/s3/blog%204.png?itok=7ED4YTCp

It’s easy to get started:

For UBI 8:
podman pull registry.access.redhat.com/ubi8/ubi
podman pull registry.access.redhat.com/ubi8/ubi-minimal
podman pull registry.access.redhat.com/ubi8/ubi-init

For UBI 7:
podman pull registry.access.redhat.com/ubi7/ubi
podman pull registry.access.redhat.com/ubi7/ubi-minimal
podman pull registry.access.redhat.com/ubi7/ubi-init

https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image

Live Upgrade Limitations

Virt-Manager

Although still supported in RHEL 8, virt-manager has been deprecated. The RHEL 8 web console is intended to become its replacement in a subsequent release. It is, therefore, recommended that you get familiar with the web console for managing virtualization in a GUI. However, in RHEL 8, some features may only be accessible from either virt-manager or the command line.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_virtualization/index

Release Dates

Release dates for all RHEL releases can be found at Red Hat Enterprise Linux Release Dates.

Modularity / Application Streams

Network Scripts

Red Hat Enterprise Linux 8 (RHEL 8) has deprecated the network scripts that have been used in previous RHEL releases. RHEL 8 now comes with new versions of the ifup and ifdown commands which call the nmcli tool. See RHEL 8 Configure IP Address.

DNF / YUM

yum is a symlink to dnf – in general you can run ‘yum’ commands as you’ve done in the past or switch the new ‘dnf’ command and provide the same arguments to ‘dnf’ as you are used to with ‘yum’. Eg: ‘dnf update’, ‘dnf repolist’.

Centos 8

Centos 8.0.1905 will be based on RHEL 8. For full details and progress see https://wiki.centos.org/About/Building_8

VMware

You can view the products for which RHEL 8 is certified on VMware at the following URL: VMware Compatibility Guide

See also RHEL 8 Beta install fails on VMWare Workstation and Reddit Thread: RHEL 8 Beta

Remi Repository

Third party repository provider Remi has made a RHEL 8 repository available.

Dell

According to https://www.dell.com/community/Systems-Management-General/RHEL-8-support/td-p/7300982 “RHEL8 support is with September release of OpenManage Server Administrator(OMSA)”.

HPE

Veritas

The following links will show support for RHEL8:

News Articles

Leave a Reply

Your email address will not be published. Required fields are marked *