On Thu, Oct 19, 2017 at 3:06 PM, Roy Golan wrote:
>
>
> On Thu, 19 Oct 2017 at 14:02 Michal Skrivanek
> wrote:
>
>>
>> > On 18 Oct 2017, at 11:42, Roy Golan wrote:
>> >
>> >
>> >
>> > On Wed, 18 Oct 2017 at 10:25 Michal
> On 19 Oct 2017, at 09:06, Marek Libra wrote:
>
> Regarding libvirt, there's fallback to Libvirt provider (part of
> cockpit-machines) for VMs which are not managed by oVirt.
It’s layered, so the oVirt specifics are on top of the libvirt-based code. So
the whole VM
Regarding libvirt, there's fallback to Libvirt provider (part of
cockpit-machines) for VMs which are not managed by oVirt.
For the oVirt ones, oVirt API handles all the actions.
It's not yet implemented, but I'm considering to fallback to Libvirt for
selected actions in case the oVirt API can't
This looks great, guys. Congrats!
Does this also work with plain libvirt?
On Wed, Oct 18, 2017 at 3:24 AM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:
> Hi all,
> I’m happy to announce that we finally finished initial contribution of
> oVirt specific support into the Cockpit