openstack/manila
Code Issues Proposed changes

Documentation changes for thin/thick provisioning

Browse Source 
This patch adds documentation changes for the logic changed
to address thin/thick provisioning in the following patch:
    https://review.openstack.org/#/c/315266/

Change-Id: I6a15a572abd7ccec59917bd58db5e3cca32d77a3
Partial-Bug: #1578718
This commit is contained in:
xing-yang 2016-07-21 09:14:04 -04:00
parent eddeff89bd
commit 2d957f3890
1 changed files with 15 additions and 5 deletions

20
doc/source/devref/capabilities_and_extra_specs.rst

@ -116,11 +116,21 @@ be created.
by setting this extra-spec to '<is> True'. If a driver reports
thin_provisioning=False (the default) then it's assumed that the driver is
doing thick provisioning and overprovisioning is turned off.
If an array can technically support both thin and thick provisioning in a
pool, the driver still needs to programmatically determine which to use.
This should be done by configuring one pool for thin and another pool for
thick. So, a manila pool will always report thin_provisioning as True or
False. Added in Liberty.
This was added in Liberty. In Liberty and Mitaka, the driver was required
to configure one pool for thin and another pool for thick and report
thin_provisioning as either True or False even if an array can technically
support both thin and thick provisioning in a pool. In Newton, the logic is
changed to allow a driver to report thin_provisioning=[True, False] if it
can support both thin and thick provisioning in a pool. To provision a thick
share on a back end that supports both thin and thick provisioning, set one
of the following in extra specs:
::
{'thin_provisioning': 'False'}
{'thin_provisioning': '<is> False'}
{'capabilities:thin_provisioning': 'False'}
{'capabilities:thin_provisioning': '<is> False'}
* `qos` - indicates that a backend/pool can provide shares using some
QoS (Quality of Service) specification. The default value of the qos