All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: cbt <cbt@ceph.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Bluestore cluster example
Date: Fri, 15 Apr 2016 07:06:14 -0500	[thread overview]
Message-ID: <5710D936.9040507@redhat.com> (raw)

Hi all,

A couple of folks have asked me how to setup bluestore clusters for 
performance testing.  I personally am using cbt for this, but you should 
be able to use ceph-disk with some other cluster creation method as well.

For CBT, you really don't need to do much.  In the old newstore days, a 
"block" symlink needed to be created in the osd data dir to link to the 
new block device.  CBT did this when the "newstore_block: True" option 
was set in the cluster section of the cbt yaml file.  This isn't really 
needed anymore, as you can now specify the block, db, and wal devices 
directly in your ceph.conf file.  If your partitions are setup properly 
you can create bluestore clusters without having to do anything beyond 
changing the ceph.conf file (with cbt at least).

Here's a very basic example:

[global]
         enable experimental unrecoverable data corrupting features = 
bluestore rocksdb
         osd objectstore = bluestore

[osd.0]
         host = incerta01.front.sepia.ceph.com
         osd data = /tmp/cbt/mnt/osd-device-0-data
         bluestore block path = /dev/disk/by-partlabel/osd-device-0-block
         bluestore block db path = /dev/disk/by-partlabel/osd-device-0-db
         bluestore block wal path = /dev/disk/by-partlabel/osd-device-0-wal


Here we enable the experimental bluestore and rocksdb features, set the 
objectstore to bluestore, and then in the OSD sections manually set the 
osd data, bluestore block, bluestore block db, and bluestore block wal 
paths.  You might be wondering what all of these are for:

osd data <-- very small directory on FS for bootstrapping OSD.
bluestore block <-- where the actual object data lives
bluestore block db path <-- where rocksdb lives
bluestore block wal path <-- where rocksdb writeahead log lives

And that's basically it.  I've uploaded an example partitioning script, 
ceph.conf file, and cbt yaml configuration file based on actual tests 
I'm running to the examples folder that I've actually been using for 
testing here:

https://github.com/ceph/cbt/tree/master/example/bluestore

Thanks,
Mark

             reply	other threads:[~2016-04-15 12:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 12:06 Mark Nelson [this message]
2016-04-15 15:21 ` Bluestore cluster example Somnath Roy
2016-04-16  0:56 ` [Cbt] " Shinobu Kinjo
2016-04-22 13:38 ` Dan van der Ster
2016-04-22 14:09   ` Sage Weil
2016-04-22 14:48     ` Dan van der Ster
2016-04-22 14:57       ` Sage Weil
2016-04-23  4:51         ` Li Tianxiang

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=5710D936.9040507@redhat.com \
    --to=mnelson@redhat.com \
    --cc=cbt@ceph.com \
    --cc=ceph-devel@vger.kernel.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.