Appendix A. Terminology and commands
Learn more about the rpm ostree
terminology and commands.
A.1. OSTree and rpm-ostree
terminology
Following are some helpful terms that are used in context to OSTree and rpm-ostree
images.
Term | Definition |
---|---|
| A tool used for managing Linux-based operating system versions. The OSTree tree view is similar to Git and is based on similar concepts. |
| A hybrid image or system package that hosts operating system updates. |
| A release or image version of the operating system. RHEL image builder generates an OSTree commit for RHEL for Edge images. You can use these images to install or update RHEL on Edge servers. |
|
Represents a branch in OSTree. Refs always resolve to the latest commit. For example, |
| SHA-256 for a specific commit. |
| The http or https endpoint that hosts the OSTree content. This is analogous to the baseurl for a yum repository. |
| Updates to OSTree images are always delta updates. In case of RHEL for Edge images, the TCP overhead can be higher than expected due to the updates to number of files. To avoid TCP overhead, you can generate static-delta between specific commits, and send the update in a single connection. This optimization helps large deployments with constrained connectivity. |
A.2. OSTree commands
The following table provides a few OSTree commands that you can use when installing or managing OSTree images.
ostree pull |
|
ostree summary |
|
View refs |
|
View commits in repo |
|
Inspect a commit |
|
List remotes of a repo |
|
Resolve a REV |
|
Create static-delta |
|
Sign an |
|
A.3. rpm-ostree
commands
The following table provides a few rpm-ostree
commands that you can use when installing or managing OSTree images.
Commands | Description |
---|---|
| This command lists the packages existing in the <REV> commit into the repository. |
|
OSTree manages an ordered list of boot loader entries, called |
|
This command gives information about the current deployment in use. Lists the names and |
| Use this command to see which packages are within the commit or commits. You must specify at least one commit, but more than one or a range of commits also work. |
| Use this command to show how the packages are different between the trees in two revs (revisions). If no revs are provided, the booted commit is compared to the pending commit. If only a single rev is provided, the booted commit is compared to that rev. |
| This command downloads the latest version of the current tree, and deploys it, setting up the current tree as the default for the next boot. This has no effect on your running filesystem tree. You must reboot for any changes to take effect. |
Additional resources
-
The
rpm-ostree
man page.
A.4. FDO automatic onboarding terminology
Learn more about the FDO terminology.
Commands | Description |
---|---|
FDO | FIDO Device Onboarding. |
Device | Any hardware, device, or computer. |
Owner | The final owner of the device - a company or an IT department. |
Manufacturer | The device manufacturer. |
Manufacturer server | Creates the device credentials for the device. |
Manufacturer client | Informs the location of the manufacturing server. |
Ownership Voucher (OV) | Record of ownership of an individual device. Contains the following information:
* Owner (
* Rendezvous Server - FIDO server (
* Device (at least one combination) ( |
Device Credential (DC) | Key credential and rendezvous stored in the device at manufacture. |
Keys | Keys to configure the manufacturing server * key_path * cert_path * key_type * mfg_string_type: device serial number * allowed_key_storage_types: Filesystem and Trusted Platform Module (TPM) that protects the data used to authenticate the device you are using. |
Rendezvous server | Link to a server used by the device and later on, used on the process to find out who is the owner of the device |
Additional resources
A.5. FDO automatic onboarding technologies
Following are the technologies used in context to FDO automatic onboarding.
Technology | Definition |
---|---|
UEFI | Unified Extensible Firmware Interface. |
RHEL | Red Hat® Enterprise Linux® operating system |
| Background image-based upgrades. |
Greenboot |
|
Osbuild | Pipeline-based build system for operating system artifacts. |
Container | A Linux® container is a set of 1 or more processes that are isolated from the rest of the system. |
Coreos-installer | Assists installation of RHEL images, boots systems with UEFI. |
FIDO FDO | Specification protocol to provision configuration and onboarding devices. |