-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathPendingReleaseNotes
54 lines (38 loc) · 1.99 KB
/
PendingReleaseNotes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
v9.1.0
======
* When a pool quota is reached, librados operations now block indefinitely,
the same way they do when the cluster fills up. (Previously they would return
-ENOSPC). By default, a full cluster or pool will now block. If your
librados application can handle ENOSPC or EDQUOT errors gracefully, you can
get error returns instead by using the new librados OPERATION_FULL_TRY flag.
v9.0.4
======
Upgrading
---------
* Ceph daemons now run as user and group ceph by default. The ceph user has a
static UID assigned by Fedora and Debian (also used by derivative distributions
like RHEL/CentOS and Ubuntu). On SUSE the ceph user will currently get a
dynamically assigned UID when the user is created.
If your systems already have a ceph user, upgrading the package will cause
problems. We suggest you first remove or rename the existing 'ceph' user
before upgrading.
When upgrading, administrators have two options:
#. Add the following line to ``ceph.conf`` on all hosts::
setuser match path = /var/lib/ceph/$type/$cluster-$id
This will make the Ceph daemons run as root (i.e., not drop
privileges and switch to user ceph) if the daemon's data
directory is still owned by root. Newly deployed daemons will
be created with data owned by user ceph and will run with
reduced privileges, but upgraded daemons will continue to run as
root.
#. Fix the data ownership during the upgrade. This is the preferred option,
but is more work. The process for each host would be to:
#. Upgrade the ceph package. This creates the ceph user and group.
#. Stop the daemon(s)
#. Fix the ownership. E.g.,::
chown -R ceph:ceph /var/lib/ceph/mon/ceph-foo
chown -R ceph:ceph /var/lib/ceph/osd/ceph-123
#. Restart the daemon(s)
* The on-disk format for the experimental KeyValueStore OSD backend has
changed. You will need to remove any OSDs using that backend before you
upgrade any test clusters that use it.