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

Upstreamize VM subscriptions guide #3528

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

apinnick
Copy link
Contributor

@apinnick apinnick commented Dec 15, 2024

What changes are you introducing?

Upstreamizing VM subscriptions guide.

  • Updated doc title because user story is configuring virt-who for VM subscriptions, not configuring the subscriptions themselves.
  • Updated UI procedure for creating virt-who configs for Nutanix and CNV
  • Removed troubleshooting sections that duplicated troubleshooting content in Subscription Central doc, Getting started with RHEL system registration, retaining only Satellite/Foreman procedures.

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

https://issues.redhat.com/browse/SAT-27789

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
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only)
  • 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.

Copy link

github-actions bot commented Dec 15, 2024

The PR preview for f55acc9 is available at theforeman-foreman-documentation-preview-pr-3528.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch 7 times, most recently from 4eba9e6 to 0cdf087 Compare December 16, 2024 15:11
@apinnick apinnick marked this pull request as draft December 17, 2024 11:54
@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch 7 times, most recently from f0529d6 to 7905ee8 Compare December 18, 2024 15:42
@apinnick apinnick marked this pull request as ready for review December 18, 2024 15:46
@apinnick apinnick changed the title Upstreamize VM subscriptions guide (WIP) Upstreamize VM subscriptions guide Dec 18, 2024
@apinnick apinnick added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective labels Dec 18, 2024
@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch from 7905ee8 to 2c90793 Compare December 18, 2024 16:04
@apinnick
Copy link
Contributor Author

@chris1984 Please review.

@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch from 37f3007 to f16c7f4 Compare January 5, 2025 13:08
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.

Generally looks good! I've taken a look at a couple of top-level formalities so far. Will give it another round afterwards.

guides/common/modules/snip_technology-preview.adoc Outdated Show resolved Hide resolved
guides/common/attributes-titles.adoc Show resolved Hide resolved
guides/upstream_filename_to_satellite_link.json Outdated Show resolved Hide resolved
@pr-processor pr-processor bot added the Waiting on contributor Requires an action from the author label Jan 7, 2025
@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch from f16c7f4 to f0321f9 Compare January 9, 2025 12:13
@pr-processor pr-processor bot added Needs re-review and removed Waiting on contributor Requires an action from the author Needs re-review labels Jan 9, 2025
@apinnick apinnick force-pushed the upstreamize-vm-subscription-guide branch from f0321f9 to f55acc9 Compare January 9, 2025 14:18
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.

I tried to go more in depth with my review. This is what stood out.

@@ -0,0 +1,15 @@
<title>Configuring virt-who for virtual machine subscriptions</title>
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
<title>Configuring virt-who for virtual machine subscriptions</title>
<title>{ConfiguringVMSubscriptionsDocTitle}</title>

You can use the DocTitle attribute here as well.

<title>Configuring virt-who for virtual machine subscriptions</title>
<productname>{ProjectName}</productname>
<productnumber>{ProjectVersion}</productnumber>
<subtitle>Tracking the usage of your host-based subscriptions</subtitle>
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
<subtitle>Tracking the usage of your host-based subscriptions</subtitle>
<subtitle>Track the usage of your host-based subscriptions</subtitle>

We use this verb form in other subtitles.

Comment on lines +11 to +25
. On the {EL} server, install the {ProjectServer} CA certificate:
+
[options="nowrap" subs="+quotes"]
----
$ rpm -ivh http://__{server.example.com}__/pub/katello-ca-consumer-latest.noarch.rpm
----

. Register the {EL} server to {ProjectServer}:
+
[options="nowrap" subs="+quotes"]
----
$ subscription-manager register \
--org=_organization_label_ \
--auto-attach
----
Copy link
Contributor

@Lennonka Lennonka Jan 9, 2025

Choose a reason for hiding this comment

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

These two steps look like an outdated way to register a host because the Katello CA consumer package is deprecated. Perhaps we should link to global registration instead?

[IMPORTANT]
====
[subs="attributes+"]
{FeatureName} is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
Copy link
Contributor

Choose a reason for hiding this comment

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

One sentence per line.

guides/common/attributes-titles.adoc Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we make the example values a bit more descriptive and use a bit more formatting to distinguish values that are to be replaced by the user? For example:

hypervisor_id=_hypervisor.example.com_
server=_server.example.com_

Btw, what server is server.example.com? If it's supposed to be the Foreman/Satellite server, you can use the {foreman-example-com} attribute.

:virt-who-vm-subs:
:ProductName: {ProjectServer}

= {ConfiguringVMSubscriptionsDocTitle}
Copy link
Contributor

Choose a reason for hiding this comment

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

For some reason, the build displays "Configuring virtual machine subscriptions" as the title. I don't understand why.

@@ -2,6 +2,7 @@
"build/Administering_Project/index-satellite.html": "administering_red_hat_satellite",
"build/Configuring_Load_Balancer/index-satellite.html": "configuring_capsules_with_a_load_balancer",
"build/Configuring_User_Authentication/index-satellite.html": "configuring_authentication_for_red_hat_satellite_users",
"build/Configuring_Virtual_Machine_Subscriptions/index-satellite.html": "configuring_virt-who_for_virtual_machine_subscriptions",
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
"build/Configuring_Virtual_Machine_Subscriptions/index-satellite.html": "configuring_virt-who_for_virtual_machine_subscriptions",
"build/Configuring_Virt-Who-VM-Subscriptions/index-satellite.html": "configuring_virt-who_for_virtual_machine_subscriptions",

This path has to match the folder name after the doc- prefix.

Copy link
Contributor

Choose a reason for hiding this comment

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

I can't see this file included anywhere.

Copy link
Contributor

Choose a reason for hiding this comment

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

I can't see this file included anywhere.

Copy link
Member

@chris1984 chris1984 left a comment

Choose a reason for hiding this comment

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

Left a few comments around ovirt, debugging and hammer. Overall looks pretty good

After you create a virt-who configuration, you download a script from the {ProjectWebUI} to deploy the configuration.

The script installs virt-who and creates the local and global virt-who configuration files.

Copy link
Member

Choose a reason for hiding this comment

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

Should we mention you can deploy the script on the {ProjectWebUI} with hammer as well?
screenshot-ip-10-0-167-73 rhos-01 prod psi rdu2 redhat com-2025 01 09-11_12_13

* VMware vSphere
* {EL} Virtualization (KVM)
* {OpenStack}
* {oVirt}
Copy link
Member

Choose a reason for hiding this comment

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

Downstream we don't support {oVirt} anymore and the project upstream has been abandoned. We remove support for it here theforeman/foreman_virt_who_configure#136

* Microsoft Hyper-V:
** You have enabled remote management on each hypervisor.
** You have created a virt-who user with read-only access and a non-expiring password on each hypervisor.
* {oVirt}, {EL} Virtualization (KVM), {OpenStack}:
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}

* *Hypervisor Type*: Select one of the following types:
** *VMware vSphere / vCenter (esx)*.
** *Microsoft Hyper-V (hyperv)*.
** *libvirt*: For {oVirt}, {EL} Virtualization (KVM), or {OpenStack}.
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}

====

<4> Specify the hypervisor type:
* {EL} Virtualization (KVM), {oVirt}, or {OpenStack}: `libvirt`.
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}

.Prerequisites

* You have registered the hypervisor to {ProjectServer}.
* {oVirt}: You have updated {oVirt} to the latest version so that the minimum virt-who version is available.
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}

[id="deploying-a-virt-who-configuration-on-a-hypervisor_{context}"]
= Deploying a virt-who configuration on a hypervisor or a {SmartProxyServer}

For {oVirt}, {EL} Virtualization (KVM), and {OpenStack}, you deploy the configuration on the hypervisor specified in the file.
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}


* You have registered the hypervisor to {ProjectServer}.
* {oVirt}: You have updated {oVirt} to the latest version so that the minimum virt-who version is available.
virt-who is available by default on {oVirt}, but you cannot update virt-who by using the `rhel-7-server-rhvh-4-rpms` repository.
Copy link
Member

Choose a reason for hiding this comment

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

Drop {oVirt}

# virt-who -op >/tmp/virt-who.json
# systemctl start virt-who
# cat /tmp/virt-who.json | json_reformat | grep "guestId" | sort | uniq -c | wc -l
----
Copy link
Member

Choose a reason for hiding this comment

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

Looks really good, sent you a link on Slack to some of the debugging steps support uses, that maybe we can include here as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants