All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Tommi Virtanen <tv@inktank.com>
Cc: Alexandre DERUMIER <aderumier@odiso.com>, ceph-devel@vger.kernel.org
Subject: Re: is rados block cluster production ready ?
Date: Mon, 21 May 2012 10:09:19 +0200	[thread overview]
Message-ID: <4FB9F82F.9050208@profihost.ag> (raw)
In-Reply-To: <CADvuQREa3PXCG4Udvuy45wHUKBAruc40md_cOrssXYTN+8-JJw@mail.gmail.com>

Am 18.05.2012 18:13, schrieb Tommi Virtanen:
> <aderumier@odiso.com> wrote:
>> About network, does the rados protocol support some kind of multipathing ? Or does I need to use bonding/lacp ?
> 
> Bonding is almost always good if you have the switch ports & bandwidth
> to spare. Even without bonding, one of the tricks RADOS does is that
> each chunk of the RBD image is stored on a different OSD, so your
> hypervisor will actually talk to even thousands of OSDs when the vm
> accesses the disk. This way, the network link of any individual
> storage node is less likely to become a performance bottleneck for the
> vm.
That's great but if you go the way of having for example 8x OSDs per
server with 8 single Disks - how can i archieve that ceph is splitting
my files to the correct servers for redundancy?

Stefan

  reply	other threads:[~2012-05-21  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <531ff5f3-11d5-488e-adfb-68000f3c36c0@mailpro>
2012-05-18  6:08 ` is rados block cluster production ready ? Alexandre DERUMIER
2012-05-18  8:45   ` Christian Brunner
2012-05-18  9:58     ` Alexandre DERUMIER
2012-05-18 10:43       ` Christian Brunner
2012-05-18 16:13   ` Tommi Virtanen
2012-05-21  8:09     ` Stefan Priebe - Profihost AG [this message]
2012-05-21  8:18       ` Tim O'Donovan
2012-05-21  8:25         ` Stefan Priebe - Profihost AG

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=4FB9F82F.9050208@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=aderumier@odiso.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tv@inktank.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 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.