-
-
Notifications
You must be signed in to change notification settings - Fork 23
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 for roboxes/generic boxes #118
Comments
If you can find a way to shim them into the build i'd be happy to merge a PR, assuming they work as expected |
So as i quick test i did the following:
The generic libvirt boxes depend on an internal libvirt management network and are by default configured
I think the one way one would get the same behavior with the ovirt4 provider is to have an external https://github.com/oVirt/ovirt-provider-ovn which seems to have the feature to create networks with DHCP enabled, So provision with the vagrant-ovirt4
|
Is there anything actionable here? Im still unsure about this:
Im not familiar with this functionality being in the provider itself. Is it inherited in the provider? Or is this on the ovirt server itself? |
vagrant-libvirt for example checks if the base image configured in the Vagrantfile is available in the local storage where |
hi there,
i mainly using vagrant with the libvirt provider. There is a big variety of operating systems available, created by the
roboxes project (https://github.com/lavabit/robox). Maybe it would make sense to have support for these boxes
in the ovirt4 provider too? They should meet all requirements as they work on plain libvirt nicely (but are missing cloud-init).
This would make it easier to use existing boxes, and not having to use a dummy box with templates ..
The text was updated successfully, but these errors were encountered: