You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2012/09/25 20:52:07 UTC
[jira] [Created] (VCL-633) Change of vmprofile.vmdisk value can
cause image capture to fail due to insufficient space
Andy Kurth created VCL-633:
------------------------------
Summary: Change of vmprofile.vmdisk value can cause image capture to fail due to insufficient space
Key: VCL-633
URL: https://issues.apache.org/jira/browse/VCL-633
Project: VCL
Issue Type: Bug
Reporter: Andy Kurth
The possible values of vmprofile.vmdisk were changed in 2.3 from local/network to dedicated/shared. Code in VMware.pm and vbox.pm is checking only for "local" when an image is captured in order to determine whether or not to save a copy in both the datastore path and repository or only the repository.
It is assumed that a VM host's local disk is used if vmdisk is local/dedicated and this disk may not have much capacity. A copy is not saved to the datastore path if vmdisk is local/dedicated, the repository path is set, and mounted on the VM host in order to prevent space issues.
When the DB values changed with 2.3, the code was not updated to check for "dedicated". As a result, if the profile is set to "dedicated" a copy of the vmdk is being saved to the datastore path.
All lines which check the value of vmprofile.vmdisk need to be updated to reflect the new values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-633) Change of vmprofile.vmdisk value can
cause image capture to fail due to insufficient space
Posted by "Andy Kurth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VCL-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Kurth updated VCL-633:
---------------------------
Component/s: vcld (backend)
Affects Version/s: 2.3
Fix Version/s: 2.3.1
Assignee: Andy Kurth
> Change of vmprofile.vmdisk value can cause image capture to fail due to insufficient space
> ------------------------------------------------------------------------------------------
>
> Key: VCL-633
> URL: https://issues.apache.org/jira/browse/VCL-633
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.3
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.3.1
>
>
> The possible values of vmprofile.vmdisk were changed in 2.3 from local/network to dedicated/shared. Code in VMware.pm and vbox.pm is checking only for "local" when an image is captured in order to determine whether or not to save a copy in both the datastore path and repository or only the repository.
> It is assumed that a VM host's local disk is used if vmdisk is local/dedicated and this disk may not have much capacity. A copy is not saved to the datastore path if vmdisk is local/dedicated, the repository path is set, and mounted on the VM host in order to prevent space issues.
> When the DB values changed with 2.3, the code was not updated to check for "dedicated". As a result, if the profile is set to "dedicated" a copy of the vmdk is being saved to the datastore path.
> All lines which check the value of vmprofile.vmdisk need to be updated to reflect the new values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira