cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jan Friesse <jfriesse@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] config: drastically improve cman RRP configuration handling
Date: Thu, 01 Dec 2011 08:51:00 +0100	[thread overview]
Message-ID: <4ED731E4.2030303@redhat.com> (raw)
In-Reply-To: <1322657478-19020-1-git-send-email-fdinitto@redhat.com>

Patch looks good with one question.

Fabio M. Di Nitto wrote:
> From: "Fabio M. Di Nitto" <fdinitto@redhat.com>
> 
> - don't allow configuration of more than 2 rings
> - allow overrided of alternate mcast address and port via
>   envars
> - when using broadcast, set different ports on second ring.
>   this also required a substantial change in transport handling
> ...
> +		if (!strcmp(altmcast_name, mcast_name) &&
> +		    ((altportnum == portnum) || (altportnum == portnum - 1) || (portnum == altportnum - 1))) {
> +			sprintf(error_reason, "Alternate communication channel (mcast: %s ports: %d,%d) cannot use\n"
> +					      "same address and ports of primary channel (mcast: %s ports: %d,%d)",
> +					      altmcast_name, altportnum, altportnum - 1,
> +					      mcast_name, portnum, portnum - 1);

(altportnum == portnum - 1) || (portnum == altportnum - 1)) ->
(altportnum == portnum - 1) || (altportnum == portnum + 1)), but
corosync uses only port and port -1, so second condition seems to be
useless (on the other hand, it doesn't hurt anything).

> +			write_cman_pipe(error_reason);
> +			return -1;



  reply	other threads:[~2011-12-01  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 12:51 [Cluster-devel] [PATCH] config: drastically improve cman RRP configuration handling Fabio M. Di Nitto
2011-12-01  7:51 ` Jan Friesse [this message]
2011-12-01  8:43   ` Fabio M. Di Nitto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ED731E4.2030303@redhat.com \
    --to=jfriesse@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).