designs/management-console/service-discovery.md

7 Created: 2019-07-12
11 [1] https://www.engineersgarage.com/Articles/IoT-Service-Discovery-Protocols [2]
14 https://github.com/lathiat/avahi/blob/master/avahi-daemon/example.service
16 Apple’s Bonjour uses mDNS and DNS-SD. Linux’s Avahi uses IPv4LL, mDNS, and
17 DNS-SD. Linux’s systemd uses resolve hostnames on a network via DNS, mDNS, and
24 wants to discover the vendor-specific server.
26 eg: Management console wants to discover the low-end server of manufacturer XYZ.
32 mDNS/DNS-SD protocol suite. BMC publishes the hostname and interface details to
35 The services that are being published by Avahi have various fields like -
37 the above-listed problem, we are proposing a solution in which the
38 vendor-specific information is included in the text record field of the Avahi
42 service-specific data is passed through a systemd service specific bb file.
45 the vendor-specific information in the avahi service file(under txt-record).
49 https://gerrit.openbmc.org/c/openbmc/meta-phosphor/+/22950
50 https://gerrit.openbmc.org/c/openbmc/meta-ibm/+/22951
63 Avahi-browse -rt <service type> e.g. To discover service type :
64 \_obmc_rest.\_tcp avahi-browse -rt \_obmc_rest.\_tcp Output of the above command
65 is as follows avahi-browse -rt \_obmc_rest.\_tcp
67 - eth0 IPv6 obmc_rest \_obmc_rest.\_tcp local
68 - eth0 IPv4 obmc_rest \_obmc_rest.\_tcp local = eth0 IPv6 obmc_rest
70   [witherspoon-cdcb785972fb41f082c7ca747e287fa6.local] address =
73   [witherspoon-cdcb785972fb41f082c7ca747e287fa6.local] address = [9.5.180.233]