-
Notifications
You must be signed in to change notification settings - Fork 96
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
Update IPv4/IPv6 installation prerequisites #3545
base: master
Are you sure you want to change the base?
Update IPv4/IPv6 installation prerequisites #3545
Conversation
The PR preview for 5e04042 is available at theforeman-foreman-documentation-preview-pr-3545.surge.sh The following output files are affected by this PR: |
9d74bc6
to
93b2342
Compare
Hi @lhellebr, I'm trying to address the issue with disabling IPv6 in kernel that you discovered (https://issues.redhat.com/browse/SAT-29764). Do you think that cb69625 would work? |
I've added one comment, otherwise looks good |
|
||
* You must deploy an external DHCP IPv6 server as a separate, unmanaged service to bootstrap clients into GRUB2. | ||
GRUB2 configures IPv6 networking by using DHCPv6 or by assigning a static IPv6 address. | ||
This is required because the DHCP server in {RHEL} (ISC DHCP) does not provide an integration API for managing IPv6 records, therefore the {SmartProxy} DHCP plugin that provides DHCP management is limited to IPv4 subnets. |
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.
Preempting customer questions: Infoblox does have an API to manage DHCPv6. Can I use that? The answer is no, so perhaps just reduce it to say we currently can't manage DHCPv6?
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.
No change, because #3541 removes this line.
Part of the feedback resulted in changes that can't be cherry-picked to all versions, which is why I raised a separate PR to address the IPv4 requirements #3553. |
e0c6274
to
81c3947
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.
LGTM style wise
Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. | ||
This limitation only relates to users who plan to use {Project} to provision hosts. |
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.
Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. | |
This limitation only relates to users who plan to use {Project} to provision hosts. |
I think that these lines no longer apply because of #3532 (TFTP ~ PXE). I think we can just remove them.
@ShimShtein Can you please confirm? Or is there another limitation?
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 confirm that I am working on enabling PXE provisioning in IPv6 networking.
As far as limitations go - I don't see anything yet
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.
some mostly optional comments. I prefer to always say "HTTP proxy" to clearly differentiate between Smart Proxies and HTTP proxies.
Co-authored-by: Maximilian Kolb <[email protected]>
Co-authored-by: Maximilian Kolb <[email protected]>
Co-authored-by: Maximilian Kolb <[email protected]>
7d0bcc8
to
5e04042
Compare
I implemented feedback from @maximiliankolb (thank you!) > Tech review is still needed so I'll wait for @ekohl and/or @ShimShtein to review as requested above. |
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.
style-wise LGTM
What changes are you introducing?
* Expanding the existing IPv6 section with information on IPv4 installationsWhy are you introducing these changes? (Explanation, links to references, issues, etc.)
This started with https://issues.redhat.com/browse/SAT-29764 which requests adding the information about IPv4 and it seemed like a good opportunity to implement a few other changes that had been discussed at various times.
EDIT: The IPv4 changes now have their own PR #3553
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Checklists
Please cherry-pick my commits into: