Feature #2393
VMFS datastore clone should maintain the same format when cloning
| Status: | Closed | Start date: | 10/18/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Drivers - Storage | |||
| Target version: | Release 4.4 | |||
| Resolution: | fixed | Pull request: |
Description
VMFS clone does not specify the format the target image is going to have and changes to thin when using NFS or lazy zeroed when using VMFS. The format should be the same as the source image.
Associated revisions
Feature #2393: Add new CLONE_FSTYPE for images, supported in VMFS datastores ATM
Feature #2393: Fix for empty CLONE_FSTYPE in vmfs clone (no -d left behind)
History
#1
Updated by OpenNebula Systems Support Team over 7 years ago
- Tracker changed from Request to Feature
- Status changed from Pending to New
- Target version set to Release 4.4
#2
Updated by Tino Vázquez over 7 years ago
- Status changed from New to Closed
- Assignee set to Tino Vázquez
- % Done changed from 0 to 100
- Resolution set to fixed
A new attributes for IMAGES in vmfs datastores is used to drive the format of the target image of the clone operation. The attribute is called CLONE_FSTPYE. Docu updated