<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div><br>
<blockquote class="userQuote" style="border-left: 3px solid rgb(200, 200, 200); padding-left: 1ex; margin-left: 0.8ex; color: rgb(102, 102, 102);">
What format does the API take ? Is it a plain REST API we will<br>
call via the existing libcurl dependancy in libvirt ?</blockquote>
<br>
</div>
</div>
Yes of course. It is just what I think - plain REST API <span style="font-family: Calibri, Arial, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important">
by https requests </span>and already existing in project libcurl.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dmitry</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Daniel P. Berrangé <berrange@redhat.com><br>
<b>Sent:</b> Thursday, April 16, 2020 4:49 PM<br>
<b>To:</b> Dmitry Nesterenko <dmitry.nesterenko@virtuozzo.com><br>
<b>Cc:</b> Nikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>; Martin Kletzander <mkletzan@redhat.com>; libvir-list@redhat.com <libvir-list@redhat.com>; Dmitry Mishin <dim@virtuozzo.com><br>
<b>Subject:</b> Re: [RFC] Adding docker driver to libvirt</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Thu, Apr 16, 2020 at 01:47:39PM +0000, Dmitry Nesterenko wrote:<br>
> <br>
> > The container based drivers in libvirt have been a bit of a square-peg /<br>
> > round-hole thing. Given that we have a couple of them already (LXC,<br>
> > OpenVZ, VZ), I wouldn't say no to adding a docker one too. The only<br>
> > real issue is having people willing to do the work to implement it and<br>
> > then maintain it thereafter.<br>
> ><br>
> > Describing the scope of the desired work is probably useful....<br>
> <br>
> Hi all!<br>
> <br>
> I am that man who will do this work. I think it can be stateless<br>
> driver like hyperv driver from libvirt. Most of calls to the driver<br>
> will bring remote call to docker host by native docker API. So my<br>
> first implementation of docker driver will iclude all calls those<br>
> have realized for hyperv driver now.<br>
<br>
What format does the API take ? Is it a plain REST API we will<br>
call via the existing libcurl dependancy in libvirt ?<br>
<br>
Regards,<br>
Daniel<br>
-- <br>
|: <a href="https://berrange.com">https://berrange.com</a> -o- <a href="https://www.flickr.com/photos/dberrange">
https://www.flickr.com/photos/dberrange</a> :|<br>
|: <a href="https://libvirt.org">https://libvirt.org</a> -o- <a href="https://fstop138.berrange.com">
https://fstop138.berrange.com</a> :|<br>
|: <a href="https://entangle-photo.org">https://entangle-photo.org</a> -o- <a href="https://www.instagram.com/dberrange">
https://www.instagram.com/dberrange</a> :|<br>
<br>
</div>
</span></font></div>
</body>
</html>