Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 24 Aug 2013 01:07:51 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12664301.1376892653254.26971.1377306471766@arcas>
In-Reply-To: <JIRA.12664301.1376892653254@arcas>
References: <JIRA.12664301.1376892653254@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-4390) Using full-clone by default
 for VMware deployment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749214#comment-13749214 ] 

ASF subversion and git services commented on CLOUDSTACK-4390:
-------------------------------------------------------------

Commit 448bfc2d580308baeece1fc54d81e3998324fcb7 in branch refs/heads/4.2-forward from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=448bfc2 ]

CLOUDSTACK-4390: Using full-clone by default for VMware deployment

Description:
    Setting default setting of vmware.use.full.clone flag
    to true in sql upgrade script else global config will be
    overwritten back to false.

                
> Using full-clone by default for VMware deployment
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-4390
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4390
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Kelven Yang
>            Assignee: Kelven Yang
>            Priority: Critical
>
> To better integrate with VMware features like storage live migration,  fully utilize third-party integrations from vSphere eco-system, deploy VM in full-clone mode by default

--
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