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:



-b, --bluestore

Use bluestore as the objectstore backend for osds.

--cache <pool>

Set a cache-tier for the specified pool.

-d, --debug

Launch in debug mode.


Create an erasure pool.

-f, --filestore

Use filestore as the osd objectstore backend.

--hitset <pool> <hit_set_type>

Enable hitset tracking.

-i ip_address

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


Keep old configuration files instead of overwritting theses.

-K, --kstore

Use kstore as the osd objectstore backend.

-l, --localhost

Use localhost instead of hostanme.

-m ip[:port]

Specifies monitor ip address and port.


Use memstore as the objectstore backend for osds

--multimds <count>

Allow multimds with maximum active count.

-n, --new

Create a new cluster.

-N, --not-new

Reuse existing cluster config (default).


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


Disable lockdep

-o <config>

Add config to all sections in the ceph configuration.

--rgw_port <port>

Specify ceph rgw http listen port.

--rgw_frontend <frontend>

Specify the rgw frontend configuration (default is civetweb).

--rgw_compression <compression_type>

Specify the rgw compression plugin (default is disabled).


Configure mds with small limit cache size.


Short object names only; necessary for ext4 dev

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

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


Do not run using mgr dashboard.


Enable cephx (on by default).


Disable cephx.

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

For stopping the cluster, you do:

./ <cluster-name>