Skip to content

Added vmware disk provisioning types #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sureshanaparti merged 1 commit into from
Jul 19, 2021
Merged

Added vmware disk provisioning types #217

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 19 additions & 3 deletions source/adminguide/service_offerings.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.