-
Notifications
You must be signed in to change notification settings - Fork 97
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add concept for Package and Imahe Mode Hosts
- Loading branch information
Showing
3 changed files
with
34 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31 changes: 31 additions & 0 deletions
31
guides/common/modules/con_understanding-package-mode-and-image-mode-hosts.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
[id="understanding_package_mode_and_image_mode_hosts_{context}"] | ||
= Understanding Package mode and Image mode hosts | ||
|
||
In the latest update, hosts can now operate in two modes: package mode and image mode. | ||
|
||
.Image mode hosts | ||
Image mode hosts include eight new fields that reflect their boot status. | ||
These fields track the container images used in various scenarios: | ||
|
||
* *Booted Image & Digest*: Indicates the container image the host is currently using. | ||
* *Staged Image & Digest*: Indicates the container image the host uses after the next reboot. | ||
* *Available Image & Digest*: Represents the container image cached by running `Bootc upgrade --check`. | ||
* *Rollback Image & Digest*: Represents the container image the host reverts to after the next reboot if `Bootc rollback` is applied. | ||
|
||
.All host listing page updates | ||
* *New Column for Host Types*: The host listing page includes a column with icons that indicate the host type. | ||
** Clicking an icon displays the image path and digest. | ||
** Note that the image path can be used directly with podman or docker to pull the image from a registry. | ||
Check failure on line 18 in guides/common/modules/con_understanding-package-mode-and-image-mode-hosts.adoc GitHub Actions / linter
|
||
* *Search Enhancements*: | ||
** Use `image_mode=true` or `image_mode=false` to filter hosts by type. | ||
** Unregistered systems are assumed to be in package mode. | ||
** Search using eight new fields: | ||
`Bootc_booted_image`, `Bootc_booted_digest`, `Bootc_staged_image`, `Bootc_staged_digest`, `Bootc_available_image`, `Bootc_available_digest`, `Bootc_rollback_image`, `Bootc_rollback_digest`. | ||
|
||
.Host Details Page Enhancements | ||
A new card appears on the Details tab for registered hosts, displaying the eight fields from `Bootc`. | ||
|
||
.Important Notes | ||
* *Pull-Mode Remote Execution*: For pull-mode remote execution users, related packages must be included in the image mode host's container image. | ||
|
||
This distinction between package mode and image mode provides greater flexibility in managing host systems and streamlines operations for image-based deployments. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters