On 04/10/11 19:52, Adam Stokes wrote:
On Mon, 03 Oct 2011 19:37:11 -0400
Perry Myers<pmyers(a)redhat.com> wrote:
>> I think C is do-able but only using two separate ports. i.e.
>> `vios-proxy-guest /dev/virtio-devs 48999` then have the broker
>> federate with localhost:48999.
>
> ack. this seems reasonable to me. We don't need to use the official
> IANA port for something that is just a QMF/virtio-serial proxy
> connection.
>
HOST
- Broker:49000
- vios-proxy-host:49000
guest 1
- Broker:49001
- vios-proxy-guest:49000
guest 2 ->
- broker:49001
- vios-proxy-guest:49000
Setting up qpid federation
# qpid-route dynamic add localhost:49001<can not link here over
proxy>:49001 amq.direct
There is a disconnect between how the broker communicate between each
other over the vios-proxy since they can not bind to the guest ports
themselves. So im a little confused as to what you want to do with the
different ports? Also, how is changing the ports going to help if the
broker can't even bind to them on the guest? The host and
vios-proxy-host is the only case where a broker can be listening on the
vios proxy port.
Ah, got it - you are correct.
I was thinking "qpid-route dynamic add localhost:49000 localhost:49001
amq.direct", but I think what you're saying is that we can only add one
half of the route that way. We can't add a bidirectional route because
the host broker has no way of contacting the guest broker, only the
other way around.
Incidentally, have we tested broker federation across different
machines? Because we're passing localhost:49000 as one endpoint of the
routes, and I suspect that might not work if the brokers are on
different hosts.
thanks,
Zane.