Hi Jp, while the project looks intriging, it also looks still very whet behind
the ears and nothing I could do on a side job time budget.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: h
KubeVirt. https://kubevirt.io/
Otherwise, your hosts are managing VMs as threads and containers as threads,
side-by-side, without awareness of conflict.
Ex: dockerd expects to manage its network for containers, and oVirt expects to
manage a network (bridge) for VMs. Docker will be expecting t
nt: Sunday, April 12, 2020 2:15 PM
To: users@ovirt.org
Subject: [ovirt-users] Re: oVirt thrashes Docker network during installation
The general idea was, that with oVirt I'd get a little more automation and
benefits than with just using VirtualBox as a GUI for KVMs.
Boy did I underestimat
On April 12, 2020 9:54:15 PM GMT+03:00, Arman Khalatyan
wrote:
>i think it wouldn't work out of box
>ovirt will overwrite all your routes and network. you might try to tell
>ovirt do jot maintain the network of a interface where you got a docker
>and
>also add custom rules in the firewall ports t
i think it wouldn't work out of box
ovirt will overwrite all your routes and network. you might try to tell
ovirt do jot maintain the network of a interface where you got a docker and
also add custom rules in the firewall ports template on the engine.
schrieb am So., 12. Apr. 2020, 15:51:
> I w
The general idea was, that with oVirt I'd get a little more automation and
benefits than with just using VirtualBox as a GUI for KVMs.
Boy did I underestimate the amount of intellectual investment for the first
value return. Turned out quite a bit bigger than vSphere, but much more
intriguing,
On April 12, 2020 7:36:23 PM GMT+03:00, tho...@hoberg.net wrote:
>Hi Strahil,
>
>color me surprised, too, especially considering where things are
>supposed to go in terms of roadmap.
>
>Yet again, both oVIrt and Docker could be excused to think that they
>"own the hardware" they are running on, be
Hi Strahil,
color me surprised, too, especially considering where things are supposed to go
in terms of roadmap.
Yet again, both oVIrt and Docker could be excused to think that they "own the
hardware" they are running on, because it's a rather natural assumption, even
if there are good reason
On April 12, 2020 4:49:51 PM GMT+03:00, tho...@hoberg.net wrote:
>I want to run containers and VMs side by side and not necessarily
>nested. The main reason for that is GPUs, Voltas mostly, used for CUDA
>machine learning not for VDI, which is what most of the VM
>orchestrators like oVirt or vSpher
9 matches
Mail list logo
