From cb12a3177cb51ea37d3930a40f58c681ddefd2ac Mon Sep 17 00:00:00 2001 From: Sebastian Wagner Date: Fri, 20 Mar 2020 12:33:27 +0100 Subject: [PATCH] doc/cephadm: replace `osd create` with `apply osd` Fixes: https://tracker.ceph.com/issues/44692 Signed-off-by: Sebastian Wagner --- doc/cephadm/drivegroups.rst | 4 ++-- doc/cephadm/install.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/cephadm/drivegroups.rst b/doc/cephadm/drivegroups.rst index 8497559f486eb..29c8e388a3389 100644 --- a/doc/cephadm/drivegroups.rst +++ b/doc/cephadm/drivegroups.rst @@ -10,7 +10,7 @@ with which configuration without knowing the specifics of device names and paths Instead of doing this:: - [monitor 1] # ceph orchestrator osd create **:** + [monitor 1] # ceph orch daemon add osd **:** for each device and each host, we can define a yaml|json file that allows us to describe the layout. Here's the most basic example. @@ -32,7 +32,7 @@ There will be a more detailed section on host_pattern down below. and pass it to `osd create` like so:: - [monitor 1] # ceph orchestrator osd create -i /path/to/drivegroup.yml + [monitor 1] # ceph orch apply osd -i /path/to/drivegroup.yml This will go out on all the matching hosts and deploy these OSDs. diff --git a/doc/cephadm/install.rst b/doc/cephadm/install.rst index 42c135e55560e..c6f4962d58924 100644 --- a/doc/cephadm/install.rst +++ b/doc/cephadm/install.rst @@ -289,7 +289,7 @@ There are a few ways to create new OSDs: based on their properties, such device type (SSD or HDD), device model names, size, or the hosts on which the devices exist:: - # ceph orch osd create -i spec.yml + # ceph orch apply osd -i spec.yml Deploy MDSs -- 2.39.5