On 2011-07-29 23:09, Steven Dake wrote:
On 07/26/2011 08:28 PM, manish.gu...@ionidea.com wrote:
Thank you Steave,
We are currentely using corosync-1.2.1 and pacemaker 1.0.10
Can we use the same version of pacemaker with corosync-1.4
Yes, although redundant ring is not onwire
Ahoj Jan,
Thanks for reviewing. Please take a look at this followup patch to see if
the information in there is useful. If everything is OK for you, I'll fix up
my git tree again so you can pull later today.
Cheers,
Florian
___
Openais mailing list
file.
Signed-off-by: Florian Haas florian.h...@linbit.com
---
conf/corosync.conf.example | 16
1 files changed, 12 insertions(+), 4 deletions(-)
diff --git a/conf/corosync.conf.example b/conf/corosync.conf.example
index c849dba..ac1718f 100644
--- a/conf/corosync.conf.example
review on the list. Thanks to Dan Frincu and
Jan Friesse for their valuable feedback. A patch-by-patch summary and
diffstat are below, as usual.
Cheers,
Florian
Florian Haas (4):
corosync.conf.example: change bindnetaddr
corosync.conf.example: change mcastaddr
corosync.conf.example
Hello,
please consider the following patches to the example configuration
file. Many thanks to Dan Frincu for reviewing and pointing out two
factual errors:
* Corosync uses mcastport and mcastport-1, not mcastport and
mcastport+1 like the original patch set suggested.
* RFC 2365 specifies
It's nice to say people should read the man page. It's also naive to
assume that they always do. Include comments in the example config
file itself.
Signed-off-by: Florian Haas florian.h...@linbit.com
Reviewed-by: Dan Frincu dan.fri...@1and1.ro
---
conf/corosync.conf.example | 42
Change suggested mcastaddr to one in the 239.255.0.0/16
pseudo-subnet. Multicast addresses outside 239.x.x.x may be IANA
registered and can clash with other services present on the
network. Suggest an address defined as part of the multicast IPv4
Local Scope in RFC 2365.
Signed-off-by: Florian
Change the example configuration file so bindnetaddr has a value
that more obviously looks like a network address. So as not to have
people think they need to set an existing IP address here (and hence,
have non-identical corosync.conf files between nodes).
Signed-off-by: Florian Haas florian.h
On 2011-07-27 10:43, Lars Marowsky-Bree wrote:
On 2011-07-21T07:59:23, Steven Dake sd...@redhat.com wrote:
There is no fallback. You can specify one transport or the other.
Thinking a moment how to implement this type of feature, it could not be
reasonably implemented.
But the transport
Change the example configuration file so bindnetaddr has a value
that more obviously looks like a network address. So as not to have
people think they need to set an existing IP address here (and hence,
have non-identical corosync.conf files between nodes).
Signed-off-by: Florian Haas florian.h
-by: Florian Haas florian.h...@linbit.com
---
conf/corosync.conf.example |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/conf/corosync.conf.example b/conf/corosync.conf.example
index 5a8d195..cff8ec2 100644
--- a/conf/corosync.conf.example
+++ b/conf/corosync.conf.example
@@ -8,7
It's nice to say people should read the man page. It's also naive to
assume that they always do. Include comments in the example config
file itself.
Signed-off-by: Florian Haas florian.h...@linbit.com
---
conf/corosync.conf.example | 42 +-
1 files
On 2011-07-06 22:15, Steven Dake wrote:
On 07/06/2011 01:02 PM, Florian Haas wrote:
On 07/06/2011 03:52 PM, Steven Dake wrote:
From: Florian Haas florian.h...@linbit.com
Enable RDMA in RPM builds by default to maintain the previous behavior
(which always included --enable-rdma
On 2011-07-05 14:03, Fabio M. Di Nitto wrote:
I checked the changes in that branch and they are good to me.
I've rebased my repo against current upstream (after the RRP ring
recovery merge).
Cheers,
Florian
signature.asc
Description: OpenPGP digital signature
On 2011-07-06 15:49, Steven Dake wrote:
Florian,
I'll take improvements however I can get them, but sending patches to
the list is preferred that way multiple people can look at them.
Arguably that counts for github too, as my repo happens to be quite
public. :)
The way I generally do this
On 2011-07-06 15:59, Steven Dake wrote:
On 07/06/2011 06:56 AM, Florian Haas wrote:
On 2011-07-06 15:49, Steven Dake wrote:
Florian,
I'll take improvements however I can get them, but sending patches to
the list is preferred that way multiple people can look at them.
Arguably that counts
On 2011-07-06 16:07, Steven Dake wrote:
On 07/06/2011 06:52 AM, Steven Dake wrote:
From: Florian Haas florian.h...@linbit.com
Having to force {ibverbs,rdmacm}_{LIBS,CFLAGS} looks positively odd;
so this may warrant further review. However, they are definitely not
needed if building without
On 2011-07-06 16:08, Florian Haas wrote:
Hmmm. You can merge from my repo into yours, then use git rebase -i
base rev to edit commit messages and add your Reviewed-By lines. But
the downside of this is that this creates in place of my changesets it
creates new ones, and then I have to reset
On 07/06/2011 03:52 PM, Steven Dake wrote:
From: Florian Haas florian.h...@linbit.com
Enable RDMA in RPM builds by default to maintain the previous behavior
(which always included --enable-rdma in the %configure invocation).
Steve, seeing that you acked all the others, any objections
They are all small patches fixing minor issues related to RPM builds.
Thanks.
Cheers,
Florian
Florian Haas (4):
build: force LC_ALL=C correctly for dates
build: make RDMA support an RPM build conditional
build: set RDMA related _LIBS and _CFLAGS only if building with
RDMA support
Thanks Darren!
Thanks for the contribution! Can I suggest
- we move this discussion to the linux-ha-dev list (where most OCF RA
related discussions and reviews take place);
- you give the RA a makeover following the OCF RA developer's guide
On 12/13/2010 08:15 PM, Steven Dake wrote:
On 12/13/2010 12:08 AM, Florian Haas wrote:
On 12/07/2010 01:13 PM, Florian Haas wrote:
Honza, Steve,
do I understand correctly that this would trigger if, for example, a
user had configured an iptables rule that blocked UDP port 5405? And if
yes
On 12/07/2010 01:13 PM, Florian Haas wrote:
Honza, Steve,
do I understand correctly that this would trigger if, for example, a
user had configured an iptables rule that blocked UDP port 5405? And if
yes, would Corosync behave any differently when instead there is no
_physical_ link between
On 2010-11-22 11:29, Florian Götz wrote:
Hi everybody,
I´m new to cluster setups and set up a Webserver cluster with an Apache,
MySQL and DRBD for storage (2 Nodes).
I´ve put the primitives for ClusterIP, Apache, MySQL and the DRBD Filesystem
in a group.
Idea behind that was, if one of
On 2010-09-13 11:21, Chase Venters wrote:
On Monday 13 September 2010 3:45:50 am Florian Haas wrote:
I realize I may be asking for a lot, but is there any chance you could
rewrite your module to use SWIG, thereby making it more easily portable
to languages other than Perl?
I definitely see
Olivier,
that one definitely belongs on the drbd-user list. Please subscribe
there and repost. Thanks!
Cheers,
Florian
On 03/16/2010 09:40 PM, Olivier BATARD wrote:
Hi,
I'm trying to build an active passive cluster with drbd / corosync /
pacemaker on debian lenny.
I followed the doc
26 matches
Mail list logo
