From: Chris Webb <chris@arachsys.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: Dietmar Maurer <dietmar@proxmox.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Sheepdog: Distributed Storage System for KVM
Date: Fri, 23 Oct 2009 11:26:59 +0100 [thread overview]
Message-ID: <20091023102659.GY1930@arachsys.com> (raw)
In-Reply-To: <20091023101738.GA1997@arachsys.com>
Chris Webb <chris@arachsys.com> writes:
> MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp> writes:
>
> > We use JGroups (Java library) for reliable multicast communication in
> > our cluster manager daemon. We don't worry about the performance much
> > since the cluster manager daemon is not involved in the I/O path. We
> > might think about moving to corosync if it is more stable than
> > JGroups.
>
> I'd love to see this running on top of corosync too. Corosync is a well
> tested, stable cluster manager, and doesn't have the JVM dependency of
> jgroups so feels more suitable for building 'thin virtualisation fabrics'.
Very exciting project, by the way!
Best wishes,
Chris.
WARNING: multiple messages have this Message-ID (diff)
From: Chris Webb <chris@arachsys.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Dietmar Maurer <dietmar@proxmox.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [ANNOUNCE] Sheepdog: Distributed Storage System for KVM
Date: Fri, 23 Oct 2009 11:26:59 +0100 [thread overview]
Message-ID: <20091023102659.GY1930@arachsys.com> (raw)
In-Reply-To: <20091023101738.GA1997@arachsys.com>
Chris Webb <chris@arachsys.com> writes:
> MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp> writes:
>
> > We use JGroups (Java library) for reliable multicast communication in
> > our cluster manager daemon. We don't worry about the performance much
> > since the cluster manager daemon is not involved in the I/O path. We
> > might think about moving to corosync if it is more stable than
> > JGroups.
>
> I'd love to see this running on top of corosync too. Corosync is a well
> tested, stable cluster manager, and doesn't have the JVM dependency of
> jgroups so feels more suitable for building 'thin virtualisation fabrics'.
Very exciting project, by the way!
Best wishes,
Chris.
next prev parent reply other threads:[~2009-10-23 10:32 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 5:13 [ANNOUNCE] Sheepdog: Distributed Storage System for KVM MORITA Kazutaka
2009-10-21 5:13 ` [Qemu-devel] " MORITA Kazutaka
2009-10-21 8:28 ` Nikolai K. Bochev
2009-10-21 8:28 ` [Qemu-devel] " Nikolai K. Bochev
2009-10-21 8:45 ` Nikolai K. Bochev
2009-10-21 8:45 ` [Qemu-devel] " Nikolai K. Bochev
2009-10-23 9:59 ` MORITA Kazutaka
2009-10-23 9:59 ` [Qemu-devel] " MORITA Kazutaka
2009-10-21 9:08 ` Dietmar Maurer
2009-10-21 9:08 ` [Qemu-devel] " Dietmar Maurer
2009-10-23 10:06 ` MORITA Kazutaka
2009-10-23 10:06 ` [Qemu-devel] " MORITA Kazutaka
2009-10-23 10:17 ` Chris Webb
2009-10-23 10:17 ` [Qemu-devel] " Chris Webb
2009-10-23 10:26 ` Chris Webb [this message]
2009-10-23 10:26 ` Chris Webb
2009-10-23 11:10 ` Dietmar Maurer
2009-10-23 11:10 ` [Qemu-devel] " Dietmar Maurer
2009-10-23 11:45 ` Dietmar Maurer
2009-10-23 11:45 ` [Qemu-devel] " Dietmar Maurer
2009-10-21 9:08 ` Dietmar Maurer
2009-10-22 15:30 ` Avi Kivity
2009-10-22 15:30 ` [Qemu-devel] " Avi Kivity
2009-10-22 16:28 ` Anthony Liguori
2009-10-22 16:28 ` [Qemu-devel] " Anthony Liguori
2009-10-22 22:09 ` Alexander Graf
2009-10-22 22:09 ` [Qemu-devel] " Alexander Graf
2009-10-23 10:41 ` MORITA Kazutaka
2009-10-23 10:41 ` [Qemu-devel] " MORITA Kazutaka
2009-10-23 11:10 ` Alexander Graf
2009-10-23 11:10 ` [Qemu-devel] " Alexander Graf
2009-10-23 16:17 ` MORITA Kazutaka
2009-10-23 14:14 ` Javier Guerra
2009-10-23 14:14 ` [Qemu-devel] " Javier Guerra
2009-10-23 14:58 ` Chris Webb
2009-10-23 14:58 ` Chris Webb
2009-10-23 15:10 ` Javier Guerra
2009-10-23 15:10 ` Javier Guerra
2009-10-23 17:05 ` Tomasz Chmielewski
2009-10-23 17:05 ` Tomasz Chmielewski
2009-10-25 8:44 ` Dietmar Maurer
2009-10-25 8:44 ` Dietmar Maurer
2009-10-25 10:55 ` Tomasz Chmielewski
2009-10-25 10:55 ` Tomasz Chmielewski
2009-10-23 15:40 ` FUJITA Tomonori
2009-10-23 15:40 ` [Qemu-devel] " FUJITA Tomonori
2009-10-25 5:36 ` Avi Kivity
2009-10-25 5:36 ` [Qemu-devel] " Avi Kivity
2009-10-25 8:51 ` Dietmar Maurer
2009-10-25 8:51 ` [Qemu-devel] " Dietmar Maurer
2009-10-26 6:53 ` MORITA Kazutaka
2009-10-26 6:53 ` [Qemu-devel] " MORITA Kazutaka
2009-10-22 18:46 ` Avishay Traeger
2009-10-22 18:46 ` [Qemu-devel] " Avishay Traeger
2009-10-22 18:53 ` Avishay Traeger
2009-10-23 15:41 ` MORITA Kazutaka
2009-10-23 11:22 ` Dietmar Maurer
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-23 19:45 ` Javier Guerra
2009-10-24 2:49 ` MORITA Kazutaka
2009-10-24 2:49 ` MORITA Kazutaka
2009-10-28 3:53 ` 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=20091023102659.GY1930@arachsys.com \
--to=chris@arachsys.com \
--cc=dietmar@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.