Project

General

Profile

Bug #750 » ceph.conf

changping Wu, 02/09/2011 07:49 PM

 
;
; Sample ceph ceph.conf file.
;
; This file defines cluster membership, the various locations
; that Ceph stores data, and any other runtime options.

; If a 'host' is defined for a daemon, the start/stop script will
; verify that it matches the hostname (or else ignore it). If it is
; not defined, it is assumed that the daemon is intended to start on
; the current host (e.g., in a setup with a startup.conf on each
; node).

; global
[global]
; enable secure authentication
;auth supported = cephx

; monitors
; You need at least one. You need at least three if you want to
; tolerate any node failures. Always create an odd number.
[mon]
mon data = /opt/data/mon$id

; logging, for debugging monitor crashes, in order of
; their likelihood of being helpful :)
;debug ms = 1
;debug mon = 20
;debug paxos = 20
;debug auth = 20

[mon0]
host = ubuntu-client
mon addr = 172.16.10.68:6789

;[mon1]
;host = ubuntu-client
;mon addr = 127.0.0.1:6789

;[mon2]
;host = gamma
;mon addr = 192.168.0.12:6789

; mds
; You need at least one. Define two to get a standby.
[mds]
; where the mds keeps it's secret encryption keys
keyring = /opt/data/keyring.$name

; mds logging to debug issues.
;debug ms = 1
;debug mds = 20

[mds.alpha]
host = ubuntu-client

[mds.beta]
host = ubuntu-client

; osd
; You need at least one. Two if you want data to be replicated.
; Define as many as you like.
[osd]
; This is where the btrfs volume will be mounted.
osd data = /opt/data/osd$id

; Ideally, make this a separate disk or partition. A few
; hundred MB should be enough; more if you have fast or many
; disks. You can use a file under the osd data dir if need be
; (e.g. /data/osd$id/journal), but it will be slower than a
; separate disk or partition.
osd journal = /opt/data/osd$id/journal
osd journal size = 10000
; osd logging to debug osd issues, in order of likelihood of being
; helpful
;debug ms = 1
;debug osd = 20
;debug filestore = 20
;debug journal = 20

[osd0]
host = ubuntu-client

; if 'btrfs devs' is not specified, you're responsible for
; setting up the 'osd data' dir. if it is not btrfs, things
; will behave up until you try to recover from a crash (which
; usually fine for basic testing).
; btrfs devs = /dev/sdx

[osd1]
host = ubuntu-client
;btrfs devs = /dev/sdy

;[osd2]
;host = ubuntu-client
;btrfs devs = /dev/sdx

;[osd3]
;host = eta
;btrfs devs = /dev/sdy
(1-1/3)