From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/2] indirectly simplify cluster.rng
Date: Thu, 28 Feb 2013 22:37:06 +0100 [thread overview]
Message-ID: <1362087428-566-1-git-send-email-jpokorny@redhat.com> (raw)
Hello,
I've noticed how stale some parts in resulting cluster.rng schema are.
Following patches aim to solve the FA part; first we enable native
metadata generating for Node Assassin agent, then nothing prevents us
to drop static non-generated FA part of schema completely.
Jan Pokorn? (2):
Node Assassin: add support for metadata
lib: remove static metadata from fence.rng.head
fence/agents/lib/fence.rng.head | 129 -----------------------------
fence/agents/node_assassin/fence_na.lib.in | 50 +++++++++++
fence/agents/node_assassin/fence_na.pl | 9 +-
3 files changed, 58 insertions(+), 130 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-02-28 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 21:37 Jan Pokorný [this message]
2013-02-28 21:37 ` [Cluster-devel] [PATCH 1/2] Node Assassin: add support for metadata Jan Pokorný
2013-02-28 21:37 ` [Cluster-devel] [PATCH 2/2] lib: remove static metadata from fence.rng.head Jan Pokorný
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=1362087428-566-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).