Content deleted Content added
No edit summary |
m Improved Readability |
||
Line 39:
}}
'''Container Linux''' (formerly '''CoreOS Linux''') is a discontinued [[Open-source software|open-source]] lightweight [[operating system]] based on the [[Linux kernel]] and designed for providing infrastructure
| url = https://coreos.com/blog/tectonic-self-driving.html#coreos-linux-is-now-container-linux
| title = CoreOS Linux is now Container Linux
Line 94:
| author = Brian Harrington | publisher = Rackspace
| website = youtube.com
}}</ref>{{rp|7:02}} CoreOS was developed primarily by Alex Polvi, Brandon Philips, and Michael Marineau,<ref name="wired-201308" /> with its major features available as a [[stable release]].<ref>{{cite web
| url = https://coreos.com/blog/stable-release/
| title = CoreOS Stable Release
Line 161:
| date = February 4, 2015 | access-date = June 22, 2015
| author = Josh Berkus | publisher = [[LWN.net]]
}}</ref> CoreOS provides rkt as an implementation of the so-called ''app container'' (appc) specification that describes the required properties of the ''application container image'' (ACI). CoreOS created appc and ACI as an independent committee-steered set of specifications<ref name="lwn-644089">{{Cite web
| url = https://lwn.net/Articles/644089/
| title = CoreOS Fest and the world of containers, part 1
Line 204:
}}</ref>
Container Linux uses [[ebuild]] scripts from Gentoo Linux for automated [[Compiler|compilation]] of its system components,<ref name="coreos-sdk-building" /><ref name="gentoo-based" /> and uses [[systemd]] as its primary [[init]] system, with tight integration between systemd and various Container Linux's internal mechanisms.<ref name="linux.com-737364" /><ref>{{Cite web
| url = https://coreos.com/using-coreos/systemd/
| title = CoreOS documentation: Using systemd with CoreOS
Line 242:
}}</ref>
To ensure that only a certain part of the [[Computer cluster|cluster]] reboots at once when the operating system updates are applied, preserving
| url = http://www.centurylinklabs.com/interviews/simple-introduction-to-coreos-with-ceo-alex-polvi-and-cto-brandon-philips/
| title = Simple Introduction to CoreOS with CEO Alex Polvi and CTO Brandon Philips
Line 285:
| archive-url = https://web.archive.org/web/20090506062328/http://omaha.googlecode.com/svn/wiki/OmahaOverview.html
| archive-date = May 6, 2009
}}</ref> Additionally, CoreOS provides ''CoreUpdate'' as a web-based [[Dashboard (management information systems)|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 Container Linux versions, stopping and restarting updates, and reviewing recorded update logs. CoreUpdate also provides
| url = https://godoc.org/github.com/coreos/go-omaha/omaha
| title = Package omaha
Line 327:
}}</ref> etcd is also used in [[Kubernetes]] software.
Container Linux also provides the {{Mono|fleet}} cluster manager, which controls Container Linux's separate systemd instances at the cluster level. As of 2017, "fleet" is no longer actively developed and is deprecated in favor of [[Kubernetes]].<ref>{{cite web|last1=Wood|first1=Josh|title=Container orchestration: Moving from fleet to Kubernetes|url=https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html|website=coreos..com|publisher=CoreOS}}</ref> By using {{Mono|fleetd}}, Container Linux creates a distributed [[init|init system]] that ties together separate systemd instances and a cluster-wide {{Mono|etcd}} deployment;<ref name="lwn-617452" /> internally, {{Mono|fleetd}} daemon communicates with local {{Mono|systemd}} instances over [[D-Bus]], and with the {{Mono|etcd}} deployment through its exposed API. Using {{Mono|fleetd}} allows the deployment of single or multiple [[Software container|containers]] cluster-wide, with more advanced options including [[Redundancy (engineering)|redundancy]], [[failover]], deployment to specific cluster members, dependencies between containers, and grouped deployment of containers. A command-line utility called {{Mono|fleetctl}} is used to configure and monitor this distributed init system;<ref>{{Cite web
| url = https://www.digitalocean.com/community/tutorials/how-to-use-fleet-and-fleetctl-to-manage-your-coreos-cluster
| title = How To Use Fleet and Fleetctl to Manage your CoreOS Cluster
Line 369:
== {{Anchor|TECTONIC|FLANNEL}}Deployment ==
When running on dedicated hardware, Container Linux can be either permanently installed
| url = https://coreos.com/docs/running-coreos/bare-metal/installing-to-disk/
| title = CoreOS documentation: Installing CoreOS to disk
Line 411:
| date = April 6, 2015 | access-date = April 29, 2015
| author = Ben Kepes | magazine = [[Forbes]]
}}</ref> Furthermore, CoreOS provides ''Flannel'' as a component, implementing an [[overlay network]] required primarily for the integration with Kubernetes.<ref name="lwn-644089" /><ref>{{Cite web
| url = https://coreos.com/blog/introducing-rudder/
| title = Introducing flannel: An etcd-backed overlay network for containers
Line 428:
=={{Anchor|Derivatives}}Derivatives ==
Following its acquisition of CoreOS, Inc.<ref>{{Cite web|url=https://www.cnbc.com/2018/01/30/red-hat-buys-coreos-for-250-mililon.html|title=Red Hat pays $250 million for CoreOS, a start-up that sells Google-developed technology|last=Rosoff|first=Matt|date=2018-01-30|website=CNBC|language=en|access-date=2019-06-06}}</ref> in January 2018, Red Hat announced<ref>{{Cite web|url=https://coreos.com/blog/fedora-coreos-red-hat-coreos-and-future-container-linux|title=Fedora CoreOS, Red Hat CoreOS, and the future of Container Linux {{!}} CoreOS|website=coreos.com|access-date=2019-06-06}}</ref> that it would be merging CoreOS Container Linux with Red Hat's Project Atomic
On March 6, 2018, Kinvolk GmbH announced<ref>{{Cite web|url=https://kinvolk.io/blog/2018/03/announcing-the-flatcar-linux-project/|title=Announcing the Flatcar Linux project {{!}} Kinvolk|website=kinvolk.io|date=March 6, 2018 |access-date=2019-06-06}}</ref> [https://www.flatcar-linux.org/ Flatcar Container Linux], a derivative of CoreOS Container Linux. This tracks the upstream CoreOS alpha
== Reception ==
| |||