07-24-2019, 02:05 PM
Introducing Fedora CoreOS
<div><p>The Fedora CoreOS team is excited to <a href="https://getfedora.org/coreos/">announce the first preview release</a> of Fedora CoreOS, a new Fedora edition built specifically for running containerized workloads securely and at scale. It’s the successor to both <a href="https://www.projectatomic.io/">Fedora Atomic Host</a> and <a href="https://coreos.com/os/docs/latest/">CoreOS Container Linux</a>. Fedora CoreOS combines the provisioning tools, automatic update model, and philosophy of Container Linux with the packaging technology, OCI support, and SELinux security of Atomic Host.</p>
<p>Read on for more details about this exciting new release.</p>
<p> <span id="more-28945"></span> </p>
<h2>Why Fedora CoreOS?</h2>
<p>Containers allow workloads to be reproducibly deployed to production and automatically scaled to meet demand. The isolation provided by a container means that the host OS can be small. It only needs a Linux kernel, systemd, a container runtime, and a few additional services such as an SSH server. </p>
<p>While containers can be run on a full-sized server OS, an operating system built specifically for containers can provide functionality that a general purpose OS cannot. Since the required software is minimal and uniform, the entire OS can be deployed as a unit with little customization. And, since containers are deployed across multiple nodes for redundancy, the OS can update itself automatically and then reboot without interrupting workloads.</p>
<p>Fedora CoreOS is built to be the secure and reliable host for your compute clusters. It’s designed specifically for running containerized workloads without regular maintenance, automatically updating itself with the latest OS improvements, bug fixes, and security updates. It provisions itself with Ignition, runs containers with Podman and Moby, and updates itself atomically and automatically with rpm-ostree.</p>
<h2>Provisioning immutable infrastructure</h2>
<p>Whether you run in the cloud, virtualized, or on bare metal, a Fedora CoreOS machine always begins from the same place: a <a href="https://getfedora.org/coreos/download/">generic OS image</a>. Then, during the first boot, Fedora CoreOS uses <em>Ignition</em> to provision the system. Ignition reads an <em>Ignition config</em> from cloud user data or a remote URL, and uses it to create disk partitions and file systems, users, files and systemd units.</p>
<p>To provision a machine:</p>
<ol>
<li>Write a <a href="https://github.com/coreos/fcct/blob/master/docs/configuration-v1_0.md">Fedora CoreOS Config</a> (FCC), a YAML document that specifies the desired configuration of a machine. FCCs support all Ignition functionality, and also provide additional syntax (“sugar”
that makes it easier to specify typical configuration changes.</li>
<li>Use the <a href="https://github.com/coreos/fcct/releases">Fedora CoreOS Config Transpiler</a> to <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_generating_ignition_configs">validate your FCC and convert it to an Ignition config</a>.</li>
<li>Launch a Fedora CoreOS machine and <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_launching_fedora_coreos">pass it the Ignition config</a>. If the machine boots successfully, provisioning has completed without errors.</li>
</ol>
<p>Fedora CoreOS is designed to be managed as <em>immutable infrastructure</em>. After a machine is provisioned, you should not modify <em>/etc</em> or otherwise reconfigure the machine. Instead, modify the FCC and use it to provision a replacement machine. </p>
<p>This is similar to how you’d manage a container: container images are not updated in place, but rebuilt from scratch and redeployed. This approach makes it easy to scale out when load increases. Simply use the same Ignition config to launch additional machines.</p>
<h2>Automatic updates</h2>
<p>By default, Fedora CoreOS automatically downloads new OS releases, atomically installs them, and reboots into them. Releases roll out gradually over time. We can even stop a rollout if we discover a problem in a new release. Upgrades between Fedora releases are treated as any other update, and are automatically applied without user intervention.</p>
<p>The Linux ecosystem evolves quickly, and software updates can bring undesired behavior changes. However, for automatic updates to be trustworthy, they cannot break existing machines. To avoid this, Fedora CoreOS takes a two-pronged approach. First, we automatically test each change to the OS. However, automatic testing can’t catch all regressions, so Fedora CoreOS also ships multiple independent <em>release streams</em>:</p>
<ul>
<li>The <em>testing</em> stream is a regular snapshot of the current Fedora release, plus updates.</li>
<li>After a <em>testing</em> release has been available for two weeks, it is sent to the <em>stable</em> stream. Bugs discovered in <em>testing</em> will be fixed before a release is sent to <em>stable</em>.</li>
<li>The <em>next</em> stream is a regular snapshot of the upcoming Fedora release, allowing additional time for testing larger changes.</li>
</ul>
<p>All three streams receive security updates and critical bugfixes, and are intended to be safe for production use. Most machines should run the <em>stable</em> stream, since that receives the most testing. However, users should run a few percent of their nodes on the <em>next</em> and <em>testing</em> streams, and report problems to the <a href="https://github.com/coreos/fedora-coreos-tracker/issues">issue tracker</a>. This helps ensure that bugs that only affect certain workloads or certain hardware are fixed before they reach <em>stable</em>.</p>
<h2>Telemetry</h2>
<p>To help direct our development efforts, Fedora CoreOS performs some telemetry by default. A service called <em><a href="https://github.com/coreos/fedora-coreos-pinger/">fedora-coreos-pinger</a></em> periodically collects non-identifying information about the machine, such as the OS version, cloud platform, and instance type, and report it to servers controlled by the Fedora project.</p>
<p>No unique identifiers are reported or collected, and the data is only used in aggregate to answer questions about how Fedora CoreOS is being used. We prominently document that this collection is occurring and how to disable it. We also tell you how to help the project by reporting additional detail, including information that might identify the machine.</p>
<h2>Current status of Fedora CoreOS</h2>
<p>Fedora CoreOS is still under active development, and some planned functionality is not available in the first preview release:</p>
<ul>
<li>Only the <em>testing</em> stream currently exists; the <em>next</em> and <em>stable</em> streams are not yet available.</li>
<li>Several cloud and virtualization platforms are not yet available. Only x86_64 is currently supported.</li>
<li>Booting a live Fedora CoreOS system via network (PXE) or CD is not yet supported.</li>
<li>We are actively discussing plans for closer integration with Kubernetes distributions, including OKD.</li>
<li>Fedora CoreOS Config Transpiler will gain more sugar over time.</li>
<li>Telemetry is not yet active.</li>
<li>Documentation is still under development.</li>
</ul>
<p><strong>While Fedora CoreOS is intended for production use, preview releases should <em>not</em> be used in production. Fedora CoreOS may change in incompatible ways during the preview period. There is no guarantee that a preview release will successfully update to a later preview release, or to a stable release.</strong></p>
<h2>The future</h2>
<p>We expect the preview period to continue for about six months. At the end of the preview, we will declare Fedora CoreOS stable and encourage its use in production.</p>
<p>CoreOS Container Linux will be maintained until about six months after Fedora CoreOS is declared stable. We’ll announce the exact timing later this year. During the preview period, we’ll publish tools and documentation to help Container Linux users migrate to Fedora CoreOS.</p>
<p><a href="https://fedoramagazine.org/announcing-fedora-coreos/https://fedoramagazine.org/announcing-fedora-coreos/">Fedora Atomic Host will be maintained</a> until the end of life of Fedora 29, expected in late November. Before then, Fedora Atomic Host users should migrate to Fedora CoreOS.</p>
<h2>Getting involved in Fedora CoreOS</h2>
<p>To try out the new release, head over to the <a href="https://getfedora.org/coreos/download/">download page</a> to get OS images or cloud image IDs. Then use the <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/">quick start guide</a> to get a machine running quickly. Finally, get involved! You can report bugs and missing features to the <a href="https://github.com/coreos/fedora-coreos-tracker/issues">issue tracker</a>. You can also discuss Fedora CoreOS in <a href="https://discussion.fedoraproject.org/c/server/coreos">Fedora Discourse</a>, the <a href="https://lists.fedoraproject.org/archives/list/[email protected]/">development mailing list</a>, or in #fedora-coreos on Freenode.</p>
<p>Welcome to Fedora CoreOS, and let us know what you think!</p>
</div>
<div><p>The Fedora CoreOS team is excited to <a href="https://getfedora.org/coreos/">announce the first preview release</a> of Fedora CoreOS, a new Fedora edition built specifically for running containerized workloads securely and at scale. It’s the successor to both <a href="https://www.projectatomic.io/">Fedora Atomic Host</a> and <a href="https://coreos.com/os/docs/latest/">CoreOS Container Linux</a>. Fedora CoreOS combines the provisioning tools, automatic update model, and philosophy of Container Linux with the packaging technology, OCI support, and SELinux security of Atomic Host.</p>
<p>Read on for more details about this exciting new release.</p>
<p> <span id="more-28945"></span> </p>
<h2>Why Fedora CoreOS?</h2>
<p>Containers allow workloads to be reproducibly deployed to production and automatically scaled to meet demand. The isolation provided by a container means that the host OS can be small. It only needs a Linux kernel, systemd, a container runtime, and a few additional services such as an SSH server. </p>
<p>While containers can be run on a full-sized server OS, an operating system built specifically for containers can provide functionality that a general purpose OS cannot. Since the required software is minimal and uniform, the entire OS can be deployed as a unit with little customization. And, since containers are deployed across multiple nodes for redundancy, the OS can update itself automatically and then reboot without interrupting workloads.</p>
<p>Fedora CoreOS is built to be the secure and reliable host for your compute clusters. It’s designed specifically for running containerized workloads without regular maintenance, automatically updating itself with the latest OS improvements, bug fixes, and security updates. It provisions itself with Ignition, runs containers with Podman and Moby, and updates itself atomically and automatically with rpm-ostree.</p>
<h2>Provisioning immutable infrastructure</h2>
<p>Whether you run in the cloud, virtualized, or on bare metal, a Fedora CoreOS machine always begins from the same place: a <a href="https://getfedora.org/coreos/download/">generic OS image</a>. Then, during the first boot, Fedora CoreOS uses <em>Ignition</em> to provision the system. Ignition reads an <em>Ignition config</em> from cloud user data or a remote URL, and uses it to create disk partitions and file systems, users, files and systemd units.</p>
<p>To provision a machine:</p>
<ol>
<li>Write a <a href="https://github.com/coreos/fcct/blob/master/docs/configuration-v1_0.md">Fedora CoreOS Config</a> (FCC), a YAML document that specifies the desired configuration of a machine. FCCs support all Ignition functionality, and also provide additional syntax (“sugar”
that makes it easier to specify typical configuration changes.</li><li>Use the <a href="https://github.com/coreos/fcct/releases">Fedora CoreOS Config Transpiler</a> to <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_generating_ignition_configs">validate your FCC and convert it to an Ignition config</a>.</li>
<li>Launch a Fedora CoreOS machine and <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_launching_fedora_coreos">pass it the Ignition config</a>. If the machine boots successfully, provisioning has completed without errors.</li>
</ol>
<p>Fedora CoreOS is designed to be managed as <em>immutable infrastructure</em>. After a machine is provisioned, you should not modify <em>/etc</em> or otherwise reconfigure the machine. Instead, modify the FCC and use it to provision a replacement machine. </p>
<p>This is similar to how you’d manage a container: container images are not updated in place, but rebuilt from scratch and redeployed. This approach makes it easy to scale out when load increases. Simply use the same Ignition config to launch additional machines.</p>
<h2>Automatic updates</h2>
<p>By default, Fedora CoreOS automatically downloads new OS releases, atomically installs them, and reboots into them. Releases roll out gradually over time. We can even stop a rollout if we discover a problem in a new release. Upgrades between Fedora releases are treated as any other update, and are automatically applied without user intervention.</p>
<p>The Linux ecosystem evolves quickly, and software updates can bring undesired behavior changes. However, for automatic updates to be trustworthy, they cannot break existing machines. To avoid this, Fedora CoreOS takes a two-pronged approach. First, we automatically test each change to the OS. However, automatic testing can’t catch all regressions, so Fedora CoreOS also ships multiple independent <em>release streams</em>:</p>
<ul>
<li>The <em>testing</em> stream is a regular snapshot of the current Fedora release, plus updates.</li>
<li>After a <em>testing</em> release has been available for two weeks, it is sent to the <em>stable</em> stream. Bugs discovered in <em>testing</em> will be fixed before a release is sent to <em>stable</em>.</li>
<li>The <em>next</em> stream is a regular snapshot of the upcoming Fedora release, allowing additional time for testing larger changes.</li>
</ul>
<p>All three streams receive security updates and critical bugfixes, and are intended to be safe for production use. Most machines should run the <em>stable</em> stream, since that receives the most testing. However, users should run a few percent of their nodes on the <em>next</em> and <em>testing</em> streams, and report problems to the <a href="https://github.com/coreos/fedora-coreos-tracker/issues">issue tracker</a>. This helps ensure that bugs that only affect certain workloads or certain hardware are fixed before they reach <em>stable</em>.</p>
<h2>Telemetry</h2>
<p>To help direct our development efforts, Fedora CoreOS performs some telemetry by default. A service called <em><a href="https://github.com/coreos/fedora-coreos-pinger/">fedora-coreos-pinger</a></em> periodically collects non-identifying information about the machine, such as the OS version, cloud platform, and instance type, and report it to servers controlled by the Fedora project.</p>
<p>No unique identifiers are reported or collected, and the data is only used in aggregate to answer questions about how Fedora CoreOS is being used. We prominently document that this collection is occurring and how to disable it. We also tell you how to help the project by reporting additional detail, including information that might identify the machine.</p>
<h2>Current status of Fedora CoreOS</h2>
<p>Fedora CoreOS is still under active development, and some planned functionality is not available in the first preview release:</p>
<ul>
<li>Only the <em>testing</em> stream currently exists; the <em>next</em> and <em>stable</em> streams are not yet available.</li>
<li>Several cloud and virtualization platforms are not yet available. Only x86_64 is currently supported.</li>
<li>Booting a live Fedora CoreOS system via network (PXE) or CD is not yet supported.</li>
<li>We are actively discussing plans for closer integration with Kubernetes distributions, including OKD.</li>
<li>Fedora CoreOS Config Transpiler will gain more sugar over time.</li>
<li>Telemetry is not yet active.</li>
<li>Documentation is still under development.</li>
</ul>
<p><strong>While Fedora CoreOS is intended for production use, preview releases should <em>not</em> be used in production. Fedora CoreOS may change in incompatible ways during the preview period. There is no guarantee that a preview release will successfully update to a later preview release, or to a stable release.</strong></p>
<h2>The future</h2>
<p>We expect the preview period to continue for about six months. At the end of the preview, we will declare Fedora CoreOS stable and encourage its use in production.</p>
<p>CoreOS Container Linux will be maintained until about six months after Fedora CoreOS is declared stable. We’ll announce the exact timing later this year. During the preview period, we’ll publish tools and documentation to help Container Linux users migrate to Fedora CoreOS.</p>
<p><a href="https://fedoramagazine.org/announcing-fedora-coreos/https://fedoramagazine.org/announcing-fedora-coreos/">Fedora Atomic Host will be maintained</a> until the end of life of Fedora 29, expected in late November. Before then, Fedora Atomic Host users should migrate to Fedora CoreOS.</p>
<h2>Getting involved in Fedora CoreOS</h2>
<p>To try out the new release, head over to the <a href="https://getfedora.org/coreos/download/">download page</a> to get OS images or cloud image IDs. Then use the <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/">quick start guide</a> to get a machine running quickly. Finally, get involved! You can report bugs and missing features to the <a href="https://github.com/coreos/fedora-coreos-tracker/issues">issue tracker</a>. You can also discuss Fedora CoreOS in <a href="https://discussion.fedoraproject.org/c/server/coreos">Fedora Discourse</a>, the <a href="https://lists.fedoraproject.org/archives/list/[email protected]/">development mailing list</a>, or in #fedora-coreos on Freenode.</p>
<p>Welcome to Fedora CoreOS, and let us know what you think!</p>
</div>