5c8d968eea
Remove the extra drop sql line
...
This would result in 3.0.1 to 3.0.2 upgrade failed, due to index not found.
2012-05-10 14:43:07 -07:00
f27a0a0386
Mark local storages as removed when they have no ref in storage_pool_host_ref
...
Conflicts:
setup/db/db/schema-301to302.sql
2012-04-27 13:15:58 -07:00
12255db122
CS-14629: added missing global config variables
...
Conflicts:
setup/db/db/schema-301to302.sql
2012-04-25 13:43:40 -07:00
319d4c5cfd
Catch all exceptions when change engine and row_format - can fail when table is full. Just skip as its not a critical fix
2012-04-24 15:49:14 -07:00
47a1527719
CS-14591: added XenServer 6.0.2 and VmWare 5.0 as supported hypervisors to fresh 3.0.2 and to the 3.0.1-3.0.2 db upgrade
...
Conflicts:
setup/db/db/schema-301to302.sql
2012-04-23 11:19:24 -07:00
74aa4974c0
CS-14589: change engine and row_format for op_lock op_nwgrp_work during the db upgrade
2012-04-23 10:55:15 -07:00
d51d018a1b
CS-14553: db upgrade - for default network offerings:
...
1) Change display text to match fresh 3.0.2
2) Delete lb service for the offerings using VR as a provider and not having source nat service
2012-04-18 17:10:41 -07:00
419faa1f90
Revert "Fix foreign key "fk_domain_router__element_id" in the upgrade"
...
This reverts commit 52e334cefc
2012-04-11 17:37:32 -07:00
2530ea17dd
CS-14429 Cloud db schema differences between fresh installed 3.0.2 & upgraded 3.0.2
...
do check befor droping index i_host__allocation_state`(`allocation_state`)
2012-04-11 17:25:15 -07:00
2252d6db1c
Fix foreign key "fk_domain_router__element_id" in the upgrade
2012-04-11 16:50:38 -07:00
3e968d2b9d
CS-14429 Cloud db schema differences between fresh installed 3.0.2 & upgraded 3.0.2
...
drop index i_host__allocation_state`(`allocation_state`)
2012-04-11 16:42:41 -07:00
cd774c9fab
Db upgrade path for 3.0.2 to 3.0.3
2012-04-09 15:50:23 -07:00
b7f5bc099d
bug 14622: introduced ha tagging for host
...
status 14622: resolved fixed
2012-04-09 15:17:13 -07:00
d3bca8df8f
bug 14615: deployVm can work 2 diff ways now: 1) Default way - create and start the vm. 2) Create the vm without starting it. Note that vm's volumes stay in Allocated state -not created on the backend till the point where vm starts
...
status 14615: resolved fixed
2012-04-06 11:30:26 -07:00
0bd655f79b
bug 14539: 1) introduced 2 new config parameters defining default offerings for ssvm and cpvm - consoleproxy.service.offering and secstorage.service.offering
...
2) Added new api - changeServiceForSystemVm - to support service offering upgrade for system vms
3) Removed global config parameters that are not in use anymore: consoleproxy.ram.size, consoleproxy.cpu.mhz, secstorage.vm.ram.size, secstorage.vm.cpu.mhz
2012-04-03 10:51:35 -07:00
Sheng Yang
Alena Prokharchyk
frank