Merge pull request #51568 from rohennes/TELCODOCS-432-support-PXE-with-ZTP

TELCODOCS-432: Adding support for iPXE to ZTP

Author: michaelryanpeter

modules/ztp-deploying-a-site.adoc

@@ -116,7 +116,7 @@ spec:
     nodes:
       - hostName: "example-node1.example.com" <6>
         role: "master"
-        bmcAddress: "idrac-virtualmedia+https://[1111:2222:3333:4444::bbbb:1]/redfish/v1/Systems/System.Embedded.1" <7>
+        bmcAddress: idrac-virtualmedia://<out_of_band_ip>/<system_id>/ <7>
         bmcCredentialsName:
           name: "example-node1-bmh-secret" <8>
         bootMACAddress: "AA:BB:CC:DD:EE:11"
@@ -160,7 +160,7 @@ spec:
 <4> Applies to three-node and standard clusters. The value defines the cluster network sections.
 <5> Applies to three-node and standard clusters. The value defines the cluster network sections.
 <6> Applies to all cluster types. For single node deployments, define one host. For three-node deployments, define three hosts. For standard deployments, define three hosts with `role: master` and two or more hosts defined with `role: worker`.
-<7> Applies to all cluster types. Specifies the BMC address.
+<7> Applies to all cluster types. Specifies the BMC address. ZTP supports iPXE and virtual media booting by using Redfish or IPMI protocols. For more information about BMC addressing, see the _Additional resources_ section.
 <8> Applies to all cluster types. Specifies the BMC credentials.
 <9> Applies to all cluster types. Specifies the network settings for the node.
 
@@ -184,4 +184,4 @@ The `SiteConfig` CR creates the following CRs on the hub cluster:
 * `NMStateConfig` - One per node
 * `ExtraManifestsConfigMap` - Extra manifests. The extra manifests include workload partitioning, mountpoint hiding, sctp enablement, and more. To automatically merge the extra manifests into a single manifest per each `MachineConfigPool` role, which is named as `predefined-extra-manifests-<role>`, set the `.spec.clusters.mergeDefaultMachineConfigs` to `true` in the `SiteConfig.yaml` file.
 * `ManagedCluster`
-* `KlusterletAddonConfig`
+* `KlusterletAddonConfig`

modules/ztp-manually-install-a-single-managed-cluster.adoc

@@ -271,7 +271,7 @@ spec:
   automatedCleaningMode: disabled
   online: true
 ----
-<1> The baseboard management console address of the installation ISO on the target bare-metal host.
+<1> The baseboard management console (BMC) address on the target bare-metal host. ZTP supports iPXE and virtual media booting by using Redfish or IPMI protocols. For more information about BMC addressing, see the _Additional resources_ section.
 <2> The MAC address of the target bare-metal host.
 +
 Optionally, you can add `bmac.agent-install.openshift.io/hostname: <host-name>` as an annotation to set the managed cluster’s hostname. If you don't add the annotation, the hostname will default to either a hostname from the DHCP server or local host.

modules/ztp-ztp-custom-resources.adoc

@@ -29,7 +29,7 @@ Both methods create the CRs shown in the following table. On the cluster site, a
 
 |`BareMetalHost`
 |Contains the connection information for the Baseboard Management Controller (BMC) of the target bare-metal host.
-|Provides access to the BMC in order to load and boot the Discovery image ISO on the target server by using the Redfish protocol.
+|Provides access to the BMC to load and boot the discovery image on the target server by using the Redfish protocol. ZTP supports iPXE and virtual media network booting.
 
 |`InfraEnv`
 |Contains information for pulling {product-title} onto the target bare-metal host.
@@ -49,7 +49,7 @@ Both methods create the CRs shown in the following table. On the cluster site, a
 
 |`Agent`
 |Contains hardware information about the target bare-metal host.
-|Created automatically on the hub when the target machine's Discovery image ISO boots.
+|Created automatically on the hub when the target machine's discovery image boots.
 
 |`ManagedCluster`
 |When a cluster is managed by the hub, it must be imported and known. This Kubernetes object provides that interface.

scalability_and_performance/ztp-deploying-disconnected.adoc

@@ -123,6 +123,11 @@ include::modules/ztp-customizing-the-install-extra-manifests.adoc[leveloffset=+1
 
 include::modules/ztp-deploying-a-site.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#bmc-addressing_ipi-install-installation-workflow[BMC addressing]
+
 include::modules/ztp-talo-integration.adoc[leveloffset=+1]
 
 // End of 340
@@ -196,6 +201,11 @@ include::modules/ztp-roll-out-the-configuration-changes.adoc[leveloffset=+2]
 
 include::modules/ztp-manually-install-a-single-managed-cluster.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#bmc-addressing_ipi-install-installation-workflow[BMC addressing]
+
 include::modules/ztp-du-host-bios-requirements.adoc[leveloffset=+2]
 
 include::modules/ztp-configuring-a-static-ip.adoc[leveloffset=+2]