Merge pull request #12054 from ddiss/doc_osd_pool_restriction

doc: clarify file deletion from OSD restricted pool behaviour

Reviewed-by: Sage Weil <sage@redhat.com>
This commit is contained in:
Sage Weil 2016-11-17 14:57:24 -06:00 committed by GitHub
commit f61b7ce6a9
2 changed files with 8 additions and 2 deletions

View File

@ -78,6 +78,12 @@ restricts access to the CephFS data pool(s):
caps: [mon] allow r
caps: [osd] allow rw pool=data1, allow rw pool=data2
.. note::
Without a corresponding MDS path restriction, the OSD capabilities above do
**not** restrict file deletions outside of the ``data1`` and ``data2``
pools.
You may also restrict clients from writing data by using 'r' instead of
'rw' in OSD capabilities. This does not affect the ability of the client
to update filesystem metadata for these files, but it will prevent them

View File

@ -24,7 +24,7 @@ how many ranks will be created. The actual number of ranks
in the filesystem will only be increased if a spare daemon is
available to take on the new rank.
An daemon has a *name* that is set statically by the administrator
A daemon has a *name* that is set statically by the administrator
when the daemon is first configured. Typical configurations
use the hostname where the daemon runs as the daemon name.
@ -95,7 +95,7 @@ mds_standby_replay
~~~~~~~~~~~~~~~~~~
If this is set to true, then the standby daemon will continuously read
the metadata journal an up rank. This will give it
the metadata journal of an up rank. This will give it
a warm metadata cache, and speed up the process of failing over
if the daemon serving the rank fails.