mirror of
https://github.com/apache/cloudstack.git
synced 2025-11-03 04:12:31 +01:00
CLOUDSTACK-4079: Made a change to make sure we are setting the hypervisor capabilities for storage motion to true.
If an upgrade is taking place from an older setup which supported a hypervisor but not storage motion on that hypervisor, the upgraded setup will not have the storage motion field enabled. Enabled it explicitly.
This commit is contained in:
parent
506f2a4b94
commit
7b5f4bd99c
@ -36,6 +36,8 @@ INSERT IGNORE INTO `cloud`.`hypervisor_capabilities`(uuid, hypervisor_type, hype
|
||||
INSERT IGNORE INTO `cloud`.`hypervisor_capabilities`(uuid, hypervisor_type, hypervisor_version, max_guests_limit, security_group_enabled, max_hosts_per_cluster) VALUES (UUID(), 'VMware', '5.1', 128, 0, 32);
|
||||
UPDATE `cloud`.`hypervisor_capabilities` SET `storage_motion_supported`=true WHERE `hypervisor_type`='VMware' AND `hypervisor_version`='5.1';
|
||||
UPDATE `cloud`.`hypervisor_capabilities` SET `storage_motion_supported`=true WHERE `hypervisor_type`='VMware' AND `hypervisor_version`='5.0';
|
||||
UPDATE `cloud`.`hypervisor_capabilities` SET `storage_motion_supported`=true WHERE `hypervisor_type`='XenServer' AND `hypervisor_version`='6.1.0';
|
||||
UPDATE `cloud`.`hypervisor_capabilities` SET `storage_motion_supported`=true WHERE `hypervisor_type`='XenServer' AND `hypervisor_version`='6.2.0';
|
||||
DELETE FROM `cloud`.`configuration` where name='vmware.percluster.host.max';
|
||||
DELETE FROM `cloud`.`configuration` where name='router.template.id';
|
||||
DELETE FROM `cloud`.`configuration` where name='swift.enable';
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user