As an alternative to re-implementing support in cobbler proper, we could
simply add an entry to /etc/avahi/services to accomplish the same thing,
using the same tools (avahi-daemon). As far as I can see, the only
advantage to having cobblerd do this for us is the fact that the service
is only advertised when cobblerd is running.
I've been using a avahi service entry as follows alongside cobbler:
<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
<name replace-wildcards="yes">Cobbler server on %h</name>
<service protocol="ipv4">
<type>_orchestra_cobbler._tcp</type>
<port>80</port>
</service>
</service-group>
The service type could be changed to something more general
(_orchestra_provisioning_server) While this would get discovered
regardless of the availability of cobbler, the ability to discover the
provisioning server within the local orchestra infrastructure may be
useful later on for other tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893189
Title:
avahi advertisement support disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/893189/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
