The newest version of Fedora is jam-packed with the latest basic technologies. Because the Fedora project is the test bed for Red Hat’s enterprise distributions, administrators can take a sneak preview at technologies intended for later use in RHEL and RHEV.

Fedora 16 continues to occupy its place as a pioneer of Linux technology, with key features such as Linux kernel 3.1 and Gnome 3.2.1. The Fedora-customized Gnome version 3.2.1 has what it takes to rocket up to the top of the must-have chart for non-KDE users – and to take users away from Ubuntu in the wake of the problems with Ubuntu’s Unity desktop. The Gnome version that comes with Fedora 16 is definitely a more convincing package than Unity; however, from an administrator’s point of view, the pillars of Gnome 3.2.1, including desktop features such as the integration of online accounts, are probably not the most important aspects. Instead, administrators and developers will be more interested in the development tools that Fedora 16 includes, such as Perl 5.14, the GCC Python plugins, the Haskell platform, and D2 – the latest version of the D programming language – or the SELinux access control system, which Fedora enables by default. But at the top of the administrator’s list has to be kernel 3.1, with its new KVM and Xen functionality, and Fedora 16’s above average collection of virtualization and cloud computing tools.

^{New Kernel 3.1}

Much of the professional attention to Fedora 16 will fall on the new Linux kernel 3.1. The first thing to notice is that Fedora doesn’t automatically benefit from the changes to the Btrfs filesystem, such as the modified locking mechanisms, which mainly provide more speed. The Red Hat developers toyed with the idea of making Btrfs the standard filesystem but decided to stay with ext4; the main reason for keeping with ext4 is the shortage of repair tools for Btrfs, as well as the conclusion that Btrfs is still too experimental for production settings.

The ipset tool for configuring IP sets within the kernel was first added in kernel 2.6.39 and has seen some improvements that now allow it to support firewall code for more flexible use of tables and filter information. At the same time, a fairly large patch has been applied to the new kernel to upgrade the iSCSI target framework LIO, which was introduced in kernel 2.6.38, to LIO 4.1. The kernel code for software RAID now supports bad block management for RAID levels 1, 4, 5, and 6 and can thus identify defective disk sectors on the disks used for the RAID array.

Dm-crypt, which kernel 3.1 uses for disk encryption, can now pass discard commands through to the underlying medium. Besides the regular improvements in hardware support, the kernel developers have mainly implemented important optimizations to extend the feature set or improve the speed of the kernel-based KVM and Xen virtualization solutions. After adding the last missing components for cooperation with the Xen hypervisor to kernel version 3.0, the developers turned their attention to the Xen PCI back end in kernel 3.1, which now supports PCI/PCIe device pass-through to Xen guests.

More interesting for Fedora is the fact that the kernel code for KVM now possesses basic functionality to allow systems with Intel processors to launch guest systems with a different guest system (nested virtualization). The KVM kernel code for AMD processors added nested virtualization back in 2009. Additionally, kernel 3.1 now has experimental support for zero-copy RX for MacVTap and VHostNet, although this is still disabled by default. Zero-copy RX improves network performance in virtualization by reducing the management overhead that occurs on receiving or passing through network data.

^{Fedora Cloud}

Red Hat has quite obviously been pursuing a strategy of strengthening its position on the virtualization market through targeted acquisitions in recent years. Red Hat’s own enterprise products on the virtualization market still rely on free technologies like KVM, but since Red Hat owns KVM, it can exert a major influence in the ongoing development of what is currently the virtualization technology with the strongest growth.

Red Hat’s own enterprise virtualization solution, RHEV, confidently positions itself as the third force besides VMware and Citric XenServer in the battle to become the largest infrastructure provider. Users of Fedora 16 benefit from technologies developed for RHEV that go well beyond what other distributions can offer.

When it comes to cloud computing, Fedora 16 includes the HekaFS 0.7 distributed filesystem, a version of GlusterFS designed for the cloud. While HekaFS provides a cloud-capable distributed filesystem, cloud instances can be created and managed using the Aeolus Conductor (Figure 1) web front end.

Figure 1: Fedora includes the Aeolus web-based cloud management tool.

Additionally, Fedora 16 includes the cloud high-availability solution Pacemaker and the OpenStack tools that allow administrators to configure and operate cloud and storage solutions, as well as the Condor Cloud IaaS implementation.