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: comments around fence devices
Date: Tue, 28 Jul 2009 19:36:00 -0000	[thread overview]
Message-ID: <20090728193605.BF56012022C@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=ac9ba8add8ef6fdacdaf766026741e42101ba11b
Commit:        ac9ba8add8ef6fdacdaf766026741e42101ba11b
Parent:        25dd066e31c42b188fbd686f3b85358d0435db9e
Author:        David Teigland <teigland@redhat.com>
AuthorDate:    Tue Jul 28 14:26:46 2009 -0500
Committer:     David Teigland <teigland@redhat.com>
CommitterDate: Tue Jul 28 14:26:46 2009 -0500

cluster.rng: comments around fence devices

trying to understand the structure

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

diff --git a/config/tools/xml/cluster.rng b/config/tools/xml/cluster.rng
index ee54f04..2936cf7 100644
--- a/config/tools/xml/cluster.rng
+++ b/config/tools/xml/cluster.rng
@@ -672,6 +672,9 @@ To validate your cluster.conf against this schema, run:
          be used." rha:sample="fence_apc"/>
      <optional>
       <choice>
+       <!-- begin specific fence devices -->
+
+       <!-- begin non-generated device definitions -->
        <!-- RPS10 -->
        <group rha:description="RPS10 Serial Switch" >
         <attribute name="device" rha:description="The device the switch
@@ -761,8 +764,9 @@ To validate your cluster.conf against this schema, run:
        <group>
         <attribute name="rpowerpath" rha:description="" rha:sample=""/>
        </group>
+       <!-- end non-generated device definitions -->
 
-<!-- autogenerated ones -->
+       <!-- begin auto-generated device definitions -->
       <!-- fence_alom -->
       <group>
         <optional>
@@ -1097,15 +1101,15 @@ To validate your cluster.conf against this schema, run:
           <attribute name="timeout"/>
         </optional>
       </group>
+       <!-- end auto-generated device definitions -->
 
-<!-- end autogenerated -->
-
-       <!-- manual -->
        <group>
         <optional>
          <empty/>
         </optional>
        </group>
+
+       <!-- end specific fence devices -->
       </choice>
      </optional>
     </element>
@@ -2301,7 +2305,7 @@ To validate your cluster.conf against this schema, run:
 <!-- End autogenerated resources definitions -->
 <!--End of resource definitions-->
 
-<!--Beginning of fence definitions-->
+<!-- begin node fence definitions -->
 
  <define name="FENCE">
   <element name="fence" rha:description="The fence element specifies how
@@ -2338,8 +2342,9 @@ To validate your cluster.conf against this schema, run:
     <data type="IDREF"/>
    </attribute>
    <choice>
+      <!-- begin node fence specific devices -->
 
-<!-- autogenerated -->
+      <!-- begin auto-generated device definitions -->
       <!-- fence_alom -->
       <group>
         <optional>
@@ -2662,8 +2667,9 @@ To validate your cluster.conf against this schema, run:
           <attribute name="timeout"/>
         </optional>
       </group>
+      <!-- end auto-generated device definitions -->
 
-
+      <!-- begin non-generated device definitions -->
         <!-- Brocade, Vixel, McData, SANBox2 -->
         <group>
          <attribute name="port"/>
@@ -2734,7 +2740,12 @@ To validate your cluster.conf against this schema, run:
           <attribute name="domain"/>
          </optional>
         </group>
-       </choice>
-      </element>
-     </define>
+      <!-- end non-generated device definitions -->
+
+   <!-- end node fence specific devices -->
+   </choice>
+  </element>
+ </define>
+<!-- end node fence definitions -->
+
 </grammar>


                 reply	other threads:[~2009-07-28 19:36 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=20090728193605.BF56012022C@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).