From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fw: some fence_virsh, fene_apc patches for RHEL6 backports
Date: Thu, 19 Dec 2013 14:13:14 +0100 [thread overview]
Message-ID: <52B2F0EA.5010609@redhat.com> (raw)
In-Reply-To: <52B1A63D.40203@mirantis.com>
On 12/18/2013 02:42 PM, Bogdan Dobrelya wrote:
>> Based on your patch, I have sent a new patch to cluster-devel@ ; the
>> main difference is that patch is based on current version (as there
>> were several changes vs RHEL6). The other difference is that I have
>> removed obtaining status of plug from list function because it can
>> not work easily with UUID. Instead we call directly 'virsh domstate'
>> ; on older systems there can be a problem with 'virsh --uuid --all'
>> because '--uuid' is relatively new (yes, supported in RHEL6+) so I
>> did not use this feature.
> Hello. I believe, the device opt for "uuid" should be added as well
> (see patch in attachment). Correct me, If I'm wrong...
Hi,
The 'uuid' is detected automatically (via standard python uuid library)
so for user it enough to just enter it as --plug/-n. The
options["--uuid"] is filled automatically in fencing library if uuid is
detected. The same approach is used also in fence_vmware_soap.
I know that documentation is the weak point and if everything will go as
planned, I should spend most of the January by writing first drafts.
m,
next prev parent reply other threads:[~2013-12-19 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52A74740.8020904@redhat.com>
[not found] ` <52A82671.1000604@mirantis.com>
2013-12-11 9:28 ` [Cluster-devel] Fwd: some fence_virsh, fene_apc patches for RHEL6 backports Bogdan Dobrelya
2013-12-16 15:14 ` [Cluster-devel] Fw: " Marek Grac
2013-12-16 16:10 ` Bogdan Dobrelya
2013-12-19 13:31 ` [Cluster-devel] Fence agent for Tripplite PDU Marek Grac
2013-12-24 13:36 ` Bogdan Dobrelya
2014-01-06 13:01 ` Marek Grac
2013-12-18 13:42 ` [Cluster-devel] Fw: some fence_virsh, fene_apc patches for RHEL6 backports Bogdan Dobrelya
2013-12-19 13:13 ` Marek Grac [this message]
2013-12-24 13:23 ` Bogdan Dobrelya
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=52B2F0EA.5010609@redhat.com \
--to=mgrac@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).