incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-1312) Fix rolling upgrades from 4.0 to 4.1 in 4.1 release, fix db schemas to be same as 4.0
Date Wed, 20 Feb 2013 10:27:12 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohit Yadav resolved CLOUDSTACK-1312.
-------------------------------------

    Resolution: Fixed

The difference is just drop table rules now. I tested 4.1 branch by deploying the database
which upgraded the db from 4.0.0 to 4.1.0 when mgmt server started, next I was able to deploy
a zone and start a vm.

Following is the diff between 4.0.0 and 4.1.0;

--- ../create-schema.sql	2013-02-20 14:47:30.000000000 +0530
+++ setup/db/create-schema.sql	2013-02-20 15:51:01.000000000 +0530
@@ -141,11 +141,61 @@
 DROP TABLE IF EXISTS `cloud`.`cluster_vsm_map`;
 DROP TABLE IF EXISTS `cloud`.`virtual_supervisor_module`;
 DROP TABLE IF EXISTS `cloud`.`port_profile`;
+DROP TABLE IF EXISTS `cloud`.`region`;
 DROP TABLE IF EXISTS `cloud`.`s2s_customer_gateway`;
 DROP TABLE IF EXISTS `cloud`.`s2s_vpn_gateway`;
 DROP TABLE IF EXISTS `cloud`.`s2s_vpn_connection`;
-DROP TABLE IF EXISTS `cloud`,`external_nicira_nvp_devices`;
-DROP TABLE IF EXISTS `cloud`,`nicira_nvp_nic_map`;
+DROP TABLE IF EXISTS `cloud`.`external_nicira_nvp_devices`;
+DROP TABLE IF EXISTS `cloud`.`nicira_nvp_nic_map`;
+DROP TABLE IF EXISTS `cloud`.`s3`;
+DROP TABLE IF EXISTS `cloud`.`template_s3_ref`;
+DROP TABLE IF EXISTS `cloud`.`nicira_nvp_router_map`;
+DROP TABLE IF EXISTS `cloud`.`external_bigswitch_vns_devices`;
+DROP TABLE IF EXISTS `cloud`.`autoscale_vmgroup_policy_map`;
+DROP TABLE IF EXISTS `cloud`.`autoscale_policy_condition_map`;
+DROP TABLE IF EXISTS `cloud`.`autoscale_vmgroups`;
+DROP TABLE IF EXISTS `cloud`.`autoscale_vmprofiles`;
+DROP TABLE IF EXISTS `cloud`.`autoscale_policies`;
+DROP TABLE IF EXISTS `cloud`.`counter`;
+DROP TABLE IF EXISTS `cloud`.`conditions`;
+DROP TABLE IF EXISTS `cloud`.`inline_load_balancer_nic_map`;
+DROP TABLE IF EXISTS `cloud`.`cmd_exec_log`;
+DROP TABLE IF EXISTS `cloud`.`keystore`;
+DROP TABLE IF EXISTS `cloud`.`swift`;
+DROP TABLE IF EXISTS `cloud`.`project_account`;
+DROP TABLE IF EXISTS `cloud`.`project_invitations`;
+DROP TABLE IF EXISTS `cloud`.`elastic_lb_vm_map`;
+DROP TABLE IF EXISTS `cloud`.`ntwk_offering_service_map`;
+DROP TABLE IF EXISTS `cloud`.`ntwk_service_map`;
+DROP TABLE IF EXISTS `cloud`.`external_load_balancer_devices`;
+DROP TABLE IF EXISTS `cloud`.`external_firewall_devices`;
+DROP TABLE IF EXISTS `cloud`.`network_external_lb_device_map`;
+DROP TABLE IF EXISTS `cloud`.`network_external_firewall_device_map`;
+DROP TABLE IF EXISTS `cloud`.`virtual_router_providers`;
+DROP TABLE IF EXISTS `cloud`.`op_user_stats_log`;
+DROP TABLE IF EXISTS `cloud`.`netscaler_pod_ref`;
+DROP TABLE IF EXISTS `cloud`.`mshost_peer`;
+DROP TABLE IF EXISTS `cloud`.`vm_template_details`;
+DROP TABLE IF EXISTS `cloud`.`hypervisor_capabilities`;
+DROP TABLE IF EXISTS `cloud`.`template_swift_ref`;
+DROP TABLE IF EXISTS `cloud`.`account_details`;
+DROP TABLE IF EXISTS `cloud`.`vpc`;
+DROP TABLE IF EXISTS `cloud`.`vpc_offerings`;
+DROP TABLE IF EXISTS `cloud`.`vpc_offering_service_map`;
+DROP TABLE IF EXISTS `cloud`.`vpc_gateways`;
+DROP TABLE IF EXISTS `cloud`.`router_network_ref`;
+DROP TABLE IF EXISTS `cloud`.`private_ip_address`;
+DROP TABLE IF EXISTS `cloud`.`static_routes`;
+DROP TABLE IF EXISTS `cloud`.`resource_tags`;
+DROP TABLE IF EXISTS `cloud`.`primary_data_store_provider`;
+DROP TABLE IF EXISTS `cloud`.`image_data_store_provider`;
+DROP TABLE IF EXISTS `cloud`.`image_data_store`;
+DROP TABLE IF EXISTS `cloud`.`vm_compute_tags`;
+DROP TABLE IF EXISTS `cloud`.`vm_root_disk_tags`;
+DROP TABLE IF EXISTS `cloud`.`vm_network_map`;
+DROP TABLE IF EXISTS `cloud`.`netapp_volume`;
+DROP TABLE IF EXISTS `cloud`.`netapp_pool`;
+DROP TABLE IF EXISTS `cloud`.`netapp_lun`;
 
 CREATE TABLE `cloud`.`version` (
   `id` bigint unsigned NOT NULL UNIQUE AUTO_INCREMENT COMMENT 'id',
@@ -156,7 +206,8 @@
   INDEX `i_version__version`(`version`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
  

                
> Fix rolling upgrades from 4.0 to 4.1 in 4.1 release, fix db schemas to be same as 4.0
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1312
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1312
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.1.0
>
>
> For 4.1:
> - We stick to major db version as 4.0, create-schema is not touched
> unless it's a major version. So, next change is to be done only for
> 5.0.
> - We move out any 4.1 changes to 4041 upgrade sql file and have a
> upgrade path (a upgrading logic/class).

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

Mime
View raw message