From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [cluster.git][v2][PATCH] rng: enforce unfence action to always be "on" ("enable") convention
Date: Thu, 21 Nov 2013 01:41:20 +0100 [thread overview]
Message-ID: <1384994480-13513-1-git-send-email-jpokorny@redhat.com> (raw)
In-Reply-To: <1384555575-9513-1-git-send-email-jpokorny@redhat.com>
There is a silent agreement on this probably "since beginning" already
(cf. [1]). Enforce it to move a boundary of what it explicitly wrong
a bit futher. As per Marek, "enable" should be nominally supported
as well.
Counterpart changeset for fence-agents (relevant branch) is also
proposed [2].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=865161#c17
[2] https://www.redhat.com/archives/cluster-devel/2013-November/msg00062.html
Signed-off-by: Jan Pokorn? <jpokorny@redhat.com>
---
config/tools/xml/cluster.rng.in.head | 33 +++++++++++++++++++++++++++++++--
1 file changed, 31 insertions(+), 2 deletions(-)
diff --git a/config/tools/xml/cluster.rng.in.head b/config/tools/xml/cluster.rng.in.head
index 003ceaf..86f384f 100644
--- a/config/tools/xml/cluster.rng.in.head
+++ b/config/tools/xml/cluster.rng.in.head
@@ -828,6 +828,10 @@ To validate your cluster.conf against this schema, run:
<attribute name="agent" rha:description="The fence agent to be
used. fenced(8)"/>
+ <optional>
+ <attribute name="action" rha:description="Fencing (Unfencing) Action"/>
+ </optional>
+
<ref name="FENCEDEVICEOPTIONS"/>
</element>
@@ -1105,20 +1109,45 @@ To validate your cluster.conf against this schema, run:
<element name="unfence" rha:description="Contains devices for unfencing
the node. fence_node(8)">
<zeroOrMore>
- <ref name="DEVICE"/>
+ <ref name="UNFENCEDEVICE"/>
</zeroOrMore>
</element>
</define>
<define name="DEVICE">
<element name="device" rha:description="Defines the properties of a
- device used for fencing or unfencing a node. fenced(8)">
+ device used for fencing a node. fenced(8)">
+
+ <attribute name="name" rha:description="The name of a fencedevice
+ defined in the fencedevices section. fenced(8)">
+ <data type="IDREF"/>
+ </attribute>
+
+ <optional>
+ <attribute name="action" rha:description="Fencing Action"/>
+ </optional>
+
+ <ref name="FENCEDEVICEOPTIONS"/>
+
+ </element>
+ </define>
+
+ <define name="UNFENCEDEVICE">
+ <element name="device" rha:description="Defines the properties of a
+ device used for unfencing a node. fenced(8)">
<attribute name="name" rha:description="The name of a fencedevice
defined in the fencedevices section. fenced(8)">
<data type="IDREF"/>
</attribute>
+ <attribute name="action" rha:description="Unfencing Action">
+ <choice>
+ <value>enable</value>
+ <value>on</value>
+ </choice>
+ </attribute>
+
<ref name="FENCEDEVICEOPTIONS"/>
</element>
--
1.8.1.4
prev parent reply other threads:[~2013-11-21 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 22:46 [Cluster-devel] [cluster.git][PATCH] rng: enforce unfence action to always be "on" convention Jan Pokorný
2013-11-15 22:52 ` [Cluster-devel] [fence-agents.git][PATCH] rng: enforce unfence action to always be "on" convention (FA part) Jan Pokorný
2013-11-21 0:41 ` Jan Pokorný [this message]
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=1384994480-13513-1-git-send-email-jpokorny@redhat.com \
--to=jpokorny@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).