On Mon, Oct 06, 2008 at 04:18:15PM +0200, Daniel Veillard wrote: > > I got this working it's just that my firewall rules on node A blocked > access ! > Basically one need to open TCP port 5672 on the machine running the > QPid broker (and possibly 5671 when SSL auth is to be used once > configured). > Also the simplest is to edit /etc/qpidd.conf on the broker node and > add : > > auth=no > > then restart the broker with "/etc/init.d/qpidd restart" > and on all the monitored nodes edit /etc/sysconfig/libvirt-qpid and > add : > > LIBVIRT_QPID_ARGS="--broker 192.168.0.11" > > and also restart the libvirt-qpid service on them. > Assuming the services gets started automatically all the nodes will > connect automatically to the broker upon reboot without manual tuning. > > very cool ! > > I'm just wondering if there is any DNS customization trick which would > allow the qpid client to automatically find the broker based on the DNS > settings (things like _qpid._tcp SRV entries in the local domain). That > would avoid the configuration on each monitored node.
That is something oVirt does make use of, but I don't think it is useful in the general case deployment of the daemon, because regardless of whether you can find the broker, the admin needs to configure each machine with authentication credentials. So I'd just use of SRV records upto apps like oVirt to manage. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
