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
[email protected]
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to