From: David Teigland <teigland@redhat.com>
To: Bram Klein Gunnewiek <bram@shockmedia.nl>,
Zdenek Kabelac <zkabelac@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshots on clustered LVM
Date: Wed, 26 Aug 2015 09:17:35 -0500 [thread overview]
Message-ID: <20150826141735.GA24955@redhat.com> (raw)
In-Reply-To: <55DDB49D.7060501@redhat.com>
On Wed, Aug 26, 2015 at 02:44:13PM +0200, Zdenek Kabelac wrote:
> Also there are already existing solutions for what you describe, but
> I assume you prefer your own home-brewed solution - but it's long
> journey ahead of you...
RHEV/ovirt is an existing solution that uses lvm on multiple hosts and
does live migration. They have quite a bit of very specialized lvm code
to do that right -- not typical lvm usage at all.
next prev parent reply other threads:[~2015-08-26 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 10:09 [linux-lvm] Snapshots on clustered LVM Bram Klein Gunnewiek
2015-08-26 10:59 ` Zdenek Kabelac
2015-08-26 12:22 ` Bram Klein Gunnewiek
2015-08-26 12:44 ` Zdenek Kabelac
2015-08-26 14:17 ` David Teigland [this message]
2015-08-26 16:23 ` Digimer
2015-08-26 16:35 ` Digimer
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=20150826141735.GA24955@redhat.com \
--to=teigland@redhat.com \
--cc=bram@shockmedia.nl \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@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).