Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-29 Thread Andrea Bolognani
On Mon, 2019-07-29 at 13:30 +0100, Daniel P. Berrangé wrote: > On Sun, Jul 28, 2019 at 04:42:52PM +0200, Andrea Bolognani wrote: > > On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote: > > > +[Install] > > > +WantedBy=multi-user.target > > > +Also=virtproxyd.socket > > > +Also=virtproxyd-r

Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-29 Thread Jim Fehlig
On 7/23/19 10:02 AM, Daniel P. Berrangé wrote: > The libvirtd daemon provides the traditional libvirt experience where > all the drivers are in a single daemon, and is accessible over both > local UNIX sockets and remote IP sockets. > > In the new world we're having a set of per-driver daemons wh

Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-29 Thread Daniel P . Berrangé
On Mon, Jul 29, 2019 at 01:50:22PM +0100, Daniel P. Berrangé wrote: > On Mon, Jul 29, 2019 at 01:30:42PM +0100, Daniel P. Berrangé wrote: > > On Sun, Jul 28, 2019 at 04:42:52PM +0200, Andrea Bolognani wrote: > > > On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote: > > > [...] > > > > - W

Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-29 Thread Daniel P . Berrangé
On Mon, Jul 29, 2019 at 01:30:42PM +0100, Daniel P. Berrangé wrote: > On Sun, Jul 28, 2019 at 04:42:52PM +0200, Andrea Bolognani wrote: > > On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote: > > [...] > > > - We can make virtproxyd and the virtXXXd per-driver daemons all > > >have "C

Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-29 Thread Daniel P . Berrangé
On Sun, Jul 28, 2019 at 04:42:52PM +0200, Andrea Bolognani wrote: > On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote: > [...] > > - We can make virtproxyd and the virtXXXd per-driver daemons all > >have "Conflicts: libvirtd.service" in their systemd unit files. > >This will guar

Re: [libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-28 Thread Andrea Bolognani
On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote: [...] > - We can make virtproxyd and the virtXXXd per-driver daemons all >have "Conflicts: libvirtd.service" in their systemd unit files. >This will guarantee that libvirtd is never started at the same >time, as this would re

[libvirt] [PATCH 19/41] remote: introduce virtproxyd daemon to handle IP connectivity

2019-07-23 Thread Daniel P . Berrangé
The libvirtd daemon provides the traditional libvirt experience where all the drivers are in a single daemon, and is accessible over both local UNIX sockets and remote IP sockets. In the new world we're having a set of per-driver daemons which will primarily be accessed locally via their own UNIX