[libvirt] [PATCH v2 0/8] Prepare for daemon split

Daniel P. Berrangé posted 8 patches 6 years ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/20180405105147.20196-1-berrange@redhat.com
Test syntax-check passed
src/remote/remote_daemon.h          |   6 +++
src/remote/remote_daemon_dispatch.c |  94 +++++++++++++++++++-------------
src/rpc/gendispatch.pl              | 104 +++++++++++++++++++++++++-----------
3 files changed, 138 insertions(+), 66 deletions(-)
[libvirt] [PATCH v2 0/8] Prepare for daemon split
Posted by Daniel P. Berrangé 6 years ago
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 reference on the current single
connection. This will facilitate later changes.

Daniel P. Berrangé (8):
  rpc: refactor way connection object is generated for remote dispatch
  remote: push check for conn down into remoteClientFreePrivateCallbacks
  remote: use a separate connection for interface APIs
  remote: use a separate connection for network APIs
  remote: use a separate connection for nodedev APIs
  remote: use a separate connection for nwfilter APIs
  remote: use a separate connection for secret APIs
  remote: use a separate connection for storage APIs

 src/remote/remote_daemon.h          |   6 +++
 src/remote/remote_daemon_dispatch.c |  94 +++++++++++++++++++-------------
 src/rpc/gendispatch.pl              | 104 +++++++++++++++++++++++++-----------
 3 files changed, 138 insertions(+), 66 deletions(-)

-- 
2.14.3

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 0/8] Prepare for daemon split
Posted by John Ferlan 6 years ago

On 04/05/2018 06:51 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.
> 
> This series prepares for that by introducing "separate" connections,
> which are actually just an extra reference on the current single
> connection. This will facilitate later changes.
> 
> Daniel P. Berrangé (8):
>   rpc: refactor way connection object is generated for remote dispatch
>   remote: push check for conn down into remoteClientFreePrivateCallbacks
>   remote: use a separate connection for interface APIs
>   remote: use a separate connection for network APIs
>   remote: use a separate connection for nodedev APIs
>   remote: use a separate connection for nwfilter APIs
>   remote: use a separate connection for secret APIs
>   remote: use a separate connection for storage APIs
> 
>  src/remote/remote_daemon.h          |   6 +++
>  src/remote/remote_daemon_dispatch.c |  94 +++++++++++++++++++-------------
>  src/rpc/gendispatch.pl              | 104 +++++++++++++++++++++++++-----------
>  3 files changed, 138 insertions(+), 66 deletions(-)
> 

Reviewed-by: John Ferlan <jferlan@redhat.com>

(series)

John

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list