-
Notifications
You must be signed in to change notification settings - Fork 593
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
Support generating iqn
and nqn
during install
#10009
Comments
|
frezbo
added a commit
to frezbo/extensions
that referenced
this issue
Jan 5, 2025
* `tgtd` is only needed if exposing `iSCSI` targets from the host, not needed when using as a client. * Use `/system/etc` as writable homedir for open-iscsi * Drop `isns` since we never ran `isns` daemon We could also split the `iscsid-wrapper` into two services, will do after what comes out of siderolabs/talos#10009. Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/extensions
that referenced
this issue
Jan 5, 2025
* `tgtd` is only needed if exposing `iSCSI` targets from the host, not needed when using as a client. * Use `/system/etc` as writable homedir for open-iscsi * Drop `isns` since we never ran `isns` daemon We could also split the `iscsid-wrapper` into two services, will do after what comes out of siderolabs/talos#10009. Signed-off-by: Noel Georgi <[email protected]>
As per discussion we'll derive these from the machine id deterministically on each boot |
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Jan 17, 2025
Generate deterministic IQN and NQN files based on `machine-id`. Fixes: siderolabs#10009 Signed-off-by: Noel Georgi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Currently we generate an
iqn
once when the iscsi extension is installed, sinceiqn
andnqn
are pretty standard, move this to talos install process, so that they remain during the lifecycle of the node.Ref: https://docs.netapp.com/us-en/e-series-santricity/sm-settings/nvme-overview.html
The text was updated successfully, but these errors were encountered: