On Fri, Oct 03, 2008 at 03:29:17PM +0200, Daniel Veillard wrote:
> On Thu, Oct 02, 2008 at 05:33:54PM +0200, Daniel Veillard wrote:
> > On Thu, Oct 02, 2008 at 08:16:02AM -0700, Ian Main wrote:
> > > On Thu, 2 Oct 2008 16:50:08 +0200
> > > Daniel Veillard <veillard@xxxxxxxxxx> wrote:
> > >
> > > > On Thu, Oct 02, 2008 at 03:40:06PM +0100, Daniel P. Berrange wrote:
> > > > > On Thu, Oct 02, 2008 at 03:06:01PM +0200, Daniel Veillard wrote:
> > > > > > You also need 'yum install qpidd' I suspect this indicates a missing
> > > > > > dependancy maybe in the libvirt-qpid package but I'm not 100% sure
> > > > >
> > > > > Yeah, i believe that should be a requirement. NB, the versions of qpidc
> > > > > and qpidd in Fedora currently are too old for libvirt-qpid. I've been
> > > > > speaking with qpid maintainer and they'll push a new build to Fedora in
> > > > > the very near future.
> > > >
> > > > Ah, that probably explains why that didn't work for me, I got my qpidd
> > > > from Fedora ...
> > > > Another question, upon rebout the QPid service starts automatically,
> > > > I wonder if there is something to do to be able to connect assuming
> > > > a "default install" and not starting without auth .
> > >
> > > Ah, I know what happened.. I changed the dependencies since my first email.
> > > qpidd isn't needed for libvirt-qpid to operate. It's just an agent and can
> > > talk to a qpidd on a different host.
> >
> > okay, I was guessing something like that which is why i was so
> > cautious in my wording ;-)
>
> Okay I now have things working ... on one machine. Which is
> interesting but not really the point of the exercise :-)
> I have 3 machines. qpidd runs on machine A, qpid-tool on that machine
> allows to access the local node and local domains. libvirt-qpid
> started on machine B and C in the same subnet without error,
> but well they don't find the qpidd on machine A since I don't see them
> there. qpid-tool there tries to get to localhost and fail.
> If then I install and start qpidd on machine B qpid-tool can connect
> to it ... but the already started libvirt-qpid don't seems to be
> able to find it, unless I restart it which seems to indicate a failure
> to connect after startup. And I'm still only able to list local
> domains/nodes never remote ones.
>
> Ideas ?
I got this working across 3 machines as follows
- Machine A provides a Qpid broker, run as root with
qpidd --auth no
- Machine B and C are libvirt hosts, each run a libvirtd, and libvirt-qpid
libvirt-qpid --broker machineA.example.com
On machine A, if you run 'qpid-tool' you should now see node, domain
objects from both machines B & C. NB, it take 5-10 seconds from
starting libvirt-qpid before they appear in the broker
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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list