Skip to content

Review abstracts and headings in Managing hosts#4712

Open
aneta-petrova wants to merge 25 commits intotheforeman:masterfrom
aneta-petrova:cqa-managing-hosts
Open

Review abstracts and headings in Managing hosts#4712
aneta-petrova wants to merge 25 commits intotheforeman:masterfrom
aneta-petrova:cqa-managing-hosts

Conversation

@aneta-petrova
Copy link
Copy Markdown
Member

@aneta-petrova aneta-petrova commented Mar 13, 2026

What changes are you introducing?

  • Reviewing abstracts and headings in Managing Hosts to ensure they conform with the requirements from CQA (content quality assessment)

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

This is a downstream requirement

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

Contributor 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.18/Katello 4.20 (Satellite 6.19)
  • Foreman 3.17/Katello 4.19
  • Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6 and 7.7)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
  • We do not accept PRs for Foreman older than 3.12.

@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Mar 13, 2026
@aneta-petrova aneta-petrova removed Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Mar 13, 2026
@aneta-petrova aneta-petrova force-pushed the cqa-managing-hosts branch 3 times, most recently from 1ea9528 to 63ea89f Compare March 16, 2026 15:44
@aneta-petrova aneta-petrova changed the title Review abstracts Review abstracts and headings Mar 16, 2026
@aneta-petrova aneta-petrova marked this pull request as ready for review March 16, 2026 20:05
@maximiliankolb maximiliankolb self-requested a review March 17, 2026 06:48
Copy link
Copy Markdown
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

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

28/121

Copy link
Copy Markdown
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

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

70/121

Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
@aneta-petrova aneta-petrova changed the title Review abstracts and headings Review abstracts and headings in Managing hosts Mar 18, 2026
Copy link
Copy Markdown
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

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

121/121

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would appreciate tech ACK for this change.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Hi @jeremylenz and/or @nofaralfasi, can you please review this change to an abstract? Does it summarize why a user would be interested in applying host groups?

[role="_abstract"]
You can import all the available Ansible Playbooks to {Project} from collections installed on {SmartProxy}.
You can import all available Ansible Playbooks to {Project} from collections installed on {SmartProxy}.
{Project} creates a job template from each playbook so you can run them on hosts via remote execution without writing templates manually.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
{Project} creates a job template from each playbook so you can run them on hosts via remote execution without writing templates manually.
{Project} creates a job template from each playbook so you can run them on hosts through remote execution without writing templates manually.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actually, there's a REX job template that does exactly this: take input and run it; the input is an Ansible playbook.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

But the new line in the abstract is correct, isn't it? It seems to summarize the contents of the module so it looks correct to me.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I don't think so. I ran the following steps on Foreman 3.16/Katello 4.18 to try to reproduce this:

  1. Sync Ansible collection

    url: https://galaxy.ansible.com/
    requirements:

    ---
    collections:
    - name: nextcloud.admin
      version: 2.3.1
  2. Check all job templates for any org/loc under hosts > templates > job templates

  3. Check via monitor > jobs > check all "Ansible *" categories.

Based on that line, I would have expected a job template under Ansible Playbooks but there's none.

-> {Project} creates a job template from each playbook looks wrong to me.

more thoughts:

-> content > content types > Ansible collections seems to provide some read-only information but they did not help me much. It's unclear what that's for:

image

-> https://docs.theforeman.org/nightly/Managing_Content/index-katello.html#Managing_Ansible_Content_content-management lacks information on why to do this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Agree that "creates a job template from each playbook" doesn't sound correct. I'm sure Adam will have more to say.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Huh, looking at the code we actually seem to have something like that, but only accessible through api (and it doesn't use katello's ansible-collection syncing). Considering noone seems to know its there and whether and how it works, maybe we shouldn't document it?

There is one other flow that can "import playbooks" - when you import roles it can also sort of pick up playbooks as well, but they will appear as ansible roles (not job templates) and sadly will break things when (relevant community thread) .

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I can de-emphasize summarizing the contents of the module and instead focus on why this is relevant to users.

@adamruzicka Can you please review the new version of the abstract?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I am unsure about this. Would appreciate a tech ACK.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@adamruzicka Can you please review this abstract?

aneta-petrova and others added 3 commits March 19, 2026 10:36
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Copy link
Copy Markdown
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

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

Looks good so far; three more minor suggestion & one open thread remain.

119/120.

Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
@aneta-petrova
Copy link
Copy Markdown
Member Author

A couple of clarifying questions, one very polite pushback on the whole via/through issue :) (https://github.com/theforeman/foreman-documentation/pull/4712/changes#r2960387106). I still need to find someone to tech review the updates where @maximiliankolb asked for an additional tech check.

@maximiliankolb
Copy link
Copy Markdown
Contributor

one very polite pushback on the whole via/through issue

I am OK either way!

[role="_abstract"]
You can import all the available Ansible Playbooks to {Project} from collections installed on {SmartProxy}.
You can import all available Ansible Playbooks to {Project} from collections installed on {SmartProxy}.
{Project} creates a job template from each playbook so you can run them on hosts via remote execution without writing templates manually.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Agree that "creates a job template from each playbook" doesn't sound correct. I'm sure Adam will have more to say.

aneta-petrova and others added 6 commits March 27, 2026 22:03
Update the reasoning for choosing transport modes to describe actual decision criteria (scalability vs. port restrictions) rather than circular descriptions of what each mode does.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Fix host collection and errata terminology

Change "adding errata/content to host collections" to "applying errata" to accurately reflect that errata application is a remote execution operation, not adding content to collections.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Rename a module

Rename a module

Fix wording for installing packages on hosts in a host collection
Co-authored-by: Jeremy Lenz <jlenz@redhat.com>
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Co-authored-by: Jeremy Lenz <jlenz@redhat.com>
Copy link
Copy Markdown
Contributor

@nofaralfasi nofaralfasi left a comment

Choose a reason for hiding this comment

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

I’d like to review this PR after addressing Jeremy’s comments (not all of them have been resolved yet). In addition, I think it would be best to get a review from someone on the Rocket team, especially for the network documentation part - perhaps Leos or Shim.

I also added a few small comments.

@aneta-petrova
Copy link
Copy Markdown
Member Author

I believe I've addressed all concerns. There are some pending requests for re-review. Thanks, everyone, for your inputs so far!

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.

5 participants