public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: David Teigland <teigland@fedoraproject.org>
To: cluster-cvs-relay@redhat.com
Subject: cluster: STABLE3 - cluster.rng: cluster_id and nodeid
Date: Mon, 27 Jul 2009 21:23:00 -0000	[thread overview]
Message-ID: <20090727212314.30537120307@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=5d55508f14db4363cd78759e6988a915fed1a417
Commit:        5d55508f14db4363cd78759e6988a915fed1a417
Parent:        4be2a85079cd05df9dd07b555f88ad0184d9f7a5
Author:        David Teigland <teigland@redhat.com>
AuthorDate:    Mon Jul 27 16:14:10 2009 -0500
Committer:     David Teigland <teigland@redhat.com>
CommitterDate: Mon Jul 27 16:14:10 2009 -0500

cluster.rng: cluster_id and nodeid

add cluster_id, fix up nodeid

Signed-off-by: David Teigland <teigland@redhat.com>
---
 config/tools/xml/cluster.rng |   21 +++++++--------------
 1 files changed, 7 insertions(+), 14 deletions(-)

diff --git a/config/tools/xml/cluster.rng b/config/tools/xml/cluster.rng
index 1fb1b65..7954ab0 100644
--- a/config/tools/xml/cluster.rng
+++ b/config/tools/xml/cluster.rng
@@ -104,6 +104,11 @@ To validate your cluster.conf against this schema, run:
      </attribute>
     </optional>
     <optional>
+     <attribute name="cluster_id">
+      <data type="nonNegativeInteger"/>
+     </attribute>
+    </optional>
+    <optional>
      <attribute name="broadcast">
       <data type="nonNegativeInteger"/>
      </attribute>
@@ -149,19 +154,9 @@ To validate your cluster.conf against this schema, run:
 	   <data type="positiveInteger"/>
 	 </attribute>
        </optional>
-       <!--FIXME: Verify if the nodeid attribute is optional. I think
-       it is required for RHEL 5. The sources.redhat.com site states
-       that the attribute is required; however, that must mean that a
-       cluster.conf file must have a nodeid for each node. The value
-       is automatically assigned a value; however, you can change its
-       value.-->
        <optional>
-	 <attribute name="nodeid" rha:description="Each node is assigned
-             a unique integer value as its node ID. You can change a
-             node's nodeid; hoever, it must be a unique integer value
-             in the cluster. A node's application to join a cluster may
-             be rejected if you try to set the nodeid to one that is
-             already used in a cluster." rha:sample="1">
+	 <attribute name="nodeid" rha:description="Each node requires
+             a unique integer value as its node ID." rha:sample="1">
 	   <data type="positiveInteger"/>
 	 </attribute>
        </optional>
@@ -1220,8 +1215,6 @@ block before determining success or failure.
        fencing of nodes with no fence methods defined." rha:default="0"
        rha:sample="1"/>
    </optional>
-   -->
-
   </element>
  </optional>
 


                 reply	other threads:[~2009-07-27 21:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090727212314.30537120307@lists.fedorahosted.org \
    --to=teigland@fedoraproject.org \
    --cc=cluster-cvs-relay@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 read-only IMAP folder(s) and NNTP newsgroup(s).