OSDOCS-12787: iSCSI booting for Agent #88177
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@skopacz1: This pull request references OSDOCS-12787 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/L
| + | ||
| [NOTE] | ||
| ==== | ||
| This is the preferred method for the Agent-based installation. Using {ztp} manifests is optional. | ||
| ==== |
There was a problem hiding this comment.
I tracked down the creation of this note to this comment thread here. It doesn't make sense to place this note under the step for creating the installation directory, and not specifying what "this" preferred method is seems confusing.
So I moved this note to this section's description. Considering that, since adding this note, I've renamed this procedure to mention "preferred inputs" anyways, I could even delete the note entirely. I'll leave that up to SME and QE to decide.
installing/installing_with_agent_based_installer/installing-using-iscsi.adoc
Show resolved
Hide resolved
skopacz1
force-pushed
the
OSDOCS-12787
branch
from
3b51af8 to
0f3c625
Compare
| set initiator-iqn <iscsi_initiator_base>:\${hostname} | ||
| sanboot --keep iscsi:<iscsi_network_subnet>.1::::$<iscsi_initiator_base>:\${hostname} |
There was a problem hiding this comment.
need example values here for the initiator base and subnet
There was a problem hiding this comment.
Also I am not sure what this page should have been called, so feel free to suggest alternative titles. For now I somewhat followed the naming of the "Preparing PXE assets for OCP" page.
|
@skopacz1: This pull request references OSDOCS-12787 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@skopacz1: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| toc::[] | ||
|
|
||
| You can boot an {product-title} cluster through iSCSI using an ISO image generated by the Agent-based Installer. | ||
| The following procedures describe how to prepare the necessary installation resources for you to upload to an iSCSI target. |
There was a problem hiding this comment.
We're reloading uploading to the target, which can be a separate iSCSI disk. So perhaps "resources to boot off of an iSCSI target"?
| Static networking is not supported. | ||
| * You must create an additional network for iSCSI that is separate from the machine network of the cluster. | ||
| The machine network is rebooted during cluster installation and cannot be used for the iSCSI session. | ||
| * If the iSCSI server uses disks, the iSCSI disk must be specified using the `rootDeviceHints` parameter. |
There was a problem hiding this comment.
This should refer to the actual host you are installing the agent ISO on, not the ISCSI server.
Perhaps - "ff the host on which you are booting the agent ISO also has an installed disk, it may be necessary to specify the iSCSI disk name in the rootDeviceHints parameter to ensure that it is picked as the boot disk for the final RHCOS image."
| * You must create an additional network for iSCSI that is separate from the machine network of the cluster. | ||
| The machine network is rebooted during cluster installation and cannot be used for the iSCSI session. | ||
| * If the iSCSI server uses disks, the iSCSI disk must be specified using the `rootDeviceHints` parameter. | ||
| You can also use a diskless environment for iSCSI booting. |
There was a problem hiding this comment.
In that case it would not be necessary to set the 'rootDeviceHints'.
| -- | ||
| where: | ||
|
|
||
| <iscsi_initiator_base>:: Specifies the (need description here). |
There was a problem hiding this comment.
Specifies the iSCSI initiator name on the host that is booting the ISO. This name can be used by the the iSCSI target.
| where: | ||
|
|
||
| <iscsi_initiator_base>:: Specifies the (need description here). | ||
| <iscsi_network_subnet>:: Specifies the subnet of the iSCSI network. |
There was a problem hiding this comment.
Specifies the IP address of the iSCSI target.
| $ cat << EOF > agent.ipxe | ||
| !ipxe | ||
| set initiator-iqn <iscsi_initiator_base>:\${hostname} | ||
| sanboot --keep iscsi:<iscsi_network_subnet>.1::::$<iscsi_initiator_base>:\${hostname} |
There was a problem hiding this comment.
The scsi_initiator_base do not have to be the same (but can be). We should make them different to make it clearer.
The one at line 26 is the name of the iSCSI initiator (resides on the host). The one at line 27 is the iSCSI target name.
| set initiator-iqn <iscsi_initiator_base>:\${hostname} | ||
| sanboot --keep iscsi:<iscsi_network_subnet>.1::::$<iscsi_initiator_base>:\${hostname} |
OSDOCS-12787
Version(s): 4.18+
This PR documents the generic support for iSCSI booting using resources generated by the Agent-based Installer.
QE review:
Previews: