-
Notifications
You must be signed in to change notification settings - Fork 244
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
Multi-arch support; S390x (IBM Z) #1281
Comments
What platform/hypervisor would you want to run crc on? |
The platform I requested is S390x (IBM Z) with hypervisor zKVM or DPM or ZVM. To start this work, How to breakdown the work? |
First of all, you need to be sure/confirm that images can be generated
using the codeready/snc repo. Without images there is no need to start work
on the driver.
The driver should be modeled after
codeready/machine-driver-[libvirt/hyperkit] in the way that it performs:
* handling the image from the bundle
* create the vm
* start the vm
* stop the vm
* delete the vm
* provide IP endpoint
* etc.
|
Note: if an abstraction already exist around zKVM, DPM or ZV, like using
libvirt, this would be preferred to avoid duplication or needing multiple
implementations.
Note 2: send an email to discuss what is needed.
|
@gbraad There is libvirt solution on IBM Z. |
In that case the existing libvirt driver might be sufficient and would only need minimal changes. However image generation remains ... which also relies on libvirt. |
@zhengxiaomei123 single node clusters can be provisioned in a zKVM environment for libvirt based deploys. The snc scripts can be used to create a single node cluster on Z with some tweaks (mostly around setting the right images/executables). This means we can also get a CRC disk image although we have not worked on that yet as it has not been required. I will discuss offline with you more about this. It would also be good to know what the use case for this will be as we have zVM and zKVM full cluster Openshift deploys already working. |
Any news on this... else I would like to close the issue as it is not on our roadmap and does not match the usecase of CRC. |
Closing |
@gbraad thanks for the info, this is not in our priority list on s390x platform |
Technical details were provided, as was done by Prashanth.
|
hello, I created crc-org/snc#209 to address s390x and ppc64le. Since 4.3 the mirror now contains the binaries for IBM's arches. Please reach out to me on slack if you have any questions (username: mick). I have been talking with @zhengxiaomei123 via email about this. Next steps would be to help provide snc team with hardware for testing. |
crc-org/snc#209 has been merged now. |
Is there any plan to do mutl-arch support? The CRC for linux now is amd64 based. How to add a new hypervisor driver ? Thanks.
The text was updated successfully, but these errors were encountered: