Feature #14716

Provision thick disks from thin templates

Added by Bryan Kearney about 1 year ago. Updated 4 months ago.

Status:Closed
Priority:Normal
Assigned To:Shimon Shtein
Category:Compute resources - VMware
Target version:Team Ivan Iteration 10
Difficulty: Bugzilla link:1322481
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4241
Story points-
Velocity based estimate-
Release1.15.0Release relationshipAuto

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.


Related issues

Duplicated by Foreman - Bug #18928: Created VM disk not respect the provisionning type choose... Duplicate 03/16/2017

Associated revisions

Revision 6d4420ba
Added by Shimon Shtein 5 months ago

Fixes #14716 - Added option to transform thin template to thick

Unfortunately, it's a single setting for all disks - you can't choose
which disks (inherited from templat) will be thin and which not.

For new disks, the logic remains the same - "thin" flag would be used.

History

#1 Updated by Bryan Kearney about 1 year ago

  • Bugzilla link set to 1322481

#2 Updated by Dominic Cleal about 1 year ago

  • Status changed from New to Need more information

Isn't this just ensuring eager zero is not checked?

#3 Updated by Michael Moll about 1 year ago

Dominic Cleal wrote:

Isn't this just ensuring eager zero is not checked?

indeed. any reaction yet?

#4 Updated by Bryan Kearney about 1 year 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.

#5 Updated by Shimon Shtein 6 months ago

It looks like it's an issue in fog-vsphere. Opened an issue there: https://github.com/fog/fog-vsphere/issues/64

#6 Updated by The Foreman Bot 5 months ago

  • Status changed from Need more information to Ready For Testing
  • Assigned To set to Shimon Shtein
  • Pull request https://github.com/theforeman/foreman/pull/4241 added

#7 Updated by Ivan Necas 5 months ago

  • Target version set to Team Ivan Iteration 10

#8 Updated by Shimon Shtein 5 months ago

  • Subject changed from Possibility to lazy zero disks to Provision thick disks from thin templates

#9 Updated by Shimon Shtein 5 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#10 Updated by Dominic Cleal 5 months ago

  • Release set to 1.15.0

#11 Updated by Dominic Cleal 4 months ago

  • Duplicated by 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