doc/dev/dev_cluster_deployment.rst - main - githubmirror/ceph

doc/dev/dev_cluster_deployment.rst
167 строк4 KB
Kefu Chai
doc/dev: refresh vstart.sh options in dev_cluster_deployment
16 май 2026, 07:45
16 май 2026, 07:45019ee27
.. _dev_deploying_a_development_cluster:

=================================
 Deploying a development cluster
=================================

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

Usage
=====

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::

	vstart.sh [OPTIONS]...

On a fresh build, the first run must create the cluster by passing ``-n``;
later runs can omit it to restart and reuse the existing cluster.

In order to stop the cluster, you can type::

	./stop.sh

Options
=======

The most common options are listed below.  ``vstart.sh`` accepts many more
(crimson, seastore, msgr versions, bluestore devices, and so on); see the
``usage`` text near the top of ``src/vstart.sh`` for the complete list.

.. option:: -b, --bluestore

    Use bluestore as the objectstore backend for osds.  This is the default.

.. option:: --cache <pool>

    Set a cache-tier for the specified pool.

.. option:: -d, --debug

    Launch in debug mode.

.. option:: -e

    Create an erasure pool.

.. option:: --hitset <pool> <hit_set_type>

    Enable hitset tracking.

.. option:: -i ip_address

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

.. option:: -k

    Keep old configuration files instead of overwriting these.

.. option:: -l, --localhost

    Use localhost instead of hostname.

.. option:: -m ip[:port]

    Specifies monitor *ip* address and *port*.

.. option:: --memstore

    Use memstore as the objectstore backend for osds

.. option:: --multimds <count>

    Allow multimds with maximum active count.

.. option:: -n, --new

    Create a new cluster, replacing any existing one.  Without this flag,
    ``vstart.sh`` reuses the existing cluster config; that is the default.

.. option:: --nodaemon

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

.. option:: --nolockdep

    Disable lockdep

.. option:: -o <config>

    Add *config* to all sections in the ceph configuration.

.. option:: --rgw_port <port>

    Specify ceph rgw http listen port.

.. option:: --rgw_frontend <frontend>

    Specify the rgw frontend configuration (default is beast).

.. option:: --rgw_compression <compression_type>

    Specify the rgw compression plugin (default is disabled).

.. option:: --smallmds

    Configure mds with small limit cache size.

.. option:: --short

    Short object names only; necessary for ext4 dev

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

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

.. option:: --without-dashboard

    Do not run using mgr dashboard.

.. option:: -x

    Enable cephx (on by default).

.. option:: -X

    Disable cephx.


Environment variables
=====================

{OSD,MDS,MON,RGW}

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

Example: ::

	OSD=3 MON=3 RGW=1 vstart.sh -n


============================================================
 Deploying multiple development clusters on the same machine
============================================================

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

Usage
=====

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::

  mstart.sh <cluster-name> <vstart options>

For eg::

  ./mstart.sh cluster1 -n


For stopping the cluster, you do::

  ./mstop.sh <cluster-name>