From: Digimer <lists@alteeve.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 cluster aware
Date: Fri, 26 Aug 2016 01:08:11 -0400 [thread overview]
Message-ID: <415584cb-2e8f-ce85-260f-9b75aea51d6c@alteeve.ca> (raw)
In-Reply-To: <CAN2gjWSe+V9nEDWuR0nVtzUZEt2d5yYjy5cQxrPPjHNO9NSMwA@mail.gmail.com>
On 25/08/16 04:49 AM, su liu wrote:
> hi digimer , Thanks your replay explanation.
>
> My use case is:
>
> One admin node and some compute nodes, All the nodes shares a storage
> (eg. FCSAN).
> I create a vg on the shared storage， and the vg can be seen on all the
> nodes.
> The admin node's responsibility is to manage the logical volume it
> created, and the other compute node can attach these lvs to VM directly,
> not through admin node.
> Under the scene of LVM driver of OpenStack Cinder project, The lvm
> volumes are attached to VMs through Cinder node via ISCSI. So I want to
> make sure whether I can attach lvm volumes to VMs directly.
>
> To achieve this goal, Should I use the method you mentiond before?
>
> Thanks very much!
I can't speak to the cinder project, but as for "do something in LVM on
one node, see that everywhere", then yes, clvmd will do just that. Our
project uses clvmd backed LVs to provide raw storage to KVM VMs with
cluster-aware tools to manage the VMs, handle live migration, etc.
In short; look at the pacemaker project. Be sure to use fencing (always
needed, but extra important with shared storage). If you want to go into
more detail, we'll drift fairly far from LVM stuff, so I would recommend
joining the Clusterlabs users list and start by introducing yourself,
explain your goals and tell us what OS/version you are planning to run.
From there, we can help you work on a POC.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
next prev parent reply other threads:[~2016-08-26 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 8:49 [linux-lvm] lvm2 cluster aware su liu
2016-08-26 5:08 ` Digimer [this message]
2016-08-26 9:39 ` Lentes, Bernd
-- strict thread matches above, loose matches on Subject: below --
2016-08-26 6:35 su liu
2016-08-26 6:28 su liu
2016-08-26 15:53 ` David Teigland
2016-08-25 1:50 su liu
2016-08-25 7:37 ` Digimer
2016-08-25 15:59 ` David Teigland
2016-08-26 5:04 ` Digimer
2016-08-26 14:56 ` David Teigland
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=415584cb-2e8f-ce85-260f-9b75aea51d6c@alteeve.ca \
--to=lists@alteeve.ca \
--cc=linux-lvm@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 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.