CoreOS

CoreOS

OS family	Unix-like
Working state	In development
Source model	Open source
Initial release	October 3, 2013 (2013-10-03)[1]
Latest release	660.0.0[2] / April 22, 2015 (2015-04-22)
Latest preview	659.0.0[3] / April 21, 2015 (2015-04-21)
Marketing target	Servers and clusters
Kernel type	Monolithic (Linux kernel)
License	Apache License 2.0[4][5]
Official website	coreos.com

CoreOS is an open source lightweight operating system based on the Linux kernel and designed for providing infrastructure to clustered deployments, while focusing on automation, ease of applications deployment, security, reliability and scalability. As an operating system, CoreOS provides only the minimal functionality required for deploying applications inside software containers, together with built-in mechanisms for service discovery and configuration sharing.^[6][7][8][9]

CoreOS is a fork of Chrome OS, by the means of using its software development kit (SDK) freely available through Chromium OS as a base while adding new functionality and customizing it to support hardware used in servers.^[8][10]:7:02 As of July 2014, CoreOS is actively developed, primarily by Alex Polvi, Brandon Philips and Michael Marineau,^[7] with its major features (other than etcd and fleet) available as a stable release.^[11][12][13]

Overview

CoreOS provides no package manager as a way for the distribution of applications, requiring instead all applications to run inside their containers. A single control host (CoreOS instance) runs multiple isolated Linux systems (containers), using Docker as an additional layer of abstraction and interface^[14] to the underlying operating-system-level virtualization features of the Linux kernel. That way, resource partitioning is performed through multiple isolated userspace instances, instead of using a hypervisor and providing full-fledged virtual machines. This approach relies on the Linux kernel's cgroups functionality, which provides namespace isolation and abilities to limit, account and isolate resource usage (CPU, memory, disk I/O, etc.) for the collections of processes.^[6][9][15]

CoreOS uses systemd as its primary init system, with tight integration between it and various CoreOS' internal mechanisms.^[6][16]

Updates distribution

For additional security and reliability of operating system updates, CoreOS employs FastPatch as a dual-partition scheme for the read-only part of its installation, meaning that the updates are performed as a whole and installed onto a passive secondary boot partition, which becomes active upon reboot or kexec. This approach avoids possible issues arising from updating only certain parts of the operating system, ensures easy rollbacks to a known-to-be-stable version of the operating system, and allows each boot partition to be signed for additional security.^[6][9][17] The root partition and its root file system are automatically resized to fill all available disk space upon reboots; while the root partition provides read-write storage space, the operating system itself is mounted read-only under /usr.^[18][19]

To ensure that only a certain part of the cluster reboots at once when the operating system updates are applied, preserving that way the resources required for running deployed applications, CoreOS provides locksmith as a reboot manager. Using locksmith, it is possible to select between different update strategies that are determined by how the reboots are performed as the last step in applying updates; for example, it may be configured how many cluster members are allowed to reboot simultaneously. Internally, locksmith operates as the locksmithd daemon that runs on cluster members, while the locksmithctl command-line utility manages configuration parameters.^[20][21] locksmith is written in the Go language and distributed under the terms of the Apache License 2.0.^[22]

The updates distribution system employed by CoreOS is based on Google's open source Omaha project, which provides a mechanism for rolling out updates and the underlying request–response protocol based on XML.^[23][24] Additionally, CoreOS provides CoreUpdate as a web-based dashboard for the management of cluster-wide updates. Operations available through CoreUpdate include assigning cluster members to different groups that share customized update policies, reviewing cluster-wide breakdowns of CoreOS versions, stopping and restarting updates, and reviewing recorded update logs. CoreUpdate also provides a HTTP-based API that allows its integration into third-party utilities or deployment systems.^[17][25][26]

Cluster infrastructure

A high-level illustration of the CoreOS cluster architecture^[27]

CoreOS provides etcd, a daemon that runs across all computers in a cluster and provides a dynamic configuration registry, allowing various configuration data to be easily and reliably shared between the cluster members. Since the key–value data stored within etcd is automatically distributed and replicated (with automated master election), all changes in stored data are reflected across the entire cluster, while the achieved redundancy prevents failures of single cluster members from causing data loss. Beside the configuration management, etcd also provides service discovery by allowing deployed applications to announce themselves and the services they offer. Communication with etcd is performed through an exposed API, which internally uses JSON on top of HTTP; the API may be used directly (through curl or wget, for example), or indirectly through etcdctl, which is a specialized command-line utility also supplied by CoreOS.^{[6][9][28][29][30]}

CoreOS also provides so-called fleet functionality, based on the fleetd cluster manager daemon that controls CoreOS' separate systemd instances at the cluster level. By using fleetd, CoreOS creates a distributed init system that ties together separate systemd instances and a cluster-wide etcd deployment; internally, fleetd daemon communicates with local systemd instances over D-Bus, and with the etcd deployment through its exposed API. Using fleetd allows single or multiple containers to be deployed cluster-wide, with more advanced options including redundancy, failover, deployment to specific cluster members, dependencies between containers, and grouped deployment of containers. Command-line utility called fleetctl is used to configure and monitor this distributed init system; internally, it communicates with the fleetd daemon using a JSON-based API on top of HTTP, which may also be used directly. When used locally on a cluster member, fleetctl communicates with the local fleetd instance over a Unix domain socket; when used from an external host, SSH tunneling is used with authentication provided through public SSH keys.^{[31][32][33][34][35]}

All of the above mentioned daemons and command-line utilities (etcd, etcdctl, fleetd and fleetctl) are written in the Go language and distributed under the terms of the Apache License 2.0.^[5][36]

Deployment

When running on dedicated hardware, CoreOS can be either permanently installed to local storage, such as a hard disk drive (HDD) or solid-state drive (SSD),^[37] or booted remotely over a network using Preboot Execution Environment (PXE) in general, or iPXE as one of its implementations.^[38][39] CoreOS also supports deployments on various hardware virtualization platforms, including Amazon EC2, DigitalOcean, Google Compute Engine, Microsoft Azure, OpenStack, QEMU/KVM, Vagrant and VMware.^{[9][40][41][42]}

CoreOS can also be deployed through its commercial distribution called Tectonic, which additionally integrates Google's Kubernetes as a cluster management utility. As of April 2015, Tectonic is planned to be offered as beta software to select customers.^[43][44]

See also

• Application virtualization – software technology that encapsulates application software from the operating system on which it is executed
• Comparison of application virtualization software – various portable and scripting language virtual machines
• Comparison of platform virtualization software – various emulators and hypervisors, which emulate the whole physical computers
• LXC (Linux Containers) – an environment for running multiple isolated Linux systems (containers) on a single Linux control host
• Operating-system-level virtualization implementations – based on operating system kernel's support for multiple isolated userspace instances
• Software as a service (SaaS) – a software licensing and delivery model that hosts the software centrally and licenses it on a subscription basis
• Virtualization – a general concept of providing virtual versions of computer hardware platforms, operating systems, storage devices, etc.

References

External links

Wikimedia Commons has media related to CoreOS.

• Official CoreOS and Tectonic websites
• CoreOS at DistroWatch
• First glimpse at CoreOS, September 3, 2013, by Sébastien Han
• CoreOS: Linux for the cloud and the datacenter, ZDNet, July 2, 2014, by Steven J. Vaughan-Nichols
• What's CoreOS? An existential threat to Linux vendors, InfoWorld, October 9, 2014, by Matt Asay
• CoreOS fleet architecture, August 26, 2014, by Brian Waldon et al.
• CoreOS is building a container runtime, Rocket, December 1, 2014, by Alex Polvi
• Running CoreOS on Google Compute Engine, May 23, 2014
• CoreOS moves from Btrfs to Ext4 + OverlayFS, Phoronix, January 18, 2015, by Michael Larabel
• CoreOS, etcd and fleet source code on GitHub