Skip to content

Commit

Permalink
deploy: f17af8b
Browse files Browse the repository at this point in the history
  • Loading branch information
@Lennonka
Lennonka committed Jan 6, 2025
1 parent 1c176e2 commit 5f45706
Show file tree
Hide file tree
Showing 5 changed files with 255 additions and 60 deletions.
63 changes: 51 additions & 12 deletions nightly/Provisioning_Hosts/index-foreman-deb.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,12 @@ <h1>Provisioning hosts</h1>
<li><a href="#facts-and-nic-filtering_provisioning">3.1. Facts and NIC filtering</a></li>
<li><a href="#optimizing-performance-by-removing-nics-from-database_provisioning">3.2. Optimizing performance by removing NICs from database</a></li>
<li><a href="#Network_Resources_provisioning">3.3. Network resources</a></li>
<li><a href="#DHCP_Options_provisioning">3.4. Foreman and DHCP options</a></li>
<li><a href="#foreman-and-dhcp-configuration">3.4. Foreman and DHCP configuration</a>
<ul class="sectlevel3">
<li><a href="#options-in-managed-dhcpv4">3.4.1. Options in managed DHCPv4</a></li>
<li><a href="#options-in-unmanaged-dhcpv6">3.4.2. Options in unmanaged DHCPv6</a></li>
</ul>
</li>
<li><a href="#Troubleshooting_DHCP_Problems_provisioning">3.5. Troubleshooting DHCP problems in Foreman</a></li>
<li><a href="#Prerequisites_for_Image_Based_Provisioning_provisioning">3.6. Prerequisites for image-based provisioning</a></li>
<li><a href="#Configuring_Network_Services_provisioning">3.7. Configuring network services</a>
Expand Down Expand Up @@ -2723,17 +2728,22 @@ <h3 id="Network_Resources_provisioning"><a class="anchor" href="#Network_Resourc
</div>
</div>
<div class="sect2">
<h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisioning"></a>3.4. Foreman and DHCP options</h3>
<h3 id="foreman-and-dhcp-configuration"><a class="anchor" href="#foreman-and-dhcp-configuration"></a>3.4. Foreman and DHCP configuration</h3>
<div class="paragraph">
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.
Foreman also sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.</p>
</div>
<div class="sect3">
<h4 id="options-in-managed-dhcpv4"><a class="anchor" href="#options-in-managed-dhcpv4"></a>3.4.1. Options in managed DHCPv4</h4>
<div class="paragraph">
<div class="title">The next-server option</div>
<p>When Foreman manages the DHCP service and can update the DHCP configuration, Foreman sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>next-server</code></dt>
<dd>
<p>The <code>next-server</code> option provides the IP address of the TFTP server to boot from.
This option is not set by default and must be set for each TFTP Smart&#160;Proxy.
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> option to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
</div>
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> argument to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"># foreman-installer --foreman-proxy-tftp-servername <em>1.2.3.4</em></pre>
Expand Down Expand Up @@ -2766,13 +2776,13 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
<div class="paragraph">
<p>If you encounter these problems, check the DNS setup on both Foreman and Smart&#160;Proxy, specifically the PTR record resolution.</p>
</div>
<div class="paragraph">
<div class="title">The filename option</div>
</dd>
<dt class="hdlist1"><code>filename</code></dt>
<dd>
<p>The <code>filename</code> option contains the full path to the file that downloads and executes during provisioning.
The PXE loader that you select for the host or host group defines which <code>filename</code> option to use.
When the PXE loader is set to <code>none</code>, Foreman does not populate the <code>filename</code> option into the DHCP record.
Depending on the PXE loader option, the <code>filename</code> changes as follows:</p>
</div>
<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 33.3333%;">
Expand Down Expand Up @@ -2819,6 +2829,36 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="options-in-unmanaged-dhcpv6"><a class="anchor" href="#options-in-unmanaged-dhcpv6"></a>3.4.2. Options in unmanaged DHCPv6</h4>
<div class="paragraph">
<p>To provision hosts over TFTP in an IPv6-only network, configure the DHCP server to respond with the <code>bootfile-url</code> DHCP option.
Foreman cannot manage the DHCPv6 service, therefore, you have to configure your DHCP server manually.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>bootfile-url</code></dt>
<dd>
<p>The URL value of this option has to point to a file on TFTP Smart&#160;Proxy that is a first-stage boot loader, such as <code>pxelinux.0</code>.
Example configuration:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"> "option-data": [
{
"name": "bootfile-url",
"data": "tftp://2001:db8:1::1/pxelinux.0"
}
],</pre>
</div>
</div>
</dd>
</dl>
</div>
</div>
</div>
<div class="sect2">
<h3 id="Troubleshooting_DHCP_Problems_provisioning"><a class="anchor" href="#Troubleshooting_DHCP_Problems_provisioning"></a>3.5. Troubleshooting DHCP problems in Foreman</h3>
Expand Down Expand Up @@ -4011,8 +4051,7 @@ <h3 id="Creating_Hosts_with_PXE_less_Provisioning_provisioning"><a class="anchor
<div class="sect2">
<h3 id="Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"><a class="anchor" href="#Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"></a>4.5. Creating hosts with UEFI HTTP boot provisioning</h3>
<div class="paragraph">
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.
This is the only method with which you can provision hosts in IPv6 network.</p>
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.</p>
</div>
<div class="paragraph">
<p>To use the CLI instead of the Foreman web UI, see the <a href="#cli-creating-hosts-with-uefi-http-boot-provisioning_provisioning">CLI procedure</a>.</p>
Expand Down
63 changes: 51 additions & 12 deletions nightly/Provisioning_Hosts/index-foreman-el.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,12 @@ <h1>Provisioning hosts</h1>
<li><a href="#facts-and-nic-filtering_provisioning">3.1. Facts and NIC filtering</a></li>
<li><a href="#optimizing-performance-by-removing-nics-from-database_provisioning">3.2. Optimizing performance by removing NICs from database</a></li>
<li><a href="#Network_Resources_provisioning">3.3. Network resources</a></li>
<li><a href="#DHCP_Options_provisioning">3.4. Foreman and DHCP options</a></li>
<li><a href="#foreman-and-dhcp-configuration">3.4. Foreman and DHCP configuration</a>
<ul class="sectlevel3">
<li><a href="#options-in-managed-dhcpv4">3.4.1. Options in managed DHCPv4</a></li>
<li><a href="#options-in-unmanaged-dhcpv6">3.4.2. Options in unmanaged DHCPv6</a></li>
</ul>
</li>
<li><a href="#Troubleshooting_DHCP_Problems_provisioning">3.5. Troubleshooting DHCP problems in Foreman</a></li>
<li><a href="#Prerequisites_for_Image_Based_Provisioning_provisioning">3.6. Prerequisites for image-based provisioning</a></li>
<li><a href="#Configuring_Network_Services_provisioning">3.7. Configuring network services</a>
Expand Down Expand Up @@ -2734,17 +2739,22 @@ <h3 id="Network_Resources_provisioning"><a class="anchor" href="#Network_Resourc
</div>
</div>
<div class="sect2">
<h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisioning"></a>3.4. Foreman and DHCP options</h3>
<h3 id="foreman-and-dhcp-configuration"><a class="anchor" href="#foreman-and-dhcp-configuration"></a>3.4. Foreman and DHCP configuration</h3>
<div class="paragraph">
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.
Foreman also sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.</p>
</div>
<div class="sect3">
<h4 id="options-in-managed-dhcpv4"><a class="anchor" href="#options-in-managed-dhcpv4"></a>3.4.1. Options in managed DHCPv4</h4>
<div class="paragraph">
<div class="title">The next-server option</div>
<p>When Foreman manages the DHCP service and can update the DHCP configuration, Foreman sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>next-server</code></dt>
<dd>
<p>The <code>next-server</code> option provides the IP address of the TFTP server to boot from.
This option is not set by default and must be set for each TFTP Smart&#160;Proxy.
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> option to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
</div>
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> argument to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"># foreman-installer --foreman-proxy-tftp-servername <em>1.2.3.4</em></pre>
Expand Down Expand Up @@ -2777,13 +2787,13 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
<div class="paragraph">
<p>If you encounter these problems, check the DNS setup on both Foreman and Smart&#160;Proxy, specifically the PTR record resolution.</p>
</div>
<div class="paragraph">
<div class="title">The filename option</div>
</dd>
<dt class="hdlist1"><code>filename</code></dt>
<dd>
<p>The <code>filename</code> option contains the full path to the file that downloads and executes during provisioning.
The PXE loader that you select for the host or host group defines which <code>filename</code> option to use.
When the PXE loader is set to <code>none</code>, Foreman does not populate the <code>filename</code> option into the DHCP record.
Depending on the PXE loader option, the <code>filename</code> changes as follows:</p>
</div>
<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 33.3333%;">
Expand Down Expand Up @@ -2830,6 +2840,36 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="options-in-unmanaged-dhcpv6"><a class="anchor" href="#options-in-unmanaged-dhcpv6"></a>3.4.2. Options in unmanaged DHCPv6</h4>
<div class="paragraph">
<p>To provision hosts over TFTP in an IPv6-only network, configure the DHCP server to respond with the <code>bootfile-url</code> DHCP option.
Foreman cannot manage the DHCPv6 service, therefore, you have to configure your DHCP server manually.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>bootfile-url</code></dt>
<dd>
<p>The URL value of this option has to point to a file on TFTP Smart&#160;Proxy that is a first-stage boot loader, such as <code>pxelinux.0</code>.
Example configuration:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"> "option-data": [
{
"name": "bootfile-url",
"data": "tftp://2001:db8:1::1/pxelinux.0"
}
],</pre>
</div>
</div>
</dd>
</dl>
</div>
</div>
</div>
<div class="sect2">
<h3 id="Troubleshooting_DHCP_Problems_provisioning"><a class="anchor" href="#Troubleshooting_DHCP_Problems_provisioning"></a>3.5. Troubleshooting DHCP problems in Foreman</h3>
Expand Down Expand Up @@ -4028,8 +4068,7 @@ <h3 id="Creating_Hosts_with_PXE_less_Provisioning_provisioning"><a class="anchor
<div class="sect2">
<h3 id="Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"><a class="anchor" href="#Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"></a>4.5. Creating hosts with UEFI HTTP boot provisioning</h3>
<div class="paragraph">
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.
This is the only method with which you can provision hosts in IPv6 network.</p>
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.</p>
</div>
<div class="paragraph">
<p>To use the CLI instead of the Foreman web UI, see the <a href="#cli-creating-hosts-with-uefi-http-boot-provisioning_provisioning">CLI procedure</a>.</p>
Expand Down
63 changes: 51 additions & 12 deletions nightly/Provisioning_Hosts/index-katello.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,12 @@ <h1>Provisioning hosts</h1>
<li><a href="#facts-and-nic-filtering_provisioning">3.1. Facts and NIC filtering</a></li>
<li><a href="#optimizing-performance-by-removing-nics-from-database_provisioning">3.2. Optimizing performance by removing NICs from database</a></li>
<li><a href="#Network_Resources_provisioning">3.3. Network resources</a></li>
<li><a href="#DHCP_Options_provisioning">3.4. Foreman and DHCP options</a></li>
<li><a href="#foreman-and-dhcp-configuration">3.4. Foreman and DHCP configuration</a>
<ul class="sectlevel3">
<li><a href="#options-in-managed-dhcpv4">3.4.1. Options in managed DHCPv4</a></li>
<li><a href="#options-in-unmanaged-dhcpv6">3.4.2. Options in unmanaged DHCPv6</a></li>
</ul>
</li>
<li><a href="#Troubleshooting_DHCP_Problems_provisioning">3.5. Troubleshooting DHCP problems in Foreman</a></li>
<li><a href="#Prerequisites_for_Image_Based_Provisioning_provisioning">3.6. Prerequisites for image-based provisioning</a></li>
<li><a href="#Configuring_Network_Services_provisioning">3.7. Configuring network services</a>
Expand Down Expand Up @@ -2736,17 +2741,22 @@ <h3 id="Network_Resources_provisioning"><a class="anchor" href="#Network_Resourc
</div>
</div>
<div class="sect2">
<h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisioning"></a>3.4. Foreman and DHCP options</h3>
<h3 id="foreman-and-dhcp-configuration"><a class="anchor" href="#foreman-and-dhcp-configuration"></a>3.4. Foreman and DHCP configuration</h3>
<div class="paragraph">
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.
Foreman also sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
<p>Foreman manages DHCP reservations through a DHCP Smart&#160;Proxy.</p>
</div>
<div class="sect3">
<h4 id="options-in-managed-dhcpv4"><a class="anchor" href="#options-in-managed-dhcpv4"></a>3.4.1. Options in managed DHCPv4</h4>
<div class="paragraph">
<div class="title">The next-server option</div>
<p>When Foreman manages the DHCP service and can update the DHCP configuration, Foreman sets the <code>next-server</code> and <code>filename</code> DHCP options.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>next-server</code></dt>
<dd>
<p>The <code>next-server</code> option provides the IP address of the TFTP server to boot from.
This option is not set by default and must be set for each TFTP Smart&#160;Proxy.
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> option to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
</div>
You can use the <code>foreman-installer</code> command with the <code>--foreman-proxy-tftp-servername</code> argument to set the TFTP server in the <code>/etc/foreman-proxy/settings.d/tftp.yml</code> file:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"># foreman-installer --foreman-proxy-tftp-servername <em>1.2.3.4</em></pre>
Expand Down Expand Up @@ -2779,13 +2789,13 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
<div class="paragraph">
<p>If you encounter these problems, check the DNS setup on both Foreman and Smart&#160;Proxy, specifically the PTR record resolution.</p>
</div>
<div class="paragraph">
<div class="title">The filename option</div>
</dd>
<dt class="hdlist1"><code>filename</code></dt>
<dd>
<p>The <code>filename</code> option contains the full path to the file that downloads and executes during provisioning.
The PXE loader that you select for the host or host group defines which <code>filename</code> option to use.
When the PXE loader is set to <code>none</code>, Foreman does not populate the <code>filename</code> option into the DHCP record.
Depending on the PXE loader option, the <code>filename</code> changes as follows:</p>
</div>
<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 33.3333%;">
Expand Down Expand Up @@ -2832,6 +2842,36 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="options-in-unmanaged-dhcpv6"><a class="anchor" href="#options-in-unmanaged-dhcpv6"></a>3.4.2. Options in unmanaged DHCPv6</h4>
<div class="paragraph">
<p>To provision hosts over TFTP in an IPv6-only network, configure the DHCP server to respond with the <code>bootfile-url</code> DHCP option.
Foreman cannot manage the DHCPv6 service, therefore, you have to configure your DHCP server manually.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>bootfile-url</code></dt>
<dd>
<p>The URL value of this option has to point to a file on TFTP Smart&#160;Proxy that is a first-stage boot loader, such as <code>pxelinux.0</code>.
Example configuration:</p>
<div class="listingblock">
<div class="content">
<pre class="nowrap"> "option-data": [
{
"name": "bootfile-url",
"data": "tftp://2001:db8:1::1/pxelinux.0"
}
],</pre>
</div>
</div>
</dd>
</dl>
</div>
</div>
</div>
<div class="sect2">
<h3 id="Troubleshooting_DHCP_Problems_provisioning"><a class="anchor" href="#Troubleshooting_DHCP_Problems_provisioning"></a>3.5. Troubleshooting DHCP problems in Foreman</h3>
Expand Down Expand Up @@ -4047,8 +4087,7 @@ <h3 id="Creating_Hosts_with_PXE_less_Provisioning_provisioning"><a class="anchor
<div class="sect2">
<h3 id="Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"><a class="anchor" href="#Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning"></a>4.5. Creating hosts with UEFI HTTP boot provisioning</h3>
<div class="paragraph">
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.
This is the only method with which you can provision hosts in IPv6 network.</p>
<p>You can provision hosts from Foreman using the UEFI HTTP Boot.</p>
</div>
<div class="paragraph">
<p>To use the CLI instead of the Foreman web UI, see the <a href="#cli-creating-hosts-with-uefi-http-boot-provisioning_provisioning">CLI procedure</a>.</p>
Expand Down
Loading

0 comments on commit 5f45706

Please sign in to comment.