Kyle,
I'm afraid I'm lacking some context here. Are you trying to offer AMQP
from an OpenShift application? What is the network configuration of
your host system? Qpid is simply a standard network service on a TCP
port. Making it "external" is a matter of providing access through DNS,
public IP addresses, and the Firewall. I don't think OpenShift will
allow you to expose anything that isn't via an HTTP proxy over port 80.
-Ted
On 02/06/2014 01:57 PM, Kyle Crumpton (kcrumpto) wrote:
Hi all.
I have a question; I'm having AMQP sit on a Linux Container on a machine. AMQP
listens on address: $OPENSHIFT-QPID-IP:5672
So say I have a system where the Linux container sits on "node.example.com" on a
container named "qpid-example.example.com".
This would exist as a CNAME record on my name server. (e.g.
qpid-example.example.com CNAME IN node.example.com)
My question is this.. is there a way that I can communicate with this internal
interface? Say I wanted a device running on my PC to communicate with this
external AMQP server. Would there be a clean way in qpid to do that? Or will
$OPENSHIFT-QPID-IP be internal only?
tldr version: Can I make qpid available externally so satellites can connect?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
