[ceph.git] / ceph / doc / ceph-volume / lvm / create.rst

.. _ceph-volume-lvm-create:

``create``
===========
This subcommand wraps the two-step process to provision a new osd (calling
``prepare`` first and then ``activate``) into a single
one. The reason to prefer ``prepare`` and then ``activate`` is to gradually
introduce new OSDs into a cluster, and avoiding large amounts of data being
rebalanced.

The single-call process unifies exactly what :ref:`ceph-volume-lvm-prepare` and
:ref:`ceph-volume-lvm-activate` do, with the convenience of doing it all at
once.

There is nothing different to the process except the OSD will become up and in
immediately after completion.

The backing objectstore can be specified with:

* :ref:`--bluestore <ceph-volume-lvm-prepare_bluestore>`

All command line flags and options are the same as ``ceph-volume lvm prepare``.
Please refer to :ref:`ceph-volume-lvm-prepare` for details.
Commit	Line	Data
3efd9988 FG	1	.. _ceph-volume-lvm-create:
	2
	3	``create``
	4	===========
	5	This subcommand wraps the two-step process to provision a new osd (calling
	6	``prepare`` first and then ``activate``) into a single
	7	one. The reason to prefer ``prepare`` and then ``activate`` is to gradually
	8	introduce new OSDs into a cluster, and avoiding large amounts of data being
	9	rebalanced.
	10
	11	The single-call process unifies exactly what :ref:`ceph-volume-lvm-prepare` and
	12	:ref:`ceph-volume-lvm-activate` do, with the convenience of doing it all at
	13	once.
	14
	15	There is nothing different to the process except the OSD will become up and in
	16	immediately after completion.
	17
	18	The backing objectstore can be specified with:
	19
3efd9988 FG	20	* :ref:`--bluestore <ceph-volume-lvm-prepare_bluestore>`
	21
	22	All command line flags and options are the same as ``ceph-volume lvm prepare``.
	23	Please refer to :ref:`ceph-volume-lvm-prepare` for details.