diff options
| author | Sage Weil <sage@inktank.com> | 2013-05-02 07:30:55 -0700 |
|---|---|---|
| committer | Sage Weil <sage@inktank.com> | 2013-05-02 07:30:55 -0700 |
| commit | 45c9e24f0ed872da4be0a56e141098339c5d1880 (patch) | |
| tree | 44931e8d5d69f182be3ea99d81c95f0420b34d66 | |
| parent | a8d4647336bc9d3d6e92e75664c68369b6f774df (diff) | |
| download | ceph-45c9e24f0ed872da4be0a56e141098339c5d1880.tar.gz | |
doc/install/upgrading...: note about transitioning to ceph-deploy
Signed-off-by: Sage Weil <sage@inktank.com>
| -rw-r--r-- | doc/install/upgrading-ceph.rst | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/install/upgrading-ceph.rst b/doc/install/upgrading-ceph.rst index 667a9e235b9..60ead365622 100644 --- a/doc/install/upgrading-ceph.rst +++ b/doc/install/upgrading-ceph.rst @@ -200,6 +200,19 @@ Multi-MDS configurations with identical names must be adjusted accordingly to give daemons unique names. If you run your cluster with one metadata server, you can disregard this notice for now. +ceph-deploy +----------- + +The ceph-deploy tool is now the preferred method of provisioning new +clusters. For existing clusters created via mkcephfs that would like +to transition to the new tool, there is a migration path, documented +at `Transitioning to ceph-deploy`_. Note that transitioning to +ceph-deploy is not required; it is entirely acceptable to continue +provisioning new OSDs and monitors using the previous methods. +However, ceph-deploy streamlines these processes significantly. + +.. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition + Upgrade Procedures ================== |