[cloudstack-documentation] 01/01: Revert "Added vmware disk provisioning types (#187)"

[da...@apache.org]

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

dahn pushed a commit to branch revert-187-disk-provisioning-types-vmware
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git

commit 1112b24e2b21fc518b9dc236a1762bfebbcca8ea
Author: dahn <da...@gmail.com>
AuthorDate: Wed Jun 2 13:26:13 2021 +0200

    Revert "Added vmware disk provisioning types (#187)"
    
    This reverts commit 28316836a30e83fd405517282fdca782965b1b5f.
---
 source/adminguide/service_offerings.rst | 22 +++-------------------
 1 file changed, 3 insertions(+), 19 deletions(-)

diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst
index 444200c..78415e4 100644
--- a/source/adminguide/service_offerings.rst
+++ b/source/adminguide/service_offerings.rst
@@ -187,15 +187,8 @@ 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.
-      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.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+      Local
 
    -  **Compute Offering Type**: The amount of freedom that the end user
       has to customise the compute power that their instance has when using this
@@ -390,16 +383,6 @@ 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
@@ -721,3 +704,4 @@ 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.
+