CLOUDSTACK-3648: 3.0.6 to ASF 4.2 Upgrade: "hypervisor_capabilites" table has duplicate VMware 5.1 entries on the Upgraded Setup

Added a unique constraint on "hypervisor_capabilities" table based on hypervisor type and version
This commit is contained in:
Koushik Das 2013-07-19 12:12:51 +05:30
parent 12c711cef7
commit 89237554e9
1 changed files with 4 additions and 1 deletions

View File

@ -22,6 +22,9 @@
-- Disable foreign key checking
SET foreign_key_checks = 0;
-- All new inserts to the hypervisor_capabilities table should be after this
ALTER TABLE `cloud`.`hypervisor_capabilities` ADD CONSTRAINT `uc_hypervisor` UNIQUE (`hypervisor_type`, `hypervisor_version`);
ALTER TABLE `cloud`.`hypervisor_capabilities` ADD COLUMN `max_hosts_per_cluster` int unsigned DEFAULT NULL COMMENT 'Max. hosts in cluster supported by hypervisor';
ALTER TABLE `cloud`.`hypervisor_capabilities` ADD COLUMN `storage_motion_supported` int(1) unsigned DEFAULT 0 COMMENT 'Is storage motion supported';
UPDATE `cloud`.`hypervisor_capabilities` SET `max_hosts_per_cluster`=32 WHERE `hypervisor_type`='VMware';
@ -2243,4 +2246,4 @@ CREATE VIEW `cloud`.`project_view` AS
ALTER TABLE `cloud`.`sync_queue` MODIFY `queue_size` smallint(6) NOT NULL DEFAULT '0' COMMENT 'number of items being processed by the queue';
ALTER TABLE `cloud`.`sync_queue` MODIFY `queue_size_limit` smallint(6) NOT NULL DEFAULT '1' COMMENT 'max number of items the queue can process concurrently';
ALTER TABLE `cloud`.`sync_queue` MODIFY `queue_size_limit` smallint(6) NOT NULL DEFAULT '1' COMMENT 'max number of items the queue can process concurrently';