[
https://issues.apache.org/jira/browse/CLOUDSTACK-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529103#comment-15529103
]
ASF subversion and git services commented on CLOUDSTACK-9422:
-------------------------------------------------------------
Commit 3a82636b9076d18d8d04c8bbd660f279a7de55b7 in cloudstack's branch
refs/heads/4.9-bountycastle-daan from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3a82636 ]
Merge pull request #1602 from nvazquez/clonegranular
CLOUDSTACK-9422: Granular 'vmware.create.full.clone' as Primary Storage
setting### 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.
We propose introducing `fullCloneFlag` on `PrimaryDataStoreTO` sent on
`CopyCommand`. This way we can reconfigure `VmwareStorageProcessor` and
`VmwareStorageSubsystemCommandHandler` similar as it was done for `nfsVersion`
but refactoring it to be more general.
* pr/1602:
CLOUDSTACK-9422: Granular VMware vms creation as full clones on HV
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> 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)
