Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add concept for Package and Image Mode Hosts #3611

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

bangelic
Copy link
Contributor

What changes are you introducing?

Adding a concept for understanding package
mode and image mode hosts.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

This is in reference to https://issues.redhat.com/browse/SAT-28164.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • We do not accept PRs for Foreman older than 3.7.

@bangelic
Copy link
Contributor Author

@ianballou This is the concept for Package and Image Mode hosts. The procedure for https://issues.redhat.com/browse/SAT-28185 will be in another PR.

Copy link

github-actions bot commented Jan 23, 2025

@ianballou ianballou changed the title Add concept for Package and Imahe Mode Hosts Add concept for Package and Image Mode Hosts Jan 24, 2025
Copy link
Contributor

@ianballou ianballou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small comments only here!

@bangelic bangelic force-pushed the bangelic-SAT-28164-Add-section-to-managing-hosts-guide-about-image-mode-hosts branch from f9ca843 to ded44c2 Compare January 29, 2025 21:46
Copy link
Contributor

@Lennonka Lennonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The purpose of this concept module us unclear to me. It currently describes the user interface, which we don't do.

Try to think harder about what the user needs to learn before they get to manage image mode hosts:

  • What is the "image mode"?
  • Why is it relevant?
  • What are the advantages of the image mode vs. the package mode?
  • The keyword "bootc" should probably appear here.

Also, I'm not sure if this assembly is the right place. Should it go to a standalone chapter maybe? Have you considered that? Why yes? Why not?

Please, try again.

A new card appears on the Details tab for registered hosts, displaying the additional 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this should be a prerequisite in the procedure? (I'm not sure because it isn't clear to me why that's needed.)

@pr-processor pr-processor bot added the Waiting on contributor Requires an action from the author label Jan 30, 2025
@Lennonka Lennonka marked this pull request as draft January 31, 2025 06:13
@bangelic bangelic force-pushed the bangelic-SAT-28164-Add-section-to-managing-hosts-guide-about-image-mode-hosts branch from ded44c2 to b1901a6 Compare January 31, 2025 19:39
@pr-processor pr-processor bot added Needs re-review and removed Waiting on contributor Requires an action from the author labels Jan 31, 2025
Copy link
Contributor

@Lennonka Lennonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Brian, that's better!


The distinction between package mode and image mode provides greater flexibility in managing hosts and streamlines operations for image-based deployments.

{Project} enables registration, monitoring, and update support for image mode hosts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{Project} enables registration, monitoring, and update support for image mode hosts.
In {Project}, you can register, monitor, and update image mode hosts.

{Project} identifies an image mode host as any system that reports a container image from its bootc status through `subscription-manager`.
It classifies all other hosts as package mode hosts.

Image mode simplifies enterprise operations by enabling development, operations, and solution providers to use the same container-native tools and techniques to manage both applications and the underlying OS.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Image mode simplifies enterprise operations by enabling development, operations, and solution providers to use the same container-native tools and techniques to manage both applications and the underlying OS.
Image mode simplifies enterprise operations by enabling development, operations, and solution providers to use the same container-native tools and techniques to manage both applications and the underlying operating system.

I'm surprised that Vale hasn't reported this. 🤔

@@ -0,0 +1,25 @@
[id="package-mode-and-image-mode-hosts_{context}"]
= Package mode and image mode hosts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
= Package mode and image mode hosts
= Image mode hosts

I'd simplify it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this...

[id="package-mode-and-image-mode-hosts_{context}"]
= Package mode and image mode hosts

You can operate hosts in two modes: package mode and image mode.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can operate hosts in two modes: package mode and image mode.
You can operate hosts in two modes: package mode and image mode.

I'd drop this sentence because this can be inferred from the overall context.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this.

Comment on lines +6 to +7
{Project} identifies an image mode host as any system that reports a container image from its bootc status through `subscription-manager`.
It classifies all other hosts as package mode hosts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would lead with this - move it to the top.


Image mode simplifies enterprise operations by enabling development, operations, and solution providers to use the same container-native tools and techniques to manage both applications and the underlying OS.

The distinction between package mode and image mode provides greater flexibility in managing hosts and streamlines operations for image-based deployments.
Copy link
Contributor

@Lennonka Lennonka Feb 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 11 doesn't seem useful to me. Looks like fluff.


{Project} enables registration, monitoring, and update support for image mode hosts.
Register image mode hosts like any other host, view their `bootc` statuses in a centralized location, and trigger updates remotely using remote execution.
For more information on image mode concepts, refer to the https://www.redhat.com/en/blog/image-mode-red-hat-enterprise-linux-quick-start-guide[RHEL Image Mode quick start guide].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move to "Additional resources" at the bottom.

Comment on lines +17 to +25
.Image mode hosts
Image mode hosts include additional 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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't these things described in the web UI?

@@ -55,6 +55,8 @@ include::common/assembly_host-status.adoc[leveloffset=+1]

include::common/assembly_managing-packages.adoc[leveloffset=+1]

include::common/assembly_package-mode-and-image-mode-hosts.adoc[leveloffset=+1]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's quite important and I'd include it in common/assembly_overview-of-hosts.adoc


You can operate hosts in two modes: package mode and image mode.

{Project} identifies an image mode host as any system that reports a container image from its bootc status through `subscription-manager`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{Project} identifies an image mode host as any system that reports a container image from its bootc status through `subscription-manager`.
{Project} identifies an image mode host as any system that reports a container image from its bootc status through Subscription Manager.

SM is an established term.

@Lennonka
Copy link
Contributor

Lennonka commented Feb 3, 2025

I'm still missing one more bit of information: What can the user do on hosts in Package mode that they cannot do on hosts in Image mode?

My guess: manage packages (as described in the chapter Managing packages)

@Lennonka
Copy link
Contributor

Lennonka commented Feb 3, 2025

Did you know you could display a column in the New UI of All Hosts page with a mode indicator?
It looks like something the user might be interested in and the column is disabled by default. Perhaps we should give them a hint that they can do that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants