Skip to content

[enterprise-4.6] Add SME feedback to original PR#25709 (#26442) #26521

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.

Sign up for GitHub

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

Merged
bobfuru merged 1 commit into from
Oct 15, 2020
Merged

[enterprise-4.6] Add SME feedback to original PR#25709 (#26442) #26521

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 13 additions & 16 deletions installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,36 +56,33 @@ include::modules/installation-generate-ignition-configs.adoc[leveloffset=+1]
== 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.
you must create {op-system} machines for it to use. To create the machines, follow either the steps
to use an ISO image or network PXE booting.

There are several methods of configuring {op-system} during ISO and
PXE installations. These include:

* Kernel arguments: For a PXE install, you can `APPEND` arguments to the
kernel of the live installer. For an ISO install, you can interrupt the
live install boot process to add kernel arguments. In both cases, you can use
special `coreos-inst*` arguments to direct the installer, as well as
special `coreos.inst.*` arguments to direct the installer, as well as
standard boot arguments for turning standard kernel services
on or off.

* Ignition configs: You need to generate an {product-title} Ignition config
(*.ign) file for the type of node you are installing (worker, control plane,
* Ignition configs: You need to generate an {product-title} Ignition config file
(`*.ign`) for the type of node you are installing (worker, control plane,
or bootstrap). You pass the location of the Ignition config to the installed
system so that it takes effect on first boot. You can also embed that Ignition
Config into the ISO before you boot it. In special cases, you can create a
separate, limited Ignition config to pass to the live system. That limited
Ignition config could do a limited
set of tasks, like reporting reporting success to a provisioning system
after completing installation.
This special Ignition config is consumed by the installer and should not
system so that it takes effect on first boot. In special cases, you can create a
separate, limited Ignition config to pass to the live system. That Ignition config could do a certain set of tasks, such as reporting success to a provisioning system
after completing installation. This special Ignition config is consumed by the installer and should not
be used to include the standard `worker` and `master` Ignition configs.

* coreos-installer: You can boot the live ISO installer to a shell prompt,
* `coreos-installer`: You can boot the live ISO installer to a shell prompt,
which allows you to prepare the permanent system in a variety of ways
before first boot. In particular, you can manually run the `coreos-installer`
command from a shell prompt, passing it options to configure
some details of the installed system.
before first boot. In particular, you can run the `coreos-installer`
command to identify various artifacts to include, work with disk partitions,
and set up networking. In some cases, you can configure features on
the live system and copy them to the installed system.

Whether to use an ISO or PXE install depends on your situation.
A PXE install requires an available DHCP service and more preparation,
Expand Down
24 changes: 12 additions & 12 deletions installing/installing_bare_metal/installing-bare-metal.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,28 +60,28 @@ include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[lev
== 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.
you must create {op-system} machines for it to use. To create the machines, follow either the steps
to use an ISO image or network PXE booting.

There are several methods of configuring {op-system} during ISO and
PXE installations. These include:

* Kernel arguments: For a PXE install, you can `APPEND` arguments to the
kernel of the live installer. For an ISO install, you can interrupt the
live install boot process to add kernel arguments. In both cases, you can use
`special coreos-inst*` arguments, to direct the live installer, as well as
standard installation boot arguments, for turning standard kernel services
special `coreos.inst.*` arguments to direct the live installer, as well as
standard installation boot arguments for turning standard kernel services
on or off.

* Ignition configs: You need to generate an {product-title} Ignition config
(*.ign) file for the type of node you are installing (worker, control plane,
* Ignition configs: You need to generate an {product-title} Ignition config file
(`*.ign`) for the type of node you are installing (worker, control plane,
or bootstrap). You pass the location of the Ignition config to the installed
system, so it takes effect on first boot. You can also embed that Ignition
Config into the ISO before you boot it. In special cases, you can create a
separate Ignition config to pass to the live system, to do things like disk
configuration before installing the system.
system so that it takes effect on first boot. In special cases, you can create a
separate, limited Ignition config to pass to the live system. That Ignition config could do a certain set of tasks, such as reporting success to a provisioning system
after completing installation. This special Ignition config is consumed by the installer and should not
be used to include the standard `worker` and `master` Ignition configs.

* coreos-installer: You can boot the live ISO installer to a shell prompt,
* `coreos-installer`: You can boot the live ISO installer to a shell prompt,
which allows you to prepare the permanent system in a variety of ways
before first boot. In particular, you can run the `coreos-installer`
command to identify various artifacts to include, work with disk partitions,
Expand All @@ -97,7 +97,7 @@ up more than a few machines.
[NOTE]
====
As of {product-title} 4.6, the {op-system} ISO and other installation artifacts
provide support for installation on disks with 4k sectors.
provide support for installation on disks with 4K sectors.
====


Expand Down
22 changes: 11 additions & 11 deletions installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,28 +73,28 @@ include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[lev
== 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.
you must create {op-system} machines for it to use. To create the machines, follow either the steps
to use an ISO image or network PXE booting.

There are several methods of configuring {op-system} during ISO and
PXE installations. These include:

* Kernel arguments: For a PXE install, you can `APPEND` arguments to the
kernel of the live installer. For an ISO install, you can interrupt the
live install boot process to add kernel arguments. In both cases, you can use
`special coreos-inst*` arguments, to direct the live installer, as well as
standard installation boot arguments, for turning standard kernel services
special `coreos.inst.*` arguments to direct the live installer, as well as
standard installation boot arguments for turning standard kernel services
on or off.

* Ignition configs: You need to generate an {product-title} Ignition config
(*.ign) file for the type of node you are installing (worker, control plane,
* Ignition configs: You need to generate an {product-title} Ignition config file
(`*.ign`) for the type of node you are installing (worker, control plane,
or bootstrap). You pass the location of the Ignition config to the installed
system, so it takes effect on first boot. You can also embed that Ignition
Config into the ISO before you boot it. In special cases, you can create a
separate Ignition config to pass to the live system, to do things like disk
configuration before installing the system.
system so that it takes effect on first boot. In special cases, you can create a
separate, limited Ignition config to pass to the live system. That Ignition config could do a certain set of tasks, such as reporting success to a provisioning system
after completing installation. This special Ignition config is consumed by the installer and should not
be used to include the standard `worker` and `master` Ignition configs.

* coreos-installer: You can boot the live ISO installer to a shell prompt,
* `coreos-installer`: You can boot the live ISO installer to a shell prompt,
which allows you to prepare the permanent system in a variety of ways
before first boot. In particular, you can run the `coreos-installer`
command to identify various artifacts to include, work with disk partitions,
Expand Down
Loading