6fe45923f6
Added upgrade path from 225 to 226
2011-06-06 12:43:13 -07:00
859ea3c5d9
bug 10166: drop account_id/domain_id fields (if exist) in domain_router table
...
status 10166: resolved fixed
2011-06-06 12:38:34 -07:00
49650f3eb6
host_address in storage_pool should not have gotten the change to char(40)
2011-06-02 09:51:17 -07:00
cd99334d4f
bug 9961: use 'firewall_rules'.'is_static_nat' field to make a decision about what version to return - 221 or 222
...
status 9961: resolved fixed
2011-05-21 12:40:30 -07:00
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
c2c0d0192a
bug 9934: use another way to check if the foreign key already exists
...
status 9934: resolved fixed
2011-05-18 20:38:27 -07:00
6fbc65b66c
Fixed bunch of db upgrade bugs.
2011-05-18 17:36:51 -07:00
b7c68d1dc5
Added upgrade path from 224 to 225 to DbUpgradeChecker
2011-05-17 21:05:02 -07:00
c0256faa10
Added upgrade from 224 to 225
2011-05-17 16:39:07 -07:00
2b04360566
bug 9891: update network_id for ExternalFirewall and ExternalLoadBalancer device_types
...
status 9891: resolved fixed
2011-05-18 00:52:14 +05:30
b0cc754c85
bug 9891: update network_id for ExternalFirewall and ExternalLoadBalancer device_types
...
status 9891: resolved fixed
2011-05-17 19:55:56 +05:30
58ec16b02d
2.2.2 to 2.2.4 upgrade fix
2011-05-16 17:01:21 -07:00
a6b2d67b98
propagated bb04d0184ea2d713cf211618b53c56c33dbefb87
2011-05-16 16:35:20 -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
4128c82018
DB upgrade: Reverting partial commit
2011-05-04 18:24:49 -07:00
ddb64dd196
Removed unused logging
2011-05-04 18:20:24 -07:00
a9477be053
bug 9738: DB upgrade - fixed NPE happening during events migration
...
status 9738: resolved fixed
2011-05-04 18:18:42 -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
e7033702be
bug 9734: remove records having non-existing hostId from op_ha_work table
...
status 9734: resolved fixed
2011-05-04 13:42:46 -07:00
bac0fdb87f
DB upgrade: respect domain hierarchy when update resource_count for domain during the upgrade
2011-05-04 11:56:07 -07:00
9a983d3bd8
bug 9720: 2.1.x to 2.2.x upgrade: need to create Domain level records in resource_count table
...
status 9720: resolved fixed
During DB upgrade evalute per domain resource counts and populate resource_count table
2011-05-04 19:28:27 +05:30
85541705b6
bug 9722: db upgrade - when upgrade user_statistics, skip ExternalFirewall/ExternalLb records
...
status 9722: resolved fixed
2011-05-03 18:09:42 -07:00
8f198b69f8
bug 9693: generate usage event when release Direct ip address.
...
status 9693: resolved fixed
2 more fixes with this commit:
* bug 9692 is fixed - we don't increment resource count when Direct ip address is allocated.
* as a part of 2.2.2->2.2.4 upgrade resource_count for public_ip records is recalculated - count only Virtual Ip addresses
2011-05-03 17:33:47 -07:00
3daa9b0137
bug 9686,9676,9677: Create usage events for existing resources for port forwarding, load balancer and network offering usage
...
status 9686,9676,9677: resolved fixed
2011-05-03 20:03:29 +05:30
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
5b28d4bf10
bug 9683: DB upgrade - generate usage_event for source nat ip addresses
...
status 9683: resolved fixed
2011-05-02 15:54:03 -07:00
3a5b185972
bug 9675: Usage DB upgrade - set missing fields for snapshot.create/snapshot.delete events
...
status 9675: resolved fixed
2011-05-02 15:17:00 -07:00
14e857a978
bug 9674: Usage db upgrade - set resource_name for volume.create/volume.delete usage events
...
status 9674: resolved fixed
2011-05-02 14:29:54 -07:00
175fc53b53
bug 9672: usage db upgrade - set resource_id for NET.IPASSIGN/RELEASE events
...
status 9672: resolved fixed
2011-05-02 14:15:36 -07:00
a225eb3c0e
bug 9682: DB upgrade - create vm.destroy event in usage_events table
...
status 9682: resolved fixed
2011-05-02 13:54:33 -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
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
14d280634e
Added a check for duplicate public networks.
2011-04-28 16:06:17 -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
a35088d545
Fixed upgrade from 2.1.9 to 2.2.x
2011-04-27 21:27:50 -07:00
a9dded4d27
bug 9622: update mode for nics
...
status 9622: resolved fixed
2011-04-27 21:03:20 -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
d5c7258b71
bug 9597: Fixed the recreatable problem. Also added the 2.2.1 upgrade step
2011-04-26 15:43:43 -07:00
2b3c3cf949
Recalculate and update host used capacity (mem & cpu) in upgrade (2.1.x to 2.2.y)
2011-04-26 12:09:59 -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
6f76104a0e
DB upgrade: use is_static_nat field to distinguish between 2.2.1 and 2.2.2 versions
2011-04-23 21:23:07 -07:00
eb7a158e72
bug 9555: db upgrade for Basic zone - set default nic for the domR
...
status 9555: resolved fixed
2011-04-23 20:03:33 -07:00
5706041ef7
Manual merge of Bug 9539 - cpu.overprovisioning.factor does not work
...
Partial Changes:
- Changed host allocators/planner to use cpu.overprovisioning.factor
- Removed following: while adding a new host, we were setting the total_cpu in op_host_capacity to be actual_cpu * cpu.overprovisioning.factor. Now we set it to actual_cpu.
- ListCapacities response now calculates the total CPU as actual * cpu.overprovisioning.factor (This change does not add anything new - listCapacities was pulling total CPU from op_host_capacity DB earlier which had the cpu.overprovisioning.factor applied already. Now we need to apply it over the DB entry.)
- HostResponse has a new field: 'cpuWithOverprovisioning' that returns the cpu after applying the cpu.overprovisioning.factor
- Db Upgrade 222 to 224 now updates the total_cpu in op_host_capacity to be the actual_cpu for each Routing host.
Conflicts:
server/src/com/cloud/agent/manager/AgentManagerImpl.java
server/src/com/cloud/api/ApiDBUtils.java
server/src/com/cloud/api/ApiResponseHelper.java
server/src/com/cloud/deploy/BareMetalPlanner.java
server/src/com/cloud/server/ManagementServerImpl.java
2011-04-22 18:54:16 -07:00
b7a89f2229
bug 9493: fixed the bug in Basic zone when nic_count was updated incorrectly due to multiple domRs per network
...
status 9493: resolved fixed
2011-04-18 16:49:12 -07:00
4c53dc8d46
Throw server api exception with correct error code
2011-04-18 15:16:06 -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
9c8ff68ca7
Added more logging to DB upgrade code
2011-04-18 11:39:44 -07:00
alena
Alex Huang
kishan
Murali Reddy
keshav
anthony
Kelven Yang
prachi