From: Avi Kivity <avi@redhat.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [ANNOUNCE] Sheepdog: Distributed Storage System for KVM
Date: Thu, 22 Oct 2009 17:30:07 +0200 [thread overview]
Message-ID: <4AE07A7F.8000002@redhat.com> (raw)
In-Reply-To: <4ADE988B.2070303@lab.ntt.co.jp>
On 10/21/2009 07:13 AM, MORITA Kazutaka wrote:
> Hi everyone,
>
> Sheepdog is a distributed storage system for KVM/QEMU. It provides
> highly available block level storage volumes to VMs like Amazon EBS.
> Sheepdog supports advanced volume management features such as snapshot,
> cloning, and thin provisioning. Sheepdog runs on several tens or hundreds
> of nodes, and the architecture is fully symmetric; there is no central
> node such as a meta-data server.
Very interesting! From a very brief look at the code, it looks like the
sheepdog block format driver is a network client that is able to access
highly available images, yes?
If so, is it reasonable to compare this to a cluster file system setup
(like GFS) with images as files on this filesystem? The difference
would be that clustering is implemented in userspace in sheepdog, but in
the kernel for a clustering filesystem.
How is load balancing implemented? Can you move an image transparently
while a guest is running? Will an image be moved closer to its guest?
Can you stripe an image across nodes?
Do you support multiple guests accessing the same image?
What about fault tolerance - storing an image redundantly on multiple nodes?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-22 15:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 5:13 [Qemu-devel] [ANNOUNCE] Sheepdog: Distributed Storage System for KVM MORITA Kazutaka
2009-10-21 8:28 ` [Qemu-devel] " Nikolai K. Bochev
2009-10-21 8:45 ` Nikolai K. Bochev
2009-10-23 9:59 ` MORITA Kazutaka
2009-10-21 9:08 ` [Qemu-devel] " Dietmar Maurer
2009-10-23 10:06 ` [Qemu-devel] " MORITA Kazutaka
2009-10-23 10:17 ` Chris Webb
2009-10-23 10:26 ` Chris Webb
2009-10-23 11:10 ` [Qemu-devel] " Dietmar Maurer
2009-10-23 11:45 ` Dietmar Maurer
2009-10-22 15:30 ` Avi Kivity [this message]
2009-10-22 16:28 ` [Qemu-devel] " Anthony Liguori
2009-10-22 22:09 ` Alexander Graf
2009-10-23 10:41 ` MORITA Kazutaka
2009-10-23 11:10 ` Alexander Graf
2009-10-23 16:17 ` MORITA Kazutaka
2009-10-23 14:14 ` Javier Guerra
2009-10-23 14:58 ` Chris Webb
2009-10-23 15:10 ` Javier Guerra
2009-10-23 17:05 ` Tomasz Chmielewski
2009-10-25 8:44 ` Dietmar Maurer
2009-10-25 10:55 ` Tomasz Chmielewski
2009-10-23 15:40 ` FUJITA Tomonori
2009-10-25 5:36 ` Avi Kivity
2009-10-25 8:51 ` [Qemu-devel] " Dietmar Maurer
2009-10-26 6:53 ` [Qemu-devel] " MORITA Kazutaka
2009-10-22 18:46 ` Avishay Traeger
2009-10-23 11:22 ` [Qemu-devel] " Dietmar Maurer
2009-10-23 19:39 ` [Qemu-devel] " MORITA Kazutaka
2009-10-23 19:45 ` Javier Guerra
2009-10-24 2:49 ` MORITA Kazutaka
2009-10-28 3:53 ` [Qemu-devel] " MORITA Kazutaka
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=4AE07A7F.8000002@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
/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).