You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is support for provisioning containers and using libvirt only locally.
I would like to be able to:
Use remote host as a hypervisor.
Use remote host as a podman container host.
Do that with a previously provisioned machine.
My use-case would be to get a VM in supported providers (AWS, OpenStack, libvirt, beaker) and use it as a container host and hypervisor. This would enable running workflows dependent on windows (AD integration testing) also in beaker.
The text was updated successfully, but these errors were encountered:
This is already possible but bit indirectly. Treat it as 2 jobs, One job gets the host vm and second is executed on the host with the local containers/vms. The only complexity is if you want to combine the 2 methods together as it would require to combine the outputs of both provisioning.
Currently there is support for provisioning containers and using libvirt only locally.
I would like to be able to:
My use-case would be to get a VM in supported providers (AWS, OpenStack, libvirt, beaker) and use it as a container host and hypervisor. This would enable running workflows dependent on windows (AD integration testing) also in beaker.
The text was updated successfully, but these errors were encountered: