Fedora 27 Atomic Offers Multi-Arch Support, Workstation, Containerized Kubernetes, and More

Fedora 27 Atomic Host became available at the same time as Fedora 27, and we’ve included a bunch of changes and features to make it an even better platform for your container cloud. Highlights of this version include multi-architecture support, containerized Kubernetes, Workstation, a single OverlayFS volume by default, and new OSTree layering capabilities.

Multi-Architecture Support

Thanks to tremendous efforts across the Fedora project, Fedora 27 Atomic Host is available for 64-bit ARM and Power8 processor architectures as well as 64-bit Intel (i.e. AArch64, ppc64le and x86_64). Not only are we distributing ISOs and cloud images for all three architectures, we will also be providing two-week OSTree updates for them as well.

Our project has seen strong demand for multiple architectures for a while, particularly from people working on Internet of Things (IoT) projects, who want Atomic Host’s update and rollback capabilities. We’re happy to be able to finally satisfy these users. Sinny Kumari, who worked on the multi-arch support, explains more about it.

ARM64 Overdrive1000 running Atomic Host. Server loaned to Fedora by the ARM coalition.

ARM64 Overdrive1000 running Atomic Host. Server loaned to Fedora by
the ARM coalition.

Containerized Kubernetes

As planned, the Kubernetes binaries have been removed from the base image for Atomic Host. This change both shrinks the base image size, and allows users to install the container orchestration platform and version of their choice, whether it’s Kubernetes, OpenShift, or something else.

Users will now need to install Kubernetes using package layering, or, preferably, as system containers. To support this, the Fedora Layered Image Build System (FLIBS) repository now includes supported system container images for Kubernetes, etcd, and flannel. If you’re upgrading from Fedora 26 Atomic Host, Jason Brooks explains how to upgrade Kubernetes.

Atomic Workstation Updates

For over a year, Fedora contributors have been experimenting with an RPM-OStree build of Fedora Workstation, with all of their applications running in containers or Flatpaks. This spin is informally known as “Atomic Workstation.” We are now expanding that experiment, by offering regular automated updates to the Atomic Workstation image and OStree refs, starting with Fedora 27. While not yet ready for most users, Atomic Workstation offers benefits, such as rollback, to developers who want to test the latest builds of Fedora.

One Big OverlayFS2 Volume

Having tested OverlayFS2 through the Fedora 26 cycle, we are now committing to it. New Atomic Host systems will now get a single filesystem volume by default, which will share binaries, system containers, and OCI/docker containers using OverlayFS2. This change will make installation simpler for new users, as well as being appropriate for small public cloud instances. It’s also consistent with the defaults on other Fedora Editions. Users who need to partition container images and storage onto separate volumes can still do so, using kickstart options and container-storage-setup configuration.

More OSTree Package Layering

In the biweekly Atomic Host updates, we’ve tested out some additional capabilities for RPM-OSTree that give administrators more flexibility in how to add software to hosts. First, remove and replace overrides allow system owners to experiment with changes to the software mix on their host image, including replacing existing binaries with different versions. Second, LiveFS layering eliminates the need to reboot when the only RPM-OSTree change a user makes is adding software.

Upgrading and Support Policy

With the release of Fedora 27 Atomic Host, updates to the Fedora 26 Atomic Host will be strictly on a best-effort basis. As such, we strongly encourage users to upgrade to the new release soon. Upgrade instructions are on the Project Atomic blog.

The Fedora team is proud of the new release, and hopes that you will find it more powerful and easier to use. Download it and try it out soon.

Fedora Project community

4 Comments

  1. Keti Zilgish

    Does this article have anything to do with the upgrading of the Workstation from 26 to 27?

  2. Joseph Mullally

    Awesome project. I’m using Fedora Atomic 27 on a rented dedicated host for a single-node Openshift instance (using the openshift-ansible installer) for development purposes. It works great. I’m using a system container for VPN (https://github.com/ibotty/atomic-ipsec-libreswan), but I might try using “rpm-ostree install libreswan” instead to keep it up to date.

    For anyone who wants to install this on a dedicated host where the provider doesn’t provide images out of the box, but does supply rescue images with QEMU, you can do something like this: (or use virt-install if they have it). Make sure drives are unmounted / RAID unloaded from the host before continuing.

    (rescue image) $ qemu-system-x86_64 \
        -enable-kvm \
        -cpu host \
        -smp 2 \
        -m 2048 \
        -k en-us \
        -drive=/dev/sda \
        -drive=/dev/sdb \
        -device virtio-net,netdev=mynet0,mac=11:22:33:AA:BB:CC \
        -netdev user,id=mynet0 \
        -usbdevice tablet \
        -vnc 127.0.0.1:1 \
        -monitor stdio \
        -drive media=cdrom,file=/tmp/Fedora-Atomic-ostree-x86_64-27-20171129.0.iso \
        -boot d

    (localhost) $ ssh root@REMOTEHOST -N -o ExitOnForwardFailure=yes -L 5901:localhost:5901 &
    (localhost) $ vncviewer localhost:1

    To use kickstart files, with the newer Anaconda installers all you need to do is put ks.cfg on a seperate “OEMDRV” labeled ISO and it will be run automatically:
    $ vi oemdrv/ks.cfg
    $ mkisofs -V OEMDRV -o oemdrv.iso oemdrv/
    then add this to the QEMU line:
    -drive media=cdrom,file=/tmp/oemdrv.iso

    Ref:
    https://www.projectatomic.io/blog/2016/10/install-with-kickstart/
    https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html

    • Joseph Mullally

      I forgot to mention, running QEMU under screen is a good idea to prevent the install from failing if the SSH session dies

Comments are Closed

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions

%d bloggers like this: