From: Digimer <linux@alteeve.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] new to cLVM - some principal questions
Date: Sun, 04 Dec 2011 15:44:47 -0500 [thread overview]
Message-ID: <4EDBDBBF.2000006@alteeve.com> (raw)
In-Reply-To: <15785B7E063D464C86DD482FCAE4EBA5015FF83D6CCD@XCH11.scidom.de>
On 12/04/2011 01:58 PM, Lentes, Bernd wrote:
>
> Some more questions:
> - Is it necessary to have cLVM running as a resource in the cluster ?
No, so long as it is running at all, it's fine. I do recommend it
though, as you can make anything using clvmd dependent on it having
started properly.
> - And is it possible having the vm's running on different nodes, not all on one (because of load balancing) ?
> Remember that i want to run the vm's in bare lv's, without a filesystem. The lv's reside on a SAN.
That's what I do. Mount the same iSCSI target on all VM nodes, then on
one node set it up as a PV and then a clustered VG. You will see the new
PV and VG on all the other nodes in the cluster. You can then create
LVs, setup VMs on them and move the VMs around the nodes using live
migration.
--
Digimer
E-Mail: digimer@alteeve.com
Freenode handle: digimer
Papers and Projects: http://alteeve.com
Node Assassin: http://nodeassassin.org
"omg my singularity battery is dead again.
stupid hawking radiation." - epitron
next prev parent reply other threads:[~2011-12-04 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 19:22 [linux-lvm] new to cLVM - some principal questions Lentes, Bernd
2011-11-22 19:32 ` Digimer
2011-11-23 15:35 ` Lentes, Bernd
2011-11-23 18:20 ` Digimer
2011-11-24 16:32 ` Lentes, Bernd
2011-11-24 16:46 ` Digimer
2011-11-25 17:49 ` Lentes, Bernd
2011-11-25 18:10 ` Digimer
2011-12-04 18:58 ` Lentes, Bernd
2011-12-04 20:44 ` Digimer [this message]
2012-02-09 16:20 ` Lentes, Bernd
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=4EDBDBBF.2000006@alteeve.com \
--to=linux@alteeve.com \
--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 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).