[libvirt] [PATCH 00/10] Enable direct use of secondary drivers

Erik Skultety eskultet at redhat.com
Mon Jan 29 11:46:11 UTC 2018


On Fri, Jan 26, 2018 at 01:35:27PM +0000, Daniel P. Berrangé wrote:
> Currently the secondary drivers can only be used if you have a
> connection to a primary hypervisor driver. This series introduces
> explicit URIs that allow opening a connection that only talks to a
> specific secondary driver. In the future these URIs will resolve to
> individual daemons containing those drivers.
>
> This also allows us to fix long standing problems with most code that
> uses secrets internally. We need to pass a virConnectPtr into such code
> but some call stacks don't have a connection available. In some cases we
> open a temporary connection to the QEMU driver, but this is suboptimal
> for deployments without the QEMU driver present.
>
> Daniel P. Berrangé (10):
>   storage: move driver registration back to end of the file
>   storage: allow opening with storage:///system and storage:///session
>     URIs
>   network: move driver registration back to end of the file
>   network: allow opening with network:///system and network:///session
>     URIs
>   nwfilter: allow opening with nwfilter:///system URI
>   interface: allow opening with interface:///system and
>     interface:///session URIs
>   nodedev: allow opening with nodedev:///system and nodedev:///session
>     URIs
>   secret: allow opening with secret:///system and secret:///session URIs
>   storage: open secret driver connection at time of use
>   storage: remove virConnectPtr from all backend functions

Doc update would be nice as well, or are you planning on adding that as part of
separate series?

Erik




More information about the libvir-list mailing list