qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: aliguori@us.ibm.com, sheepdog@lists.wpkg.org,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	fujita.tomonori@lab.ntt.co.jp, avi@redhat.com,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU
Date: Wed, 12 May 2010 13:38:02 +0200	[thread overview]
Message-ID: <4BEA931A.6040309@redhat.com> (raw)
In-Reply-To: <1273661213-19611-1-git-send-email-morita.kazutaka@lab.ntt.co.jp>

Am 12.05.2010 12:46, schrieb MORITA Kazutaka:
> Hi all,
> 
> This patch adds a block driver for Sheepdog distributed storage
> system.  Please consider for inclusion.
> 
> Sheepdog is a distributed storage system for QEMU.  It provides highly
> available block level storage volumes to VMs like Amazon EBS.
> 
> Sheepdog features are:
> - No node in the cluster is special (no metadata node, no control
>   node, etc)
> - Linear scalability in performance and capacity
> - No single point of failure
> - Autonomous management (zero configuration)
> - Useful volume management support such as snapshot and cloning
> - Thin provisioning
> - Autonomous load balancing
> 
> The more details are available at the project site [1] and my previous
> post about sheepdog [2].
> 
> We have implemented the essential part of sheepdog features, and
> believe the API between Sheepdog and QEMU is finalized.
> 
> Any comments or suggestions would be greatly appreciated.

These patches don't apply, neither on git master nor on the block
branch. Please rebase them on git://repo.or.cz/qemu/kevin.git block for
the next submission.

I'll have a closer look at your code later, but one thing I noticed is
that the new block driver is something in between a protocol and a
format driver (just like vvfat, which should stop doing so, too). I
think it ought to be a real protocol with the raw format driver on top
(or any other format - I don't see a reason why this should be
restricted to raw).

The one thing that is unusual about it as a protocol driver is that it
supports snapshots. However, while it is the first one, supporting
snapshots in protocols is a thing that could be generally useful to
support (for example thinking of a LVM protocol, which was discussed in
the past).

So in block.c we could check if the format driver supports snapshots,
and if it doesn't we try again with the underlying protocol. Not sure
yet what we would do when both format and protocol do support snapshots
(qcow2 on sheepdog/LVM/...), but that's a detail.

Kevin

  parent reply	other threads:[~2010-05-12 11:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 10:46 [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-12 14:01   ` Christoph Hellwig
2010-05-12 19:50     ` MORITA Kazutaka
2010-05-12 14:28   ` [Qemu-devel] " Avi Kivity
2010-05-12 20:16     ` MORITA Kazutaka
2010-05-13  2:34       ` MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 2/2] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-12 11:38 ` Kevin Wolf [this message]
2010-05-12 19:46   ` [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-13 14:03     ` MORITA Kazutaka
2010-05-14  8:32       ` Kevin Wolf
2010-05-14  9:54         ` MORITA Kazutaka
2010-05-14 10:05           ` Kevin Wolf
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 0/3] " MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 " MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-17 11:08     ` Kevin Wolf
2010-05-17 12:19       ` [Qemu-devel] " MORITA Kazutaka
2010-05-17 12:20         ` Kevin Wolf
2010-05-17 13:03           ` MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-14 12:55   ` [Qemu-devel] " Kevin Wolf
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 11:08   ` [Qemu-devel] " Kevin Wolf
2010-05-17 10:34     ` 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=4BEA931A.6040309@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.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).