From: Bogdan Dobrelya <bdobrelia@mirantis.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fw: some fence_virsh, fene_apc patches for RHEL6 backports
Date: Wed, 18 Dec 2013 15:42:21 +0200 [thread overview]
Message-ID: <52B1A63D.40203@mirantis.com> (raw)
In-Reply-To: <52AF18ED.8090906@redhat.com>
On 12/16/2013 05:14 PM, Marek Grac wrote:
> Hi,
>
> Thanks for a patches,
>
> On 12/11/2013 09:46 AM, Bogdan Dobrelya wrote:
>> Hello.
>> Description for suggested patches:
>>
>>> fence_virsh: I believe the uuid support is a good idea, cuz every
>>> spawned VM would have an UUID in its dmidecode, equal to its `virsh
>>> domuuid`. Thus, to fence it, we should not either know the domain name,
>>> nor query libvirt to find it out.
>>>
> 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...
>
>>> fence_apc: As I can see from my research activities, fence_apc is quite
>>> a vendor specific agent, thus it would require custom options for
>>> command-prompt as well as ssh-options.
> --ssh-options are already available in upstream
>
> m,
--
Best regards,
Bogdan Dobrelya,
Researcher TechLead, Mirantis, Inc.
+38 (066) 051 07 53
Skype bogdando_at_yahoo.com
Irc #bogdando
38, Lenina ave.
Kharkov, Ukraine
www.mirantis.com
www.mirantis.ru
bdobrelia at mirantis.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-missed-uuid-device-opt.patch
Type: text/x-patch
Size: 883 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20131218/3b56bb3f/attachment.bin>
next prev parent reply other threads:[~2013-12-18 13:42 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 ` Bogdan Dobrelya [this message]
2013-12-19 13:13 ` [Cluster-devel] Fw: some fence_virsh, fene_apc patches for RHEL6 backports Marek Grac
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=52B1A63D.40203@mirantis.com \
--to=bdobrelia@mirantis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.