World Library  
Flag as Inappropriate
Email this Article


Article Id: WHEBN0041927028
Reproduction Date:

Title: CoreOS  
Author: World Heritage Encyclopedia
Language: English
Subject: Matthew Garrett, L4Linux, Just enough operating system, Virtualization, LynxSecure
Publisher: World Heritage Encyclopedia


CoreOS logo
OS family Unix-like
Working state In development
Source model Open source
Initial release October 3, 2013 (2013-10-03)[1]
Latest release 808.0.0[2] / September 17, 2015 (2015-09-17)
Latest preview 800.0.0[3] / September 9, 2015 (2015-09-09)
Marketing target Servers and clusters
Platforms x86-64[4]
Kernel type Monolithic (Linux kernel)
License Apache License 2.0[5][6]
Official website .comcoreos

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.[7][8][9][10]

CoreOS shares the foundations with Chrome OS and Chromium OS, by the means of using their common software development kit (SDK) as a base while adding new functionality and customizing it to support hardware used in servers.[9][11]:7:02 As of January 2015, CoreOS is actively developed, primarily by Alex Polvi, Brandon Philips and Michael Marineau,[8] with its major features available as a stable release.[12][13][14]


CoreOS provides no package manager as a way for distributing payload applications, requiring instead all applications to run inside their containers. Serving as a single control host, a CoreOS instance uses the underlying operating-system-level virtualization features of the Linux kernel to create and configure multiple containers that perform as isolated Linux systems. That way, resource partitioning between containers 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.[7][10][15]

Initially, CoreOS exclusively used Docker as a component providing an additional layer of abstraction and interface[16] to the operating-system-level virtualization features of the Linux kernel, as well as providing a standardized format for containers that allows applications to run in different environments.[7][15] In December 2014, CoreOS released and started to support Rocket (abbreviated as rkt) as an alternative to Docker, providing through it another standardized format of the application container images, related definition of the container runtime environment, and a protocol for discovering and retrieving container images.[17][18][19][20] CoreOS provides Rocket as an implementation of the so-called app container (appc) specification that describes required properties of the application container image (ACI); CoreOS initiated appc and ACI as an independent committee-steered set of specifications,[21][22] aiming at having them become part of the vendor- and operating-system-independent Open Container Project containerization standard, which was announced in June 2015.[23][24]

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

Updates distribution

CoreOS achieves additional security and reliability of its operating system updates by employing 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 that becomes active upon a 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.[7][10][26] 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.[27][28][29]

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.[30] 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.[31][32] locksmith is written in the Go language and distributed under the terms of the Apache License 2.0.[33]

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.[4][34][35] 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.[26][36][37]

Cluster infrastructure

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

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.[4][27] Since the key–value data stored within etcd is automatically distributed and replicated with automated master election and consensus establishment using the Raft algorithm, 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.[20][39] 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 REST-based 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.[7][10][40][41][42]

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;[39] 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. A command-line utility called fleetctl is used to configure and monitor this distributed init system;[43] 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.[44][45][46][47][48]

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.[6][49]


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),[50] or booted remotely over a network using Preboot Execution Environment (PXE) in general, or iPXE as one of its implementations.[51][52] CoreOS also supports deployments on various hardware virtualization platforms, including Amazon EC2, DigitalOcean, Google Compute Engine, Microsoft Azure, OpenStack, QEMU/KVM, Vagrant and VMware.[10][53][54][55]

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.[21][56][57] Furthermore, CoreOS provides Flannel as a component implementing an overlay network required primarily for the integration with Kubernetes.[21][58][59]

As of February 2015, CoreOS supports only the x86-64 architecture.[4]

See also


  1. ^
  2. ^
  3. ^
  4. ^ a b c d
  5. ^
  6. ^ a b
  7. ^ a b c d e f
  8. ^ a b
  9. ^ a b
  10. ^ a b c d e
  11. ^
  12. ^
  13. ^
  14. ^
  15. ^ a b
  16. ^
  17. ^
  18. ^
  19. ^
  20. ^ a b
  21. ^ a b c
  22. ^
  23. ^
  24. ^
  25. ^
  26. ^ a b
  27. ^ a b
  28. ^
  29. ^
  30. ^
  31. ^
  32. ^
  33. ^
  34. ^
  35. ^
  36. ^
  37. ^
  38. ^
  39. ^ a b
  40. ^
  41. ^
  42. ^
  43. ^
  44. ^
  45. ^
  46. ^
  47. ^
  48. ^
  49. ^
  50. ^
  51. ^
  52. ^
  53. ^
  54. ^
  55. ^
  56. ^
  57. ^
  58. ^
  59. ^

External links

  • Official CoreOS and Tectonic websites, and source code repositories: CoreOS on GitHub, etcd on GitHub, fleet on GitHub, and rkt on GitHub
  • 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
  • Understanding CoreOS distributed architecture, March 4, 2015, a talk to Alex Polvi by Aaron Delp and Brian Gracely
  • CoreOS fleet architecture, August 26, 2014, by Brian Waldon et al.
  • Running CoreOS on Google Compute Engine, May 23, 2014
  • CoreOS moves from Btrfs to Ext4 + OverlayFS, Phoronix, January 18, 2015, by Michael Larabel
  • Containers and persistent data,, May 28, 2015, by Josh Berkus
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.