From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Pokorný Date: Thu, 21 Nov 2013 01:41:20 +0100 Subject: [Cluster-devel] [cluster.git][v2][PATCH] rng: enforce unfence action to always be "on" ("enable") convention In-Reply-To: <1384555575-9513-1-git-send-email-jpokorny@redhat.com> References: <1384555575-9513-1-git-send-email-jpokorny@redhat.com> Message-ID: <1384994480-13513-1-git-send-email-jpokorny@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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? --- 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: + + + + @@ -1105,20 +1109,45 @@ To validate your cluster.conf against this schema, run: - + + device used for fencing a node. fenced(8)"> + + + + + + + + + + + + + + + + + + + enable + on + + + -- 1.8.1.4