fc784f1530
Bug 9585 - Existing Data Disk is being destroyed and recreated on Stop and Start of a User VM.
...
Changes:
- When the ROOT volume of a VM is found to be READY, changed planner to reuse the pool for every volume(root or data) that is READY and that has a pool not in maintenance and not in avoid state
- If ROOT volume is not ready, we dont care about the DATA disk. Both would get re-allocated.
- When a pool is reused for a ready volume, Planner does not call storagepool allocators. And such volumes are not assigned a pool in the deployment destination returned by the planner. Accordingly StorageManager :: prepare method wont recreate these volumes since they are not mentioned in the destination.
2011-04-27 11:56:14 -07:00
c909057b90
bug 9595 : Negative resource counts exception when destroying VM account
...
Avoiding double decrement for same VM instance
2011-04-27 23:40:04 +05:30
b8d9513309
bug 9605: exclude virtual interfaces when searching for cidrs
2011-04-26 17:52:31 -07:00
1bd0496bd0
Apply nic profile to nic: don't set reservationStrategy for DB object when it's value is NULL
2011-04-26 17:49:05 -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
f6258dae08
bug 9445: Signal alert for the host if a primary storage pool was unavailable on that host
2011-04-26 15:14:55 -07:00
bb0c0234bc
bug 9578: when deploy dhcp in Basic zone, put pod information to deploymentPlan
...
status 9578: resolved fixed
2011-04-26 14:41:21 -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
ee598d44c5
Bug 9548 [Cloud Stack Upgrade - 2.1.8 to 2.2.4] System VM's Volumes Recreation is not happening on an event of New Volume creation Failures
...
Changes:
- Reason was that the old volume's templateId was being updated before volume creation was attempted. So on the retry, we dint find a difference in volume's templateId and VM's templateId and did not enter the recreation logic.
- Fix is to update the new volume's templateId with the VM's templateId while creating the new volume. The old volume's templateId stays the same and the volume is marked as 'Destroy' when a new volume is created.
2011-04-26 11:55:05 -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
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
c8f4dacb0a
bug 9550: get storagePool to Host mappings before doing processDisconnect because these references are being deleted as a part of processDisconnect call.
...
status 9550: resolved fixed
2011-04-23 18:34:39 -07:00
074e143986
Manually Merged from master the remaining changes for Bug 9539 - cpu.overprovisioning.factor does not work
2011-04-22 18:58:00 -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
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
b219d3e83e
cluster guid is set up when old host reconnect happens after upgrade, prohibit adding host to the cluster before guid is etup
2011-04-21 16:01:04 -07:00
71f968a3e1
bug 9282: set cluster guid if it is null
...
status 9282: resolved fixed
2011-04-21 15:41:54 -07:00
d1650c6e60
Bug 9273: resource count going -ve
...
adding addtional check that ensure we decrease the count in advanceStart only on new vm creation
2011-04-22 01:37:45 +05:30
c8d5ef8c29
Merge branch '2.2.4' of ssh://git.cloud.com/var/lib/git/cloudstack-oss into 2.2.4
2011-04-21 09:59:48 +05:30
b979b782c1
bug 9487: race condition in taking ownership
2011-04-21 09:20:50 +05:30
e5286339f1
bug 9521: fixed NPE in finalizeCommandsOnStart() method by adding vm's nic to vm profile during the vm to vmProfile conversion.
...
status 9521: resolved fixed
2011-04-20 16:16:27 -07:00
48eebe8e7a
bug 9503: race condition in taking ownership of a Host when a Management server is restarted
...
status 9503: resolved fixed
2011-04-20 16:37:12 +05:30
a99f925de1
bug 9383: createStaticNat rule - allow opening the same port for tcp/udp traffic
...
status 9383: resolved fixed
2011-04-18 18:18:44 -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
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
b897508c03
bug 9468: DiskOfferings are now sorted by created date to keep consistent with other objects returned in CloudStack.
...
Merge from master
2011-04-15 14:27:46 -07:00
fcdf791645
bug 9475: don't update vlan in "networks" tab for non-implemented guest networks
...
status 9475: resolved fixed
2011-04-15 12:00:41 -07:00
5778204e54
Fixed Db upgrade from 2.1.9 to 2.2.2 which wasn't supported before.
2011-04-15 10:17:08 -07:00
c2455017e0
Fixed logging for remote access vpn code
2011-04-15 09:58:48 -07:00
234917780e
218-222 upgrade - no need to update user statistics with deviceId if account doesn't own any domRs
2011-04-15 09:45:19 -07:00
ce984ce89c
bug 9453: Fixed PF rules upgrade.
...
status 9453: resolved fixed
1) Problem #1 was that in 2.1.x there was a bug when we didn't delete pf rules for expunged vms. These kind of rules will be ignored during the db upgrade
2) Problem #2 . We didn't trim the spaces for PF/LB ports in 2.1.x, and DB upgrade code was failing because of that.
2011-04-14 20:35:34 -07:00
fba10b1cb8
bug 9461: don't update user_statistics with the network id if the domR is already expunged
...
status 9461: resolved fixed
2011-04-14 17:53:38 -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
8b9fc424d5
bug 8532,8755: don't create multiple HA work if there already has one of HAwork of this VM is created, but not finished
...
status 8532: resolved fixed
status 8755: resolved fixed
2011-04-14 16:55:06 -04: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
c6018bdc60
bug 9455: when host is disconnected, also remove entry in storage_pool_host_ref
...
status 9455: resolved fixed
2011-04-14 14:34:32 -07:00
78aad72ffb
bug 9407: lock network when do deployDomR/deployDhcp to avoid 2 network elements start for the same network
...
status 9407: resolved fixed
2011-04-14 13:19:04 -07:00
21c936ab15
bug 9411:
...
1. adding storage pool fails, remove the entry in DB
2. in introduce SR, create pbd for master host
status 9411: resolved fixed
2011-04-14 11:16:45 -07:00
2ab9238ae7
Bug 9440: we specify the wrong disk size when attaching storage device with custom size offering
...
wrong usage of volume size which is in bytes for setting the size of disk offering which in MB
2011-04-14 21:25:23 +05:30
7b0f95a466
bug 9422: added rows in op_networks table to correspond to the rows in networks table
2011-04-14 03:53:51 -07:00
256517f1c3
bug 9422: added rows in op_networks table to correspond to the rows in networks table
2011-04-14 03:17:55 -07:00
3f4c5225dd
fixed transaction usage
2011-04-13 19:35:13 -07:00
fede78bea8
More changes for Bug 9438 - [Cloud Stack Upgrade - 2.1.8 to 2.2.4] Secondary Storage VM could not start after stopping it.
...
Added log statement to indicate that a pool is not chosen because the vm template has no entry in template_host_ref table.
2011-04-13 18:09:28 -07:00
9afee0bb46
bug 9433: update network_id (if 0 or NULL) in user_statistics table
...
status 9433: resolved fixed
2011-04-13 17:48:49 -07:00
7acba22063
bug 9436: include page/pageSize/keyword to api xml doc for each list* command
...
status 9436: resolved fixed
2011-04-13 16:19:44 -07:00
prachi
Murali Reddy
Kelven Yang
alena
Alex Huang
anthony
root
Abhinandan Prateek
will
Edison Su
root