-
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
Question: Installing a nested libvirt cluster from a Linux VM #334
Comments
Do you think supporting libvirt without nested virt available is useful? It's going to be very, very slow. From a quick look at the libvirt terraform provider, it seems to assume KVM. There is code they use for testing purposes to set the libvirt type to "qemu" (for when kvm is not available) that you could use. Running this before running the installer may do the trick. export TERRAFORM_LIBVIRT_TEST_DOMAIN_TYPE="qemu" |
Well, the idea would be to deploy to a VM that will be target for the tectonic installer (which will run an all-in-one). However, it would be possible to have a deployment/installer VM started alongside of it, as long as it can target Hyper-V, KVM or Hyperkit/xhyve. |
@russellb It is useful but not if it is going to be very, very slow. How was the tectonic sandbox was working, was it also using the nested virt? |
What will actually run as virtualization? The installer node or a management node (like the overcloud for RDO)? Technically it is possible to have providers for Terraform that target a local 'cloud'-solution, such as Hyper-V... but from the issue related to this, it is not something that is on their rader: hashicorp/terraform#3004 (use system center to target hyper-v). |
You can definitely do nested virt with KVM. Or is this Linux VM running on something other than Linux? |
yes, it mostly Windows/MacOS. |
To get acceptable performance, it needs to be native VMs on those platforms. One route would be to try to add support for one of the other libvirt drivers, like virtualbox or hyper-v (https://libvirt.org/drivers.html). Another path would be to add support using a different terraform provider, like https://github.com/terra-farm/terraform-provider-virtualbox. None of this would be trivial, though. Everyone should get a real Linux development environment, instead. :-) |
Closing due to inactivity. |
@crawford: Closing this issue. 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 kubernetes/test-infra repository. |
This is mostly duplicate to #201 but I just want to understand if I have a Linux VM (assume CentOS/Fedora) can I use the installer on top of it to provision single node cluster (Provided I have required libvirt dependency but doesn't have nested virtualization)?
The text was updated successfully, but these errors were encountered: