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.
+ Use bluestore as the objectstore backend for osds. This is the default.
.. option:: --cache <pool>
Keep old configuration files instead of overwriting these.
-.. option:: -K, --kstore
-
- Use kstore as the osd objectstore backend.
-
.. option:: -l, --localhost
Use localhost instead of hostname.
.. option:: -n, --new
- Create a new cluster.
-
-.. option:: -N, --not-new
-
- Reuse existing cluster config (default).
+ Create a new cluster, replacing any existing one. Without this flag,
+ ``vstart.sh`` reuses the existing cluster config; that is the default.
.. option:: --nodaemon
.. option:: --rgw_frontend <frontend>
- Specify the rgw frontend configuration (default is civetweb).
+ Specify the rgw frontend configuration (default is beast).
.. option:: --rgw_compression <compression_type>
Example: ::
- OSD=3 MON=3 RGW=1 vstart.sh
+ OSD=3 MON=3 RGW=1 vstart.sh -n
============================================================