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
add iscsi support to the oci image type #3264
Conversation
For the final version, I think this should be part of the |
Bare metal instances can access block volumes only using iSCSI. Therefore, we need to install iscsi-initiator-utils and pass the right kernel options in order to make boot from iSCSI-attached volume possible. Signed-off-by: Ondřej Budai <ondrej@budai.cz>
Bare metal instances can access block volumes only using iSCSI. Therefore, we need to install iscsi-initiator-utils and pass the right kernel options in order to make boot from iSCSI-attached volume possible. Signed-off-by: Ondřej Budai <ondrej@budai.cz>
Bare metal instances can access block volumes only using iSCSI. Therefore, we need to install iscsi-initiator-utils and pass the right kernel options in order to make boot from iSCSI-attached volume possible. Signed-off-by: Ondřej Budai <ondrej@budai.cz>
oci image definitions were changed, let's regen them. Signed-off-by: Ondřej Budai <ondrej@budai.cz>
69c4f7c
to
29db29f
Compare
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.
Manifest-diff
job [0] as manifests.diff
.
We don't have enough resources to get this finished anytime soon. Also, everything in this PR can be achieved just by applying the right customizations. Here's a quick guide I put together:
|
Bare metal instances can access block volumes only using iSCSI. Therefore, we need to install
iscsi-initiator-utils
and pass the right kernel options in order to make boot from iSCSI-attached volume possible.This pull request includes: