[
https://issues.apache.org/jira/browse/CLOUDSTACK-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361961#comment-15361961
]
ASF GitHub Bot commented on CLOUDSTACK-9422:
--------------------------------------------
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1602
@syed. The default behavior won't change. The proposed enhancement will add
an ability to control link/full clone deployment of a primary storage level. If
it is not defined there a current value of a global setting will be applied. A
global configuration setting vmware.create.full.clone is already in ACS
starting from version 4.2 if I am not mistaken.
> Granular VMware vm's creation as full clones on HV
> --------------------------------------------------
>
> Key: CLOUDSTACK-9422
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9422
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
>
> h3. Introduction
> For VMware, It is possible to decide creating VMs as full clones on ESX HV,
> adjusting {{vmware.create.full.clone}} global setting. We would like to
> introduce this property as a primary storage detail, and use its value
> instead of global setting's value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
