Deploying a development cluster

In order to develop on ceph, a Ceph utility,, allows you to deploy fake local cluster for development purpose.


It allows to deploy a fake local cluster on your machine for development purpose. It starts rgw, mon, osd and/or mds, or all of them if not specified.

To start your development cluster, type the following: [OPTIONS]...

In order to stop the cluster, you can type:



-i ip_address

Bind to the specified ip_address instead of guessing and resolve from hostname.


Keep old configuration files instead of overwritting theses.

-l, --localhost

Use localhost instead of hostanme.

-m ip[:port]

Specifies monitor ip address and port.

-n, --new

Create a new cluster.

-o config

Add config to all sections in the ceph configuration.


Use ceph-run as wrapper for mon/osd/mds.


Configure mds with small limit cache size.


Enable Cephx (on by default).


Disable Cephx.

-d, --debug

Launch in debug mode

--valgrind[_{osd,mds,mon}] 'valgrind_toolname [args...]'

Launch the osd/mds/mon/all the ceph binaries using valgrind with the specified tool and arguments.


Use bluestore as the objectstore backend for osds


Use memstore as the objectstore backend for osds

--cache <pool>

Set a cache-tier for the specified pool

Environment variables


Theses environment variables will contains the number of instances of the desired ceph process you want to start.



Deploying multiple development clusters on the same machine

In order to bring up multiple ceph clusters on the same machine, a small wrapper around the above vstart can help.


To start multiple clusters, you would run mstart for each cluster you would want to deploy, and it will start monitors, rgws for each cluster on different ports allowing you to run multiple mons, rgws etc. on the same cluster. Invoke it in the following way: <cluster-name> <vstart options>

For eg:

./ cluster1 -n -r

For stopping the cluster, you do:

./ <cluster-name>