CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone

Description:

    Do not overwrite value of vmware.create.full.clone flag in the
    cloud db if it already exists. This will preserve the configured
    clone creation behaviour across upgrades.
(cherry picked from commit a30a33c14d)

Signed-off-by: animesh <animesh@apache.org>
This commit is contained in:
Vijayendra Bhamidipati 2013-08-28 10:58:02 -07:00 committed by animesh
parent 72a3cbb82e
commit 42e66aa4e6
1 changed files with 6 additions and 1 deletions

View File

@ -403,7 +403,12 @@ 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' , 'true', 'If set to true, creates VMs as full clones on ESX hypervisor');
INSERT INTO `cloud`.`configuration` (category, instance, component, name, value, description)
SELECT tmp.category, tmp.instance, tmp.component, tmp.name, tmp.value, tmp.description FROM
(SELECT 'Advanced' category, 'DEFAULT' instance, 'UserVmManager' component, 'vmware.create.full.clone' name, 'true' value, 'If set to true, creates VMs as full clones on ESX hypervisor' description) tmp
WHERE NOT EXISTS (SELECT 1 FROM `cloud`.`configuration` WHERE name = 'vmware.create.full.clone');
CREATE TABLE `cloud`.`affinity_group` (
`id` bigint unsigned NOT NULL auto_increment,