;
; 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
         ; keyring=/etc/ceph/keyring.bin
        ; allow ourselves to open a lot of files
        max open files = 131072

        ; set up logging
        log file = /var/log/ceph/$name.log

        ; set up pid files
        pid file = /var/run/ceph/$name.pid

; 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 = /mnt/data/mon$id
	crush map = /etc/ceph/crushmap/crush.new

	; 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

[mon.0]
	host = ubuntu-mon0
        mon addr = 172.16.35.10:6789

[mon.1]
	host = ubuntu-mon0
        mon addr =172.16.35.10:6790

[mon.2]
	host = ubuntu-mon0
        mon addr =172.16.35.10:6791

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

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

[mds.alpha]
	host = ubuntu-mon0
        
[mds.beta]
	host = ubuntu-mon0

; 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 = /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.

        ; This is an example of a file-based journal.
	; osd journal = /data/osd$id/journal
	; osd journal size = 10000 ; journal size, in megabytes

	; 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

[osd.0]
	host = ubuntu-osd0
        osd data = /mnt/data/osd0/osd$id
        osd journal = /mnt/journal/osd0/osd$id
        osd journal size = 20000 ; journal size, in megabytes
        ;keyring = /etc/ceph/keyring.$name

	; 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

[osd.1]
	host = ubuntu-osd0
        osd data = /mnt/data/osd1/osd$id
        osd journal = /mnt/journal/osd1/osd$id 
        osd journal size = 20000 ; journal size, in megabytes
	;keyring = /etc/ceph/keyring.$name

        ;btrfs devs = /dev/sdy

[osd.2]
	host = ubuntu-osd1
        osd data = /mnt/data/osd2/osd$id
        osd journal = /mnt/journal/osd2/osd$id
        osd journal size = 20000 ; journal size, in megabytes
	;host = zeta
	;btrfs devs = /dev/sdx

[osd.3]
	host = ubuntu-osd1
        osd data = /mnt/data/osd3/osd$id
        osd journal = /mnt/journal/osd3/osd$id 
        osd journal size = 20000 ; journal size, in megabytes
	;btrfs devs = /dev/sdy
[osd.4]
	host = ubuntu-osd2
        osd data = /mnt/data/osd4/osd$id
        osd journal = /mnt/journal/osd4/osd$id 
        osd journal size = 20000 ; journal size, in megabytes
	;btrfs devs = /dev/sdy
[osd.5]
	host = ubuntu-osd2
        osd data = /mnt/data/osd5/osd$id
        osd journal = /mnt/journal/osd5/osd$id 
        osd journal size = 20000 ; journal size, in megabytes
	;btrfs devs = /dev/sdy