-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
AGENT-1027: Dev docs for iscsi #9296
base: main
Are you sure you want to change the base?
Conversation
@pawanpinjarkar: This pull request references AGENT-1027 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 task 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@pawanpinjarkar: 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. |
It would be useful to provide more info on why a secondary interface needs to be provided for iSCSI, i.e. because the default interface on the machine interface is reconfigured by OVN at boot so access to the root volume would be interrupted. It would also be useful to mention that both the agent ISO and the installed RHCOS image would be accessed via iSCI. Also why is a minimal agent ISO is required for non-OCI platforms? I believe its since both image are stored in the same location on the iSCSI target there may be a conflict depending on the size but it would be useful to clarify. It would also be useful to outline any limitations in a mult-inode installation regarding iSCSI, as in each node must have a dedicated iSCSI target. |
iSCSI (Internet Small Computer Systems Interface) is a network storage protocol that allows clients (initiators) to send SCSI commands to storage devices (targets) over IP networks. iSCSI provides a centralized and cost-effective storage management to use remote storage as if it were local disk storage. | ||
|
||
|
||
### Supported version: OpenShift 4.18 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Supported version: OpenShift 4.18 | |
### Supported since version: OpenShift 4.18 |
## Key Systemd Services for iSCSI Boot | ||
|
||
### `iscsistart.service` | ||
- **Path**: `data/data/agent/systemd/units/iscsistart.service` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
link to the real code?
No description provided.