-
Notifications
You must be signed in to change notification settings - Fork 95
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
base: master
Are you sure you want to change the base?
Upstreamize VM subscriptions guide #3528
Conversation
4eba9e6
to
0cdf087
Compare
f0529d6
to
7905ee8
Compare
7905ee8
to
2c90793
Compare
@chris1984 Please review. |
guides/common/modules/con_virtual-machine-subscriptions-overview.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/con_virtual-machine-subscriptions-overview.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_removing-a-virt-who-configuration.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_editing-a-virt-who-configuration.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_editing-a-virt-who-configuration.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/proc_editing-a-virt-who-configuration.adoc
Outdated
Show resolved
Hide resolved
37f3007
to
f16c7f4
Compare
There was a problem hiding this 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.
f16c7f4
to
f0321f9
Compare
f0321f9
to
f55acc9
Compare
There was a problem hiding this 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> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<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> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<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.
. 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 | ||
---- |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One sentence per line.
There was a problem hiding this comment.
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} |
There was a problem hiding this comment.
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", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this 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. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* VMware vSphere | ||
* {EL} Virtualization (KVM) | ||
* {OpenStack} | ||
* {oVirt} |
There was a problem hiding this comment.
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}: |
There was a problem hiding this comment.
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}. |
There was a problem hiding this comment.
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`. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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 | ||
---- |
There was a problem hiding this comment.
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?
What changes are you introducing?
Upstreamizing VM subscriptions guide.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
https://issues.redhat.com/browse/SAT-27789
Checklists
Please cherry-pick my commits into: