Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/provisioning_hosts/using_infoblox_as_dhcp_and_dns_providers_provisioning
Section Number and Name: Adding a new section
Describe the issue:
current section is vague and allows for ambiguity
Suggestions for improvement:
The request is to add a new section "How to use Infoblox DNS/DHCP", and this is because it is a bit counterintuitive.
Additional information:
What is the nature and description of the request?
To improve the documentation and remove ambiguity.
I am suggesting adding a new section to https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/provisioning_hosts/using_infoblox_as_dhcp_and_dns_providers_provisioning
Why does the customer need this? (List the business requirements here)
Because the current section is vague and allows for ambiguity.
The request is to add a new section "How to use Infoblox DNS/DHCP", and this is because it is a bit counterintuitive.
How would the customer like to achieve this? (List the functional requirements here)
The customer would like the Red Hat documentation team to review this section and consider adding a new section to clarify infoblox usage.
If you are creating a subnet or a host, what should the IPAM setting be set to, to use the Infoblox? External IPAM would seem like the right answer, but the right answer is DHCP. The reason for this, is the smart proxy for the Infoblox is internal to foreman is is a part of the existing DNS and DHCP smart proxy (so is MS). Perhaps it's documented elsewhere, but I have not seen it and it is not mentioned in the KB https://access.redhat.com/solutions/3081191.
I've seen this discussed in the upstream at https://community.theforeman.org/t/what-is-the-future-of-infoblox-smartproxy-plugins/27774/10
Please consider adding a new section with an example or two, to explain usage to the administrator.
For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
A new satellite administrator can read the section and understand what is going on and what they need to do.
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 7 release would be nice
Hello,
Thank you very much for raising this BZ with the suggestion for improvement and detailed information.
As the doc update that you request is non-trivial, the docs team will need some time to scope it.
Updates about next steps or any progress will be shared in this ticket.
Thank you!
Comment 3Zuzana Lena Ansorgova
2024-01-23 21:28:22 UTC