mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-24 22:55:23 +00:00
5a148ce846
Libvirtd has long had integration with avahi for advertising libvirtd
using mDNS when TCP/TLS listening is enabled. For a long time the
virt-manager application had support for auto-detecting libvirtds
on the local network using mDNS, but this was removed last year
commit fc8f8d5d7e3ba80a0771df19cf20e84a05ed2422
Author: Cole Robinson <crobinso@redhat.com>
Date: Sat Oct 6 20:55:31 2018 -0400
connect: Drop avahi support
Libvirtd can advertise itself over avahi. The feature is disabled by
default though and in practice I hear of no one actually using it
and frankly I don't think it's all that useful
The 'Open Connection' wizard has a disproportionate amount of code
devoted to this feature, but I don't think it's useful or worth
maintaining, so let's drop it
I've never heard of any other applications having support for using
mDNS to detect libvirtd instances. Though it is theoretically possible
something exists out there, it is clearly going to be a niche use case
in the virt ecosystem as a whole.
By removing avahi integration we can cut down the dependency chain for
the basic libvirtd install and reduce our code maint burden.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
||
|---|---|---|
| .. | ||
| input-data-admin-server-names.json | ||
| input-data-admin.json | ||
| input-data-anon-clients.json | ||
| input-data-client-auth-pending-failure.json | ||
| input-data-client-auth-pending.json | ||
| input-data-client-ids.json | ||
| input-data-client-timestamp.json | ||
| input-data-initial.json | ||
| input-data-no-keepalive-required.json | ||
| output-data-admin-server-names.json | ||
| output-data-admin.json | ||
| output-data-anon-clients.json | ||
| output-data-client-auth-pending.json | ||
| output-data-client-ids.json | ||
| output-data-client-timestamp.json | ||
| output-data-initial.json | ||
| output-data-no-keepalive-required.json | ||
| README | ||
virnetservertest data files =========================== The various input-data-*.json files are a record of all the historical formats that libvirt has been able to produce data for. Everytime a new field is added to the JSON output, a *new* input data file should be created. We must not add new fields to existing input-data files, nor must we ever re-structure them if code changes, as we must check new code handles the legacy formats. The various output-data-*.json files are the record of what the *new* JSON output should look like for the correspondingly named input-data file. It is permissible to change the existing output-data-*.json files if the format we save in is updated.