Feature #14716
closed
Provision thick disks from thin templates
Added by Bryan Kearney over 8 years ago.
Updated over 6 years ago.
Category:
Compute resources - VMware
|
|
Description
To add functionality of deploying of VMware VMs via lazy zero disks
3. What is the nature and description of the request?
To add functionality of deploying of VMware VMs via lazy zero disks
4. Why does the customer need this? (List the business requirements here)
To minimize overhead on the storage side because of all the writes and it would speed up provisioning part
5. How would the customer like to achieve this? (List the functional requirements here)
- Add Lazy Zero check mark in Storage part of VMware provisioning.
- Bugzilla link set to 1322481
- Status changed from New to Need more information
Isn't this just ensuring eager zero is not checked?
Dominic Cleal wrote:
Isn't this just ensuring eager zero is not checked?
indeed. any reaction yet?
Michael Moll wrote:
Dominic Cleal wrote:
Isn't this just ensuring eager zero is not checked?
indeed. any reaction yet?
What the vmware guys wanted to do is saving the templates as thin provisioned (and therefore save space and distribution times with smaller images) and then during the deployment of a virtual machine ensure that it's deployed with lazy zeroed disk.
Right now what's happening is:
If template is saved with the disk as thin provisioned the cloned host is also thin provisioned.
If we add an extra disk in the foreman instance and untick the thin provision checkbox it's as you say, the disk is created with lazy zero. This is however only applicable for additional disk and not for the current use case above with pre-created templates.
- Status changed from Need more information to Ready For Testing
- Assignee set to Shimon Shtein
- Pull request https://github.com/theforeman/foreman/pull/4241 added
- Target version set to 1.11.3
- Subject changed from Possibility to lazy zero disks to Provision thick disks from thin templates
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 209
- Has duplicate Bug #18928: Created VM disk not respect the provisionning type choosed. thin provisionning is always used. Eager zero ignored added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by 
Updated by