Feature #14716
closed
Provision thick disks from thin templates
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.
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Need more information
Isn't this just ensuring eager zero is not checked?
Updated by Anonymous over 8 years ago
Dominic Cleal wrote:
Isn't this just ensuring eager zero is not checked?
indeed. any reaction yet?
Updated by Bryan Kearney over 8 years ago
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.
Updated by Shimon Shtein almost 8 years ago
It looks like it's an issue in fog-vsphere. Opened an issue there: https://github.com/fog/fog-vsphere/issues/64
Updated by The Foreman Bot almost 8 years ago
- 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
Updated by
Updated by Shimon Shtein almost 8 years ago
- Subject changed from Possibility to lazy zero disks to Provision thick disks from thin templates
Updated by Shimon Shtein almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 6d4420bac973a0119a126a0dcdbde9e4980081e1.
Updated by Dominic Cleal almost 8 years ago
- Translation missing: en.field_release set to 209
Updated by Dominic Cleal over 7 years ago
- Has duplicate Bug #18928: Created VM disk not respect the provisionning type choosed. thin provisionning is always used. Eager zero ignored added