Re: [RFC] Adding docker driver to libvirt
What format does the API take ? Is it a plain REST API we will
call via the existing libcurl dependancy in libvirt ?
Yes of course. It is just what I think - plain REST API by https requests and already
existing in project libcurl.
Dmitry
________________________________
From: Daniel P. Berrangé <berrange(a)redhat.com>
Sent: Thursday, April 16, 2020 4:49 PM
To: Dmitry Nesterenko <dmitry.nesterenko(a)virtuozzo.com>
Cc: Nikolay Shirokovskiy <nshirokovskiy(a)virtuozzo.com>; Martin Kletzander
<mkletzan(a)redhat.com>; libvir-list(a)redhat.com <libvir-list(a)redhat.com>; Dmitry
Mishin <dim(a)virtuozzo.com>
Subject: Re: [RFC] Adding docker driver to libvirt
On Thu, Apr 16, 2020 at 01:47:39PM +0000, Dmitry Nesterenko wrote:
> The container based drivers in libvirt have been a bit of a square-peg /
> round-hole thing. Given that we have a couple of them already (LXC,
> OpenVZ, VZ), I wouldn't say no to adding a docker one too. The only
> real issue is having people willing to do the work to implement it and
> then maintain it thereafter.
>
> Describing the scope of the desired work is probably useful....
Hi all!
I am that man who will do this work. I think it can be stateless
driver like hyperv driver from libvirt. Most of calls to the driver
will bring remote call to docker host by native docker API. So my
first implementation of docker driver will iclude all calls those
have realized for hyperv driver now.
What format does the API take ? Is it a plain REST API we will
call via the existing libcurl dependancy in libvirt ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
Attachments:
- attachment.html (text/html — 3.8 KB)