RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-04-01 14:51:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/release-notes: warn about sysvinit crush map update

Browse Source 
See c189d855e6.

Signed-off-by: Sage Weil <sage@inktank.com>
This commit is contained in:
Sage Weil 2013-05-03 11:36:37 -07:00
parent 6f8c1e9cf4
commit a0988be62f
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/release-notes.rst
View File

@ -15,6 +15,15 @@ Upgrading from v0.60
.. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
* The sysvinit script (/etc/init.d/ceph) will now verify (and, if
necessary, update) the OSD's position in the CRUSH map on startup.
(The upstart script has always worked this way.) By default, this
ensures that the OSD is under a 'host' with a name that matches the
hostname (``hostname -s``). Legacy clusters create with mkcephfs do
this by default, so this should not cause any problems, but legacy
clusters with customized CRUSH maps with an alternate structure
should set ``osd crush update on start = false``.
* radosgw-admin now uses the term zone instead of cluster to describe
each instance of the radosgw data store (and corresponding
collection of radosgw daemons). The usage for the radosgw-admin
@ -54,6 +63,15 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details.
.. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
* The sysvinit script (/etc/init.d/ceph) will now verify (and, if
necessary, update) the OSD's position in the CRUSH map on startup.
(The upstart script has always worked this way.) By default, this
ensures that the OSD is under a 'host' with a name that matches the
hostname (``hostname -s``). Legacy clusters create with mkcephfs do
this by default, so this should not cause any problems, but legacy
clusters with customized CRUSH maps with an alternate structure
should set ``osd crush update on start = false``.
* radosgw-admin now uses the term zone instead of cluster to describe
each instance of the radosgw data store (and corresponding
collection of radosgw daemons). The usage for the radosgw-admin