mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
Merge pull request #15058 from kalexand-rh/BZ1713125
bug 1713125 adding pxe booting
This commit is contained in:
Kathryn Alexander
@@ -36,7 +36,16 @@ include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-generate-ignition-configs.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-user-infra-machines-iso.adoc[leveloffset=+1]
|
||||
[id="creating-machines-bare-metal"]
|
||||
== Creating {op-system-first} machines
|
||||
|
||||
Before you install a cluster on bare metal infrastructure that you provision,
|
||||
you must create {op-system} machines for it to use. Follow either the steps
|
||||
to use an ISO image or network PXE booting to create the machines.
|
||||
|
||||
include::modules/installation-user-infra-machines-iso.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-user-infra-machines-pxe.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-installing-bare-metal.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
//
|
||||
// * installing/installing_bare_metal/installing-bare-metal.adoc
|
||||
|
||||
[id=" installation-user-infra-machines-iso_{context}"]
|
||||
[id="installation-user-infra-machines-iso_{context}"]
|
||||
= Creating {op-system-first} machines using an ISO image
|
||||
|
||||
Before you install a cluster on bare metal infrastructure that you provision,
|
||||
@@ -81,5 +81,5 @@ specified.
|
||||
====
|
||||
You must create the boostrap and control plane machines at this time. Because
|
||||
some pods are deployed on compute machines by default, also create at least two
|
||||
compute machine before you install the cluster.
|
||||
compute machines before you install the cluster.
|
||||
====
|
||||
|
||||
105
modules/installation-user-infra-machines-pxe.adoc
Normal file
105
modules/installation-user-infra-machines-pxe.adoc
Normal file
@@ -0,0 +1,105 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_bare_metal/installing-bare-metal.adoc
|
||||
|
||||
[id="installation-upi-machines-pxe-{context}"]
|
||||
= Creating {op-system-first} machines by PXE or iPXE booting
|
||||
|
||||
Before you install a cluster on bare metal infrastructure that you provision,
|
||||
you must create {op-system} machines for it to use. You can use PXE or iPXE
|
||||
booting to create the machines.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* Obtain the Ignition config files for your cluster.
|
||||
* Configure suitable PXE or iPXE infrastructure.
|
||||
* Have access to an HTTP server that you can access from your computer.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Upload the master, worker, and bootstrap Ignition config files that the
|
||||
installation program created to your HTTP server. Note the URLs of these files.
|
||||
|
||||
. Obtain the {op-system} ISO image, compressed metal BIOS, `kernel`
|
||||
and `initramfs` files from the
|
||||
link:https://access.redhat.com/downloads[Product Downloads] page on the Red
|
||||
Hat customer portal or the
|
||||
link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.1/[{op-system} image mirror].
|
||||
+
|
||||
The file names contain the {product-title} version number and file upload date.
|
||||
They resemble the following examples:
|
||||
|
||||
** ISO: `rhcos-<version>-<date>-installer.iso`
|
||||
** Compressed metal BIOS: `rhcos-<version>-<date>-metal-bios.raw.gz`
|
||||
** `kernel`: `rhcos-<version>-<date>-installer-kernel`
|
||||
** `initframs`: `rhcos-<version>-<date>-installer-initramfs.img`
|
||||
|
||||
. Upload the compressed metal BIOS file and the `kernel` and `initramfs` files
|
||||
to your HTTP server.
|
||||
|
||||
. Configure the network boot infrastructure so that the machines boot from their
|
||||
local disks after {op-system} is installed on them.
|
||||
|
||||
. Configure PXE or iPXE installation for the {op-system} images.
|
||||
+
|
||||
Modify one of the following example menu entries for your environment and verify
|
||||
that the image and Ignition files are properly accessible:
|
||||
** For PXE:
|
||||
+
|
||||
----
|
||||
DEFAULT pxeboot
|
||||
TIMEOUT 20
|
||||
PROMPT 0
|
||||
LABEL pxeboot
|
||||
KERNEL http://<HTTP_server>/rhcos-<version>-<date>-installer-kernel <1>
|
||||
APPEND ip=dhcp rd.neednet=1 initrd=http://<HTTP_server>/rhcos-<version>-<date>-installer-initramfs.img console=tty0 console=ttyS0 coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://<HTTP_server>/rhcos-<version>-<date>-metal-bios.raw.gz coreos.inst.ignition_url=http://<HTTP_server>/bootstrap.ign
|
||||
----
|
||||
<1> Specify the location of the `kernel` file that you uploaded to your HTTP
|
||||
server.
|
||||
<2> Specify locations of the {op-system} files that you uploaded to your
|
||||
HTTP server. The `initrd` parameter value is the location of the `initramfs` file,
|
||||
the `coreos.inst.image_url` parameter value is the location of the compressed
|
||||
metal BIOS file, and the `coreos.inst.ignition_url` parameter value is the
|
||||
location of the bootstrap Ignition config file.
|
||||
|
||||
** For iPXE:
|
||||
+
|
||||
----
|
||||
kernel http://<HTTP_server>/rhcos-<version>-<date>-installer-kernel ip=dhcp rd.neednet=1 initrd=http://<HTTP_server>/rhcos-<version>-<date>-installer-initramfs.img console=tty0 console=ttyS0 coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://<HTTP_server>/rhcos-<version>-<date>-metal-bios.raw.gz coreos.inst.ignition_url=http://<HTTP_server>/bootstrap.ign <1>
|
||||
initrd http://<HTTP_server>/rhcos-<version>-<date>-installer-initramfs.img <2>
|
||||
boot
|
||||
----
|
||||
<1> Specify locations of the {op-system} files that you uploaded to your
|
||||
HTTP server. The `kernel` parameter value is the location of the `kernel` file,
|
||||
the `initrd` parameter value is the location of the `initramfs` file,
|
||||
the `coreos.inst.image_url` parameter value is the location of the compressed
|
||||
metal BIOS file, and the `coreos.inst.ignition_url` parameter value is the
|
||||
location of the bootstrap Ignition config file.
|
||||
<2> Specify the location of the `initramfs` file that you uploaded to your HTTP
|
||||
server.
|
||||
|
||||
. If you use UEFI, edit the included `grub.conf` file that is included in the
|
||||
ISO that you downloaded to include the following installation options:
|
||||
+
|
||||
----
|
||||
menuentry 'Install Red Hat Enterprise Linux CoreOS' --class fedora --class gnu-linux --class gnu --class os {
|
||||
linux /images/vmlinuz nomodeset rd.neednet=1 coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://<HTTP_server>/rhcos-<version>-<date>-metal-bios.raw.gz coreos.inst.ignition_url=http://<HTTP_server>/bootstrap.ign <1>
|
||||
initrd http://<HTTP_server>/rhcos-<version>-<date>-installer-initramfs.img <2>
|
||||
}
|
||||
----
|
||||
<1> For the `coreos.inst.image_url` parameter value, specify the location of
|
||||
the compressed metal UEFI file that you uploaded to your HTTP server. For the
|
||||
`coreos.inst.ignition_url`, specify the location of the bootstrap Ingition
|
||||
config file that you uploaded to your HTTP server.
|
||||
<2> Specify the location of the `initramfs` file that you uploaded to your HTTP
|
||||
server.
|
||||
|
||||
. Continue to create the machines for your cluster.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
You must create the boostrap and control plane machines at this time. Because
|
||||
some pods are deployed on compute machines by default, also create at least two
|
||||
compute machine before you install the cluster.
|
||||
====
|
||||
|
||||
Reference in New Issue
Block a user