[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Adding second broker to my setup



What form of OpenShift?

If you want all components redundant, the enterprise guide may help you do that:
https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/1/html-single/Deployment_Guide/index.html#sect-OpenShift_Enterprise-Deployment_Guide-Continuing_Broker_Installation_for_Enterprise-Configuring_Redundancy
(Not sure if there's an Origin analog for this doc yet)

If you don't want redundant datastore+activemq, then you can just configure the new broker (and node) for the existing DNS/activemq/mongodb via conf files - service ports must be open, of course. Once the node attaches to activemq it is available for use (if using districts you need to district it).

----- Original Message -----
From: "Jan Pazdziora" <jpazdziora redhat com>
To: users lists openshift redhat com
Sent: Wednesday, July 3, 2013 9:57:50 AM
Subject: Adding second broker to my setup


I have a all-on-one-machine OpenShift installation and I would like to
add additional all-on-one machine to the setup -- so that the new
machine would also serve as a broker and node.

What is the recommended method of ensuring that the new machine will
become part of the existing installation? Should it have its own
activemq and datastore? How would I let it know that it should be in
sync with the original machine (and vice versa, how will the old
machine learn about the new one)?

Thank you,

-- 
Jan Pazdziora | adelton at #ipa*, #brno
Principal Software Engineer, Identity Management Engineering, Red Hat

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]