Re: [libvirt] [PATCH 0/7] Prepare for daemon split

2018-04-06 Thread Michal Privoznik
On 04/05/2018 07:06 PM, Laine Stump wrote: > On 03/28/2018 11:18 AM, Daniel P. Berrangé wrote: >> When we split up the daemons, libvirtd will need to forward different >> sets of APIs to different daemons. This means libvirtd is going to need >> to have multiple virConnectPtr instances open. > >

Re: [libvirt] [PATCH 0/7] Prepare for daemon split

2018-04-05 Thread Daniel P . Berrangé
On Thu, Apr 05, 2018 at 01:06:28PM -0400, Laine Stump wrote: > On 03/28/2018 11:18 AM, Daniel P. Berrangé wrote: > > When we split up the daemons, libvirtd will need to forward different > > sets of APIs to different daemons. This means libvirtd is going to need > > to have multiple virConnectPtr

Re: [libvirt] [PATCH 0/7] Prepare for daemon split

2018-04-05 Thread Laine Stump
On 03/28/2018 11:18 AM, Daniel P. Berrangé wrote: > When we split up the daemons, libvirtd will need to forward different > sets of APIs to different daemons. This means libvirtd is going to need > to have multiple virConnectPtr instances open. Have you done any thinking about what will need to

[libvirt] [PATCH 0/7] Prepare for daemon split

2018-03-28 Thread Daniel P . Berrangé
When we split up the daemons, libvirtd will need to forward different sets of APIs to different daemons. This means libvirtd is going to need to have multiple virConnectPtr instances open. This series prepares for that by introducing "separate" connections, which are actually just an extra