qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: qemu-devel@nongnu.org, linux-fsdevel@vger.kernel.org,
	kvm@vger.kernel.org, morita.kazutaka@lab.ntt.co.jp,
	javier@guerrag.com
Subject: [Qemu-devel] Re: [ANNOUNCE] Sheepdog: Distributed Storage System for KVM
Date: Sun, 25 Oct 2009 07:36:48 +0200	[thread overview]
Message-ID: <4AE3E3F0.3020606@redhat.com> (raw)
In-Reply-To: <20091024003756G.fujita.tomonori@lab.ntt.co.jp>

On 10/23/2009 05:40 PM, FUJITA Tomonori wrote:
> On Fri, 23 Oct 2009 09:14:29 -0500
> Javier Guerra<javier@guerrag.com>  wrote:
>
>    
>>> I think that the major difference between sheepdog and cluster file
>>> systems such as Google File system, pNFS, etc is the interface between
>>> clients and a storage system.
>>>        
>> note that GFS is "Global File System" (written by Sistina (the same
>> folks from LVM) and bought by RedHat).  Google Filesystem is a
>> different thing, and ironically the client/storage interface is a
>> little more like sheepdog and unlike a regular cluster filesystem.
>>      
> Hmm, Avi referred to Global File System? I wasn't sure. 'GFS' is
> ambiguous. Anyway, Global File System is a SAN file system. It's
> a completely different architecture from Sheepdog.
>    

I did, and yes, it is completely different since you don't require 
central storage.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-10-25  5:37 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 ` [Qemu-devel] " Avi Kivity
2009-10-22 16:28   ` 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 [this message]
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=4AE3E3F0.3020606@redhat.com \
    --to=avi@redhat.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=javier@guerrag.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).