Hello Chester, thank you very much. I will look into this.
Kind Regards, Andreas On Mon, Nov 13, 2017 at 5:06 PM, Chester <[email protected]> wrote: > https://www.clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/ > html/Clusters_from_Scratch/index.html > will get you started with pacemaker. The DRBD walkthrough is easy enough to > follow to start understanding the clustering system. > > For qpidd, you'll need the following resources: > > 1. qpidd service clone (1 running on each node) resource > 2. cluster vip (service/cluster/VIP address) resource > 3. qpidd-primary service resource > 4. fence resources > > My config looks like this: > > [root@node-01 ~]# pcs status > > Cluster name: qpid_mgmt_broker_cluster > > Stack: corosync > > Current DC: node-01.subdomain.domain.com (version > 1.1.15-11.el7_3.5-e174ec8) - partition with quorum > > Last updated: Mon Nov 13 11:01:38 2017 Last change: Thu Nov 9 17:42:21 > 2017 by root via crm_attribute on node-03.subdomain.domain.com > > > 3 nodes and 8 resources configured > > > Online: [ node-01.subdomain.domain.com node-02.subdomain.domain.com > node-03.subdomain.domain.com ] > > > Full list of resources: > > > Clone Set: qpidd-service-clone [qpidd-service] > > Started: [ node-01.subdomain.domain.com node-02.subdomain.domain.com > node-03.subdomain.domain.com ] > > cluster-vip (ocf::heartbeat:IPaddr2): Started > node-01.subdomain.domain.com > > qpidd-primary-service (lsb:qpidd-primary): Started > node-01.subdomain.domain.com > > node-01_fence_xvm (stonith:fence_xvm): Started > node-02.subdomain.domain.com > > node-02_fence_xvm (stonith:fence_xvm): Started > node-03.subdomain.domain.com > > node-03_fence_xvm (stonith:fence_xvm): Started > node-02.subdomain.domain.com > > > Daemon Status: > > corosync: active/enabled > > pacemaker: active/enabled > > pcsd: active/enabled > > > https://qpid.apache.org/releases/qpid-cpp-1.36.0/cpp- > broker/book/chapter-ha.html > is good too. > > On Fri, Nov 10, 2017 at 4:53 AM, andi welchlin <[email protected]> > wrote: > > > Hello Alan, > > > > thank you for your answer. I could install pacemaker using "apt-get > install > > pacemaker". > > > > If you could give me some hints what to do to get it run it would be > > welcome. > > > > Thanks, > > Andreas > > > > On Wed, Nov 8, 2017 at 8:01 PM, Alan Conway <[email protected]> wrote: > > > > > rgmanager has been replaced by pacemaker on RHEL7, I'm not sure what is > > > available on Ubuntu. There is no out-of-the-box integration with > > pacemaker > > > or other cluster managers, but all that is needed is some configuration > > and > > > a couple of scripts to enable the cluster manager to start, stop and > > > promote Qpid brokers at the appropriate time - the cluster manager > > already > > > knows what the "appropriate time" is based on its liveness and > membership > > > rules. If you're interested in trying to make it work, I can give you > > more > > > pointers on what is needed. > > > > > > On Wed, Nov 8, 2017 at 1:18 PM, Steve Huston <[email protected]> > > wrote: > > > > > > > I have used the qpid C++ broker in clusters. On RHEL 6. Works very > > well. > > > > > > > > > -----Original Message----- > > > > > From: andi welchlin [mailto:[email protected]] > > > > > Sent: Wednesday, November 08, 2017 12:00 PM > > > > > To: [email protected] > > > > > Subject: HA Cluster using Qpid C++ Broker 1.36.0 > > > > > > > > > > Hello, > > > > > > > > > > I would like to configure a HA cluster using the Qpid C++ message > > > broker > > > > > 1.36.0. In the handbook I read that rgmanager is neccessary. > > > > > > > > > > When I try to install it on Ubuntu 16.04 it is not found. On a > Fedora > > > > installation > > > > > it is also not found. > > > > > > > > > > Is anyone here using the Qpid message broker in a cluster? > > > > > > > > > > Are you using rgmanager or is there some other cluster manager > usable > > > on > > > > > Linux? > > > > > > > > > > Any hints are welcome ... even if you say "noone uses the Qpid > broker > > > in > > > > a > > > > > cluster". > > > > > > > > > > Kind Regards, > > > > > Andreas > > > > > > > > ------------------------------------------------------------ > --------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > >
