Zen

Source string Source string

172/10000 · 172

The string is read only.

English Actions
Configuration changes
When writing Butane configs, note the following changes:
`coreos-metadata` is now https://coreos.github.io/afterburn/[Afterburn]. The prefix of the metadata variable names has changed from `COREOS_` to `AFTERBURN_`, and the following platform names have changed:
`EC2` is now `AWS`
`GCE` is now `GCP`
For more info, see the https://coreos.github.io/afterburn/usage/attributes/[Afterburn documentation].
By default, FCOS does not allow password logins via SSH. We recommend xref:authentication.adoc#using-an-ssh-key[configuring SSH keys] instead. If needed, you can xref:authentication.adoc#enabling-ssh-password-authentication[enable SSH password authentication].
Because `usermod` is not yet fully-functional on FCOS, there is a `docker` group in the `/etc/group` file. This is a stop-gap measure to facilitate a smooth transition to FCOS. The team is working on a more functional `usermod`, at which time the `docker` group will no longer be included by default. See the https://github.com/coreos/fedora-coreos-tracker/issues/2[docker group issue].
There is no way to create directories below the `/` directory. Changes are restricted to `/etc` and `/var`. Refer to the documentation for the `storage` node of the Butane config for details about writing directories and files to FCOS.
Butane configs no longer have a separate section for network configuration. Use the Butane `files` section to write a https://developer.gnome.org/NetworkManager/stable/nm-settings-keyfile.html[NetworkManager key file] instead.
Operator notes
FCOS provides https://fedoramagazine.org/fedora-coreos-out-of-preview/[best-effort stability], and may occasionally include regressions or breaking changes for some use cases or workloads.
CL had three release channels: `alpha`, `beta`, and `stable`. The FCOS production https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#release-streams[release streams] are `next`, `testing`, and `stable`, with somewhat different semantics.
In general, SELinux confinement should work the same as in Fedora.
To deploy an Ignition config as part of a PXE image (a "custom OEM" in CL terminology), follow the https://coreos.com/os/docs/latest/booting-with-pxe.html#adding-a-custom-oem[same process] as in CL, but place the `config.ign` file in the root of the archive.
In CL, metrics/telemetry data was collected by the update mechanism. In FCOS, nodes are counted (without unique identifiers) via the xref:counting.adoc[Count Me] mechanism.
Cloud CLI clients are not included in FCOS. There is an initiative to create a "tools" container to run on FCOS.
When opening an existing file in a sticky directory, the behavior differs from CL. See https://github.com/systemd/systemd/commit/2732587540035227fe59e4b64b60127352611b35[the relevant systemd commit].
CL left Simultaneous Multi-Threading (SMT) enabled but advised users to turn it off if their systems were vulnerable to certain issues such as https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html[L1TF] or https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html[MDS]. By default, FCOS https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#automatically-disable-smt-when-needed-to-address-vulnerabilities[automatically disables SMT] for vulnerable systems.
In general, `docker` uses the default configuration from Fedora, which is different under many aspects. Notably the logging driver is set to `journald` and live-restore is enabled.
Implementation notes
The default filesystem on CL was `ext4`. On FCOS, the default is `xfs`.
While CL used systemd socket activation for `sshd`, FCOS starts `sshd` at startup by default.
CL had an "OEM partition" at `/usr/share/oem` with a user-customizable GRUB config and some additional tools, but FCOS does not have this.

Loading…

User avatar None

String updated in the repository
In CL, metrics/telemetry data was collected by the update mechanism. In FCOS, nodes are counted (without unique identifiers) via the xref:counting.adoc[Count Me] mechanism.
In CL, metrics/telemetry data was collected by the update mechanism. In FCOS, nodes are counted (without unique identifiers) via the xref:counting.adoc[Count Me] mechanism.
2 years ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Consecutive duplicated words: Portuguese (Brazil), Portuguese (Brazil)

Reset

Glossary

English English
No related strings found in the glossary.

10728385 String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
./pages/migrate-cl.adoc:53
String age
2 years ago
Last updated
a year ago
Source string age
2 years ago
Translation file
pot/master/pages/migrate-cl.pot, string 35