[cloudstack-documentation] branch main updated: Added vmware disk provisioning types (#217)

[su...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sureshanaparti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/main by this push:
     new e99c2bb  Added vmware disk provisioning types (#217)
e99c2bb is described below

commit e99c2bb3d5fd6913d6c08de873420e7c4a015a8f
Author: Spaceman1984 <49...@users.noreply.github.com>
AuthorDate: Mon Jul 19 11:03:34 2021 +0200

    Added vmware disk provisioning types (#217)
    
    Added support for VMWare disk provisioning types (Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed)
---
 source/adminguide/service_offerings.rst | 22 +++++++++++++++++++---
 1 file changed, 19 insertions(+), 3 deletions(-)

diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst
index 78415e4..444200c 100644
--- a/source/adminguide/service_offerings.rst
+++ b/source/adminguide/service_offerings.rst
@@ -187,8 +187,15 @@ To create a new compute offering:
       system VM is running. Shared allocates from storage accessible via
       NFS.
 
-   -  **Provisioning type**: The type of disk that should be allocated. 
-      Local
+   -  **Provisioning type**: The type of disk that should be allocated.
+      Valid values are thin, sparse, fat. When using the VMWare hypervisor,
+      these values are mapped to the following vSphere disk provisioning types:
+
+      -  **thin**:  **Thin Provision**
+      -  **sparse**:  **Thick Provision Lazy Zeroed**
+      -  **fat**:   **Thick Provision Eager Zeroed**
+
+      The disk provisioning type strictness on VMWare is controlled with the zone level setting - **disk.provisioning.type.strictness**. If set to true, the disk is created only when there is a suitable storage pool that supports the disk provisioning type specified by the service/disk offering. If set to false, the disk is created with a disk provisioning type supported by the pool. Default value is false and this is currently supported for VMware only.
 
    -  **Compute Offering Type**: The amount of freedom that the end user
       has to customise the compute power that their instance has when using this
@@ -383,6 +390,16 @@ To create a new disk offering:
    -  **Disk Size**: Appears only if Custom Disk Size is not selected.
       Define the volume size in GB (2^30 1GB = 1,073,741,824 Bytes).
 
+   -  **Provisioning type**: The type of disk that should be allocated.
+      Valid values are thin, sparse, fat. When using the VMWare hypervisor,
+      these values are mapped to the following vSphere disk provisioning types:
+
+      -  **thin**:  **Thin Provision**
+      -  **sparse**:  **Thick Provision Lazy Zeroed**
+      -  **fat**:   **Thick Provision Eager Zeroed**
+
+      The disk provisioning type strictness on VMWare is controlled with the zone level setting - **disk.provisioning.type.strictness**. If set to true, the disk is created only when there is a suitable storage pool that supports the disk provisioning type specified by the service/disk offering. If set to false, the disk is created with a disk provisioning type supported by the pool. Default value is false and this is currently supported for VMware only.
+
    -  **QoS Type** [2]_: Three options: Empty (no Quality of Service), hypervisor
       (rate limiting enforced on the hypervisor side), and storage
       (guaranteed minimum and maximum IOPS enforced on the storage
@@ -704,4 +721,3 @@ default system offering used for System VMs.
 
 #. Destroy the existing CPVM or SSVM offerings and wait for them to be
    recreated. The new CPVM or SSVM are configured with the new offering.
-