From 448bfc2d580308baeece1fc54d81e3998324fcb7 Mon Sep 17 00:00:00 2001 From: Vijayendra Bhamidipati Date: Fri, 23 Aug 2013 11:35:05 -0700 Subject: [PATCH] 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. --- setup/db/db/schema-410to420.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup/db/db/schema-410to420.sql b/setup/db/db/schema-410to420.sql index 4a218985c29..57051ffcc3b 100644 --- a/setup/db/db/schema-410to420.sql +++ b/setup/db/db/schema-410to420.sql @@ -403,7 +403,7 @@ CREATE TABLE `cloud`.`user_vm_clone_setting` ( ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'UserVmManager', 'vmware.create.full.clone' , 'false', 'If set to true, creates VMs as full clones on ESX hypervisor'); +INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'UserVmManager', 'vmware.create.full.clone' , 'true', 'If set to true, creates VMs as full clones on ESX hypervisor'); CREATE TABLE `cloud`.`affinity_group` ( `id` bigint unsigned NOT NULL auto_increment,