Configure host for global registration #3242
Merged
Conversation
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
|
The PR preview for 6e6ef51 is available at theforeman-foreman-documentation-preview-pr-3242.surge.sh The following output files are affected by this PR: |
Lennonka
force-pushed
the
configure-host-for-global-reg
branch
from
539a35f to
08035ed
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Lennonka
force-pushed
the
configure-host-for-global-reg
branch
2 times, most recently
from
5c131b3 to
f43e4fd
Compare
Lennonka
commented
Sep 16, 2024
|
Open to suggestions :) |
Lennonka
commented
Sep 16, 2024
Lennonka
added
Needs tech review
Lennonka
commented
Sep 30, 2024
guides/common/modules/proc_configuring-a-host-for-registration.adoc
Outdated
Show resolved
Hide resolved
|
I have rewritten the configuring procedure because earlier I was referring users to an incorrect certificate file. I have also successfully tested the configuration + secure registration on RHEL 9. ✔️ |
maximiliankolb
added
style review done
Lennonka
added
tech review done
|
I'm setting the |
Lennonka
force-pushed
the
configure-host-for-global-reg
branch
from
7e95b7c to
d88007e
Compare
Lennonka
force-pushed
the
configure-host-for-global-reg
branch
from
d88007e to
6e6ef51
Compare
|
Rebased. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are you introducing?
A host needs to be configured a certain way before it can be registered by using Global Registration and that isn't properly documented at the present time.
We have a Configure a host for registration module, but we don't use it in the Managing Hosts guide currently, which we should. Originally, it covered only the NTP synchronization.
Also, we should provide a prerequisite so that the user can make a secured curl call right away. The CA certificate config is now also included in the pre-registration configuration.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Because it's better to tell the user how the host must be configured for registration beforehand instead of explaining it when it's "too late".
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Depends on #3193
Checklists
Please cherry-pick my commits into: