b485acf8ee
Fixed upgrade bug related with the fact that some db upgrade steps were missed in 2.2.0/2.2.1 to 2.2.2 db upgrade
2011-05-19 15:25:58 -07:00
6fbc65b66c
Fixed bunch of db upgrade bugs.
2011-05-18 17:36:51 -07:00
c0256faa10
Added upgrade from 224 to 225
2011-05-17 16:39:07 -07:00
629140af2d
bug 9873: create default security group for the default admin
...
status 9873: resolved fixed
Conflicts:
setup/db/create-schema.sql
2011-05-17 15:13:48 -07:00
a6b2d67b98
propagated bb04d0184ea2d713cf211618b53c56c33dbefb87
2011-05-16 16:35:20 -07:00
e442a0888f
bug 9868: display help just once if wrong option is specified
...
status 9868: resolved fixed
2011-05-13 14:16:26 -07:00
52886155f1
Small fix to script that stop/starts system vms: added -m option (the host we send stop* api requests to); defaulted to localhost if not specified.
2011-05-12 09:51:14 -07:00
bb28d97423
Added helper script for stopping/starting all system vms
2011-05-11 11:01:21 -07:00
950b373d40
bug 9807: insert hypervisor.list config value as a part of db upgrade
...
status 9807: resolved fixed
2011-05-09 15:49:35 -07:00
4ae9fa8ad4
DB upgrade - update LVM storage with correct cluster id
2011-05-06 17:49:09 -07:00
66d6e1259a
bug 9740: fixed DB upgrade for Direct Tagged networks in Advance zone
...
status 9740: resolved fixed
2011-05-05 09:28:15 -07:00
04a344ce2a
Fixed bunch of DB upgrade bugs related with the fact that DB was manually upated in 2.1.x setup (some records were deleted from the DB)
2011-05-04 17:34:36 -07:00
40bd77525f
bug 9734: update op_ha_work table in mysql file instead of java code
...
status 9734: resolved fixed
2011-05-04 15:34:50 -07:00
c1cb1af320
bug 9690: DB upgrade - dropped unused keys
...
status 9690: resolved fixed
2011-05-03 13:25:43 -07:00
96043d4326
bug 9688: remove orphaned lb/vm mappings as a part of db upgrade (there was a bug in 2.1.x when the LB rule was removed, but mapping was left in the DB)
...
status 9688: resolved fixed
To verify that the rule was removed:
* make sure that there is no record with lb id in load_balancer table
* verify that lb.delete event was generated for this rule
2011-05-02 18:52:50 -07:00
3d963cac1b
revert changes. Can't help direct SG case because it breaks VM stopping after upgrade.
2011-05-02 14:26:29 -07:00
d8a4a5be52
bug 9658: added missing indexes to 2.1.x-2.2.x upgrade files
...
status 9658: resolved fixed
2011-05-01 12:50:26 -07:00
36e4c8625e
bug 9654: db upgrade - set is_security_group_enabled to true for Direct Guest network in Basic zone
...
status 9654: resolved fixed
2011-05-01 11:06:43 -07:00
665b60fcde
bug 9649: fixed up the instance names to be the same
2011-04-29 17:36:14 -07:00
b808604dde
bug 9623: set ha_enable to false for consoleProxy vms and service_offering.
...
status 9623: resolved fixed
Also set ram_size to 1024 for console proxy offering during the upgrade
2011-04-29 11:38:53 -07:00
ed76394b8e
bug 9519 : add index to avoid table locking
2011-04-28 18:41:01 -07:00
3ea4b18311
bug 9638: fixed bunch of DB upgrade bugs
...
status 9638: resolved fixed
2011-04-28 18:18:56 -07:00
5ad7730e06
Modify keys for security groups in java code instead of sql file (need to check if the key exists before dropping it)
2011-04-28 18:18:56 -07:00
a1fa03ab4b
bug 9633: removed schema.level
...
bug 9632: removed direct.attach.security.groups.enabled
2011-04-28 13:49:52 -07:00
71b264322d
1) Don't drop netapp tables during the upgrade.
...
2) SecurityGroups DB upgrade - drop constraints before chaning the name for the network_group table
2011-04-28 13:29:43 -07:00
a4645ac925
bug 9621: dbUpgrade - set reservation strategy to be Create for Guest Nics in Basic zone
...
status 9621: resolved fixed
2011-04-27 22:45:29 -07:00
a1aefef1f2
bug 9618: fixed a upgrade, resouce name is changed to XenServer56FP1Resource
...
status 9618: resolved fixed
2011-04-27 15:59:34 -07:00
f890c49272
bug 9617: fixed snapshot upgrade from 223 to 224
...
status 9617: resolved fixed
2011-04-27 15:52:05 -07:00
e66baae84e
bug 9610: Added VERSION table and related index change
2011-04-27 13:53:19 -07:00
25017382b6
bug 9563: fixed DB upgrade from 2.2.2/2.2.3 to 2.2.4
...
status 9563: resolved fixed
Also added unittest for 2.2.2 to 2.2.4 upgrade
2011-04-23 23:03:45 -07:00
8b0b503861
bug 9556: set ip_type=ip4 for guestVm nics in Basic zone setup
...
status 9556: resolved fixed
2011-04-23 19:56:08 -07:00
eccec4ff11
bug 9541: fix one snapshot DB migrate, one java check and one script typo
...
status 9541: resolved fixed
2011-04-22 12:50:40 -07:00
b8fdbb53b2
bug 9527: name / unique_name confusion
2011-04-20 21:44:22 -07:00
c6e1a26934
Update volumes having destroyed=127 with Destroyed state only after ensuring that corresponding account is removed, or instance is expunged
2011-04-18 13:34:59 -07:00
a43a7993cb
bug 9483: delete records from template_spool_ref if corresponding storage pool doesn't exist any more
...
status 9483: resolved fixed
2011-04-15 17:07:39 -07:00
e7dd2abfe1
bug 9441: cannot change unique_name in vm_template as this will cause template sync to fail
2011-04-15 15:01:45 -07:00
abe460c276
bug 9473: mark all volumes with Destroyed>=1 with state=Destroy
...
status 9473: resolved fixed
2011-04-15 14:05:22 -07:00
c6fee4b718
2.1.x-2.2.x upgrade: in "volumes" table use state=Destroy instead of "Destroyed"
2011-04-15 11:43:47 -07:00
c3c80006ca
bug 9453: domain path is not unique value, removed the constraint added during 2.1.8-2.2.2 upgrade
2011-04-14 16:55:55 -07:00
a76803f5e5
bug 9458: do searchIncludingRemoved when decrement resource count as corresponding domain might be removed already
...
status 9458: resolved fixed
2011-04-14 15:25:37 -07:00
9fa3f92efd
Bug 9438 - [Cloud Stack Upgrade - 2.1.8 to 2.2.4] Secondary Storage VM could not start after stopping it
...
- In the upgrade, new XenServer template entry was added in vm_template having id=100
- However we already have another System VM XenServer template downloaded in the upgrade process that gets different id.
- SSVM could not start because the vm_instance's templateId after the upgrade was set to '100' with the assumption that the Xenserver template with id=100 will be used.
Fix to upgrade script is:
- we should not insert any entry in vm_template table for XenServer systemVM via the upgrade DB script. The latest XenServer template will get added in the upgrade process having name 'routing-xenserver-2.2.4'.
- we should update the system VM's template_id in vminstance table to point to this ''routing-xenserver-2.2.4' template.
2011-04-13 18:09:22 -07:00
6468b66317
bug 9420: update existing user_statistics records with device_id and device_type
...
status 9420: resolved fixed
2011-04-13 14:31:33 -07:00
624d1c0438
DB upgrade: enable securityGroup for all Basic zones
2011-04-12 10:41:59 -07:00
1bfde99462
bug 9347: Adding index and foreign key constraint for upload table for migration from 2.1 to 2.2
...
Status 9347: resolved fixed
2011-04-12 14:24:40 +05:30
5ee6a8757a
bug 9378: db upgrade - update guest_os_id in vm_instance table for system vms.
...
status 9378: resolved fixed
2011-04-11 17:55:40 -07:00
5de4f05a1c
bug 9391: removed source_id, source_type from "volumes" table as we don't use them any more
...
status 9391: resolved fixed
2011-04-11 17:33:38 -07:00
90f79a8211
bug 9398: removed resource_type from volumes table as we no longer use it. Corresponding db upgrade scripts are updated
...
status 9398: resolved fixed
2011-04-11 15:25:34 -07:00
4de0401608
bug 9330: ensure that existing system vms are updated to new xenserver template
2011-04-11 15:22:09 -07:00
e90f03c6c0
bug 9330: add kvm / vmware builtin template definitions
2011-04-11 14:49:45 -07:00
a8487454e8
bug 9330: add kvm / vmware system vm template definitions
2011-04-11 14:35:27 -07:00
alena
Alex Huang
Kelven Yang
anthony
Chiradeep Vittal
prachi
nit