[PATCH V7 09/12] spec: Remove libvirt-daemon dependency from drivers

[Andrea Bolognani]

On Tue, Jan 10, 2023 at 04:55:03PM -0700, Jim Fehlig wrote:
> On 1/9/23 10:42, Jim Fehlig wrote:
> >   %package daemon-driver-qemu
> >   Summary: QEMU driver plugin for the libvirtd daemon
> > -Requires: libvirt-daemon = %{version}-%{release}
> > +Requires: libvirt-daemon-common = %{version}-%{release}
>
> While testing this series I found libvirt-daemon-common alone is not enough.
> virtqemud.service.in has
>
> Requires=virtlogd.socket
> Requires=virtlockd.socket
>
> So we'll need to add libvirt-daemon-lock and libvirt-daemon-log here, and
> where needed in the other hypervisor drivers. Or adjust the service files.
> Preferences?

Those were added in

  commit 88c5b9f827779ae6fe5a6f08100a4b6184492a1c
  Author: Daniel P. Berrangé <berrange at redhat.com>
  Date:   Tue Aug 31 10:59:39 2021 +0100

    qemu, xen: add missing deps on virtlockd/virtlogd sockets

    The QEMU driver uses both virtlogd and virtlockd, while the Xen driver
    uses virtlockd. The libvirtd.service unit contains deps on the socket
    units for these services, but these deps were missed in the modular
    daemons. As a result the virtlockd/virtlogd sockets are not started
    when the virtqemud/virtxend daemons are started.

    Reviewed-by: Jiri Denemark <jdenemar at redhat.com>
    Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>

I think we might need to weaken these relationship from Requires to
Wants, as that should still ensure that the corresponding sockets are
activated for standard deployments without making more specialized
ones (e.g. without virtlockd) impossible.

Similarly, I think we're missing Wants for virtstoraged.socket,
virtnetworkd.socket, virtsecretd.socket and so on.

Dan?

-- 
Andrea Bolognani / Red Hat / Virtualization