date:20170823

Re: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

2017-08-23 Thread Eric Robinson

I got it.


From: Eric Robinson [mailto:eric.robin...@psmnv.com]
Sent: Wednesday, August 23, 2017 6:51 PM
To: Cluster Labs - All topics related to open-source clustering welcomed 

Subject: Re: [ClusterLabs] Is there a Trick to Making Corosync Work on 
Microsoft Azure?

I figured out the cause. CMAN got installed by yum, and so none of my changes 
to corosync.conf had any effect, including the udpu directive. Now I just have 
to figure out how to enable unicast in cman.

--
Eric Robinson


From: Eric Robinson [mailto:eric.robin...@psmnv.com]
Sent: Wednesday, August 23, 2017 3:16 PM
To: Cluster Labs - All topics related to open-source clustering welcomed 
>
Subject: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft 
Azure?

I created two nodes on Micrsoft Azure, but I can't get them to join a cluster. 
Any thoughts?

OS: RHEL 6.9
Corosync version: 1.4.7-5.el6.x86_64
Node names: ha001a (172.28.0.4/23), ha001b (172.28.0.5/23)

The nodes are on the same subnet and can ping and ssh to each other just fine 
by either host name or IP address.

I have configured corosync to use unicast.

corosync-cfgtool looks fine...

[root@ha001b corosync]# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
id  = 172.28.0.5
status  = ring 0 active with no faults

...but corosync-objctl only shows the local node...

[root@ha001b corosync]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.2.join_count=1
runtime.totem.pg.mrp.srp.members.2.status=joined

...pcs status shows...

Cluster name: ha001
Stack: cman
Current DC: ha001b (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:04:33 2017  Last change: Wed Aug 23 
17:51:07 2017 by root via cibadmin on ha001b

2 nodes and 0 resources configured

Online: [ ha001b ]
OFFLINE: [ ha001a ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...it shows the opposite on the other node...

[root@ha001a ~]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.1.join_count=1
runtime.totem.pg.mrp.srp.members.1.status=joined
[root@ha001a ~]# pcs status
Cluster name: ha001
Stack: cman
Current DC: ha001a (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:06:04 2017  Last change: Wed Aug 23 
17:51:03 2017 by root via cibadmin on ha001a

2 nodes and 0 resources configured

Online: [ ha001a ]
OFFLINE: [ ha001b ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...here is my corosync.conf...

compatibility: whitetank

totem {
version: 2
secauth: off
interface {
member {
memberaddr: 172.28.0.4
}
member {
memberaddr: 172.28.0.5
}
ringnumber: 0
bindnetaddr: 172.28.0.0
mcastport: 5405
ttl: 1
}
transport: udpu
}

logging {
fileline: off
to_logfile: yes
to_syslog: yes
logfile: /var/log/cluster/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
}

I used tcpdump and I see a lot of traffic between them on port 2224, but 
nothing else.

Is there an issue because the bindinetaddr is 172.28.0.0 but the members have a 
/23 mask?

--
Eric Robinson

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

2017-08-23 Thread Eric Robinson

I figured out the cause. CMAN got installed by yum, and so none of my changes 
to corosync.conf had any effect, including the udpu directive. Now I just have 
to figure out how to enable unicast in cman.

--
Eric Robinson


From: Eric Robinson [mailto:eric.robin...@psmnv.com]
Sent: Wednesday, August 23, 2017 3:16 PM
To: Cluster Labs - All topics related to open-source clustering welcomed 

Subject: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft 
Azure?

I created two nodes on Micrsoft Azure, but I can't get them to join a cluster. 
Any thoughts?

OS: RHEL 6.9
Corosync version: 1.4.7-5.el6.x86_64
Node names: ha001a (172.28.0.4/23), ha001b (172.28.0.5/23)

The nodes are on the same subnet and can ping and ssh to each other just fine 
by either host name or IP address.

I have configured corosync to use unicast.

corosync-cfgtool looks fine...

[root@ha001b corosync]# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
id  = 172.28.0.5
status  = ring 0 active with no faults

...but corosync-objctl only shows the local node...

[root@ha001b corosync]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.2.join_count=1
runtime.totem.pg.mrp.srp.members.2.status=joined

...pcs status shows...

Cluster name: ha001
Stack: cman
Current DC: ha001b (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:04:33 2017  Last change: Wed Aug 23 
17:51:07 2017 by root via cibadmin on ha001b

2 nodes and 0 resources configured

Online: [ ha001b ]
OFFLINE: [ ha001a ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...it shows the opposite on the other node...

[root@ha001a ~]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.1.join_count=1
runtime.totem.pg.mrp.srp.members.1.status=joined
[root@ha001a ~]# pcs status
Cluster name: ha001
Stack: cman
Current DC: ha001a (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:06:04 2017  Last change: Wed Aug 23 
17:51:03 2017 by root via cibadmin on ha001a

2 nodes and 0 resources configured

Online: [ ha001a ]
OFFLINE: [ ha001b ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...here is my corosync.conf...

compatibility: whitetank

totem {
version: 2
secauth: off
interface {
member {
memberaddr: 172.28.0.4
}
member {
memberaddr: 172.28.0.5
}
ringnumber: 0
bindnetaddr: 172.28.0.0
mcastport: 5405
ttl: 1
}
transport: udpu
}

logging {
fileline: off
to_logfile: yes
to_syslog: yes
logfile: /var/log/cluster/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
}

I used tcpdump and I see a lot of traffic between them on port 2224, but 
nothing else.

Is there an issue because the bindinetaddr is 172.28.0.0 but the members have a 
/23 mask?

--
Eric Robinson

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

2017-08-23 Thread Eric Robinson

I have a BIG correction.

If you follow the instructions titled, "Pacemaker 1.1 for Corosync 2.x," and 
NOT the ones entitled, "Pacemaker 1.1 for CMAN or Corosync 1.x," guess what? It 
installs cman anyway, and you spend a couple of days wondering why none of your 
changes to corosync.conf seem to be working.

--
Eric Robinson

-Original Message-
From: Jan Friesse [mailto:jfrie...@redhat.com] 
Sent: Tuesday, August 22, 2017 11:52 PM
To: Cluster Labs - All topics related to open-source clustering welcomed 
; kgail...@redhat.com
Subject: Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

> Thanks for the reply. Yes, it's a bit confusing. I did end up using the 
> documentation for Corosync 2.X since that seemed newer, but it also assumed 
> CentOS/RHEL7 and systemd-based commands. It also incorporates cman, pcsd, 
> psmisc, and policycoreutils-pythonwhich, which are all new to me. If there is 
> anything I can do to assist with getting the documentation cleaned up, I'd be 
> more than glad to help.

Just a small correction.

Documentation shouldn't incorporate cman. Cman was used with corosync 1.x as a 
configuration layer and (more important) quorum provider. With Corosync 2.x 
quorum provider is already in corosync so no need for cman.



>
> --
> Eric Robinson
>
> -Original Message-
> From: Ken Gaillot [mailto:kgail...@redhat.com]
> Sent: Tuesday, August 22, 2017 2:08 PM
> To: Cluster Labs - All topics related to open-source clustering 
> welcomed 
> Subject: Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?
>
> On Tue, 2017-08-22 at 19:40 +, Eric Robinson wrote:
>> The documentation located here…
>>
>>
>>
>> http://clusterlabs.org/doc/
>>
>>
>>
>> …is confusing because it offers two combinations:
>>
>>
>>
>> Pacemaker 1.0 for Corosync 1.x
>>
>> Pacemaker 1.1 for Corosync 2.x
>>
>>
>>
>> According to the documentation, if you use Corosync 1.x you need 
>> Pacemaker 1.0, but if you use Corosync 2.x then you need Pacemaker 
>> 1.1.
>>
>>
>>
>> However, on my Centos 6.9 system, when I do ‘yum install pacemaker 
>> corosync” I get the following versions:
>>
>>
>>
>> pacemaker-1.1.15-5.el6.x86_64
>>
>> corosync-1.4.7-5.el6.x86_64
>>
>>
>>
>> What’s the correct answer? Does Pacemaker 1.1.15 work with Corosync 
>> 1.4.7? If so, is the documentation at ClusterLabs misleading?
>>
>>
>>
>> --
>> Eric Robinson
>
> The page actually offers a third option ... "Pacemaker 1.1 for CMAN or 
> Corosync 1.x". That's the configuration used by CentOS 6.
>
> However, that's still a bit misleading; the documentation set for "Pacemaker 
> 1.1 for Corosync 2.x" is the only one that is updated, and it's mostly 
> independent of the underlying layer, so you should prefer that set.
>
> I plan to reorganize that page in the coming months, so I'll try to make it 
> clearer.
>
> --
> Ken Gaillot 
>
>
>
>
>
> ___
> Users mailing list: Users@clusterlabs.org 
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> ___
> Users mailing list: Users@clusterlabs.org 
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>


___
Users mailing list: Users@clusterlabs.org 
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org Getting started: 
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

2017-08-23 Thread Eric Robinson

I created two nodes on Micrsoft Azure, but I can't get them to join a cluster. 
Any thoughts?

OS: RHEL 6.9
Corosync version: 1.4.7-5.el6.x86_64
Node names: ha001a (172.28.0.4/23), ha001b (172.28.0.5/23)

The nodes are on the same subnet and can ping and ssh to each other just fine 
by either host name or IP address.

I have configured corosync to use unicast.

corosync-cfgtool looks fine...

[root@ha001b corosync]# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
id  = 172.28.0.5
status  = ring 0 active with no faults

...but corosync-objctl only shows the local node...

[root@ha001b corosync]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.2.join_count=1
runtime.totem.pg.mrp.srp.members.2.status=joined

...pcs status shows...

Cluster name: ha001
Stack: cman
Current DC: ha001b (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:04:33 2017  Last change: Wed Aug 23 
17:51:07 2017 by root via cibadmin on ha001b

2 nodes and 0 resources configured

Online: [ ha001b ]
OFFLINE: [ ha001a ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...it shows the opposite on the other node...

[root@ha001a ~]# corosync-objctl |grep join
totem.join=60
runtime.totem.pg.mrp.srp.memb_join_tx=1
runtime.totem.pg.mrp.srp.memb_join_rx=1
runtime.totem.pg.mrp.srp.members.1.join_count=1
runtime.totem.pg.mrp.srp.members.1.status=joined
[root@ha001a ~]# pcs status
Cluster name: ha001
Stack: cman
Current DC: ha001a (version 1.1.15-5.el6-e174ec8) - partition with quorum
Last updated: Wed Aug 23 18:06:04 2017  Last change: Wed Aug 23 
17:51:03 2017 by root via cibadmin on ha001a

2 nodes and 0 resources configured

Online: [ ha001a ]
OFFLINE: [ ha001b ]

No resources


Daemon Status:
  cman: active/disabled
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled

...here is my corosync.conf...

compatibility: whitetank

totem {
version: 2
secauth: off
interface {
member {
memberaddr: 172.28.0.4
}
member {
memberaddr: 172.28.0.5
}
ringnumber: 0
bindnetaddr: 172.28.0.0
mcastport: 5405
ttl: 1
}
transport: udpu
}

logging {
fileline: off
to_logfile: yes
to_syslog: yes
logfile: /var/log/cluster/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
}

I used tcpdump and I see a lot of traffic between them on port 2224, but 
nothing else.

Is there an issue because the bindinetaddr is 172.28.0.0 but the members have a 
/23 mask?

--
Eric Robinson

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

2017-08-23 Thread Jan Friesse


Thanks for the reply. Yes, it's a bit confusing. I did end up using the 
documentation for Corosync 2.X since that seemed newer, but it also assumed 
CentOS/RHEL7 and systemd-based commands. It also incorporates cman, pcsd, 
psmisc, and policycoreutils-pythonwhich, which are all new to me. If there is 
anything I can do to assist with getting the documentation cleaned up, I'd be 
more than glad to help.


Just a small correction.

Documentation shouldn't incorporate cman. Cman was used with corosync 
1.x as a configuration layer and (more important) quorum provider. With 
Corosync 2.x quorum provider is already in corosync so no need for cman.






--
Eric Robinson

-Original Message-
From: Ken Gaillot [mailto:kgail...@redhat.com]
Sent: Tuesday, August 22, 2017 2:08 PM
To: Cluster Labs - All topics related to open-source clustering welcomed 

Subject: Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

On Tue, 2017-08-22 at 19:40 +, Eric Robinson wrote:

The documentation located here…



http://clusterlabs.org/doc/



…is confusing because it offers two combinations:



Pacemaker 1.0 for Corosync 1.x

Pacemaker 1.1 for Corosync 2.x



According to the documentation, if you use Corosync 1.x you need
Pacemaker 1.0, but if you use Corosync 2.x then you need Pacemaker
1.1.



However, on my Centos 6.9 system, when I do ‘yum install pacemaker
corosync” I get the following versions:



pacemaker-1.1.15-5.el6.x86_64

corosync-1.4.7-5.el6.x86_64



What’s the correct answer? Does Pacemaker 1.1.15 work with Corosync
1.4.7? If so, is the documentation at ClusterLabs misleading?



--
Eric Robinson


The page actually offers a third option ... "Pacemaker 1.1 for CMAN or Corosync 
1.x". That's the configuration used by CentOS 6.

However, that's still a bit misleading; the documentation set for "Pacemaker 1.1 for 
Corosync 2.x" is the only one that is updated, and it's mostly independent of the 
underlying layer, so you should prefer that set.

I plan to reorganize that page in the coming months, so I'll try to make it 
clearer.

--
Ken Gaillot 





___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org




___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

Re: [ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

[ClusterLabs] Is there a Trick to Making Corosync Work on Microsoft Azure?

Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

5 matches

Site Navigation

Mail list logo

Footer information