6e6e8ff876
better expunge and destroy of volumes
2011-01-11 18:02:09 -08:00
eec9f5f6f6
A minor fix to take into account stopping of a vm in stopping state. We will get a concurrentmodificationexception, and end in errorinmaintenance. This behavior is consistent with how stop works for cpvm.
2011-01-11 17:11:41 -08:00
8995a0afb6
adding more logging for the corner case
2011-01-11 12:14:13 -08:00
95756802e3
bug 7899: this seems to be a corner case, and from the logs, there was a vol with no pool id associated with it. Adding a check against it, as this should never happen
...
status 7899: resolved fixed
2011-01-11 12:11:46 -08:00
323fc6299d
Use volume state to determine whether or not we need to send volume DestroyCommand to hypervisor hosts.
2011-01-07 05:41:28 -08:00
be174f7f36
correct checking answer
2011-01-07 13:54:58 -08:00
d2196d169e
Moved global lock inside storage cleanup method.
2011-01-06 17:46:36 -08:00
3aa1726009
bug 7822: fixing the storage maintenance failures centered around domr stop/start
...
status 7822: resolved fixed
2011-01-04 17:37:50 -08:00
4eba6d10d7
Moved State into VirtualMachine like other States of objects
2011-01-04 15:01:34 -08:00
0b7a15ab99
bug 7348: reapply PortForwardingRules (including 1-1 Nat), LB rules, Vpn as a part of domr Stop/Start
...
status 7348: resolved fixed
More fixes:
* Update user_statistics on each domR stop/reboot
* Reset dhcpData/userData as a part of domR stop/reboot
* More logging for domR commands
2011-01-03 23:00:05 -08:00
e7749afdfe
Bug 7772: Add hypervisor type to snapshots table, fix issues with createVolumeFromSnapshot if snapshot was taken under data volume
2010-12-29 21:54:17 -08:00
544fa7ff1b
remote access vpn, user ip address changes
2010-12-29 09:32:54 -08:00
494a46a10f
bug 7735: Set null for templateId instead of -1 for usage records
...
status 7735: resolved fixed
2010-12-29 18:29:14 +05:30
f865e8b061
moveVolume is broken due to not setup hypervisortype in dskch
...
fixed
2010-12-28 19:46:21 -08:00
d005f9133e
bug 7603: update uservm count when deploy/recover vm. Also fixed updating volumes count when volume is created as a part of vm deployment
...
status 7603: resolved fixed
Couple of other fixes:
* Set correct user_id for createVolume event instead of hardcoding it to System (1)
* Deploy dhcp vm when Zone's gateway provider is External Firewall and network is Virtual
2010-12-28 17:32:17 -08:00
344a151ffe
someone had commented out the domr code in the storage maintenance, enabling the same
2010-12-27 15:25:02 -08:00
bb7170884d
bug 7677: fixing the volumes issue when we destroy a vm
...
status 7677: resolved fixed
2010-12-27 13:54:52 -08:00
e51dc79000
bug 7504: Events refactoring
...
status 7504: resolved fixed
2010-12-24 19:38:28 +05:30
53d3455cbe
bug 7504: Events refactoring
2010-12-24 12:58:32 +05:30
bb0e6a0ae3
bug 7504: Events refactoring
2010-12-24 12:58:32 +05:30
b12cd70216
bug 7504: Added usage events and made corresponding changes in usage server
2010-12-22 18:03:24 +05:30
a7626fc991
bug 7504: Added usage events
2010-12-22 12:28:05 +05:30
6b1e4d92ef
made some changes to the vm expunge flow, also added a state transition to error for vm if creation fails
2010-12-21 12:48:13 -08:00
0ecb0118ec
renamed the domainrouter services
2010-12-21 03:56:01 -08:00
356526db83
Changed exception code to give the scope of the problem
2010-12-21 03:54:30 -08:00
6eacec782e
bug 7528: the vm expunge action wasn't destroying the volumes during vm destroy. Added logic to do that. Also, made sure the volumes are removed during vm expunge
...
status 7528: resolved fixed
2010-12-20 14:56:32 -08:00
583d4a2c2e
bug 7582: there was an error in re-starting user vm, due to the master refactor which happened. Fixed that regression
...
status 7582: resolved fixed
2010-12-20 12:40:44 -08:00
65d0b32182
removed a bunch of old code
2010-12-16 14:04:32 -08:00
e39f664e89
fix storage creation bugs
2010-12-13 20:48:31 -08:00
d077b127aa
bug 7498: fixed search by keyword in listUserVm/listSystemVms/listRouters commands
...
status 7498: resolved fixed
2010-12-13 15:22:11 -08:00
33f71e1250
bug 7408: returning the source id and source type for vol creation
...
status 7408: resolved fixed
2010-12-13 12:38:43 -08:00
dedfe57280
seraral fixes for VMFS storage
2010-12-11 11:08:39 -08:00
790bf40be6
Forgot what i change but must be important
2010-12-10 17:20:31 -08:00
712953156b
fix boot from iso/attach iso/disks issue
2010-12-09 14:25:44 -08:00
bf987c57d9
bug 6838: during vm creation, the volume's device id wasn't set leading to npe during attaching a new vol to the vm (it checks for device ids)
...
status 6838: resolved fixed
2010-12-07 14:59:54 -08:00
daa9add158
removed router stuff from network manager
2010-12-04 17:32:31 -08:00
4fc18ce760
bug 7414: defaulting startretry to 10 at all references in code
2010-12-03 09:54:21 -08:00
b859e103d8
ip nat rule forwarding done
2010-12-03 08:48:03 -08:00
b51a7fec50
adding a security checker whilst creating a volume from a disk offering
2010-12-01 09:53:13 -08:00
0273872b34
bug 7362: we were missing the size validation check, when we create a volume from disk offering (the storage.max.volume.size param wasn't being used for validation). Fixed the same, made the validation method name more generic to be applicable to all validations, and changed the param description to denote GB as the unit
...
status 7362: resolved fixed
2010-11-29 17:23:16 -08:00
3d4b8ab4a0
bug 7263: changing the param name. Found a couple of bugs whilst testing this, the validation of vol size whilst cust vol creation was missing. Adding the same.
...
status 7263: resolved fixed
2010-11-23 16:20:30 -08:00
40c3a0afa2
bug 7249: during volume creation (root and data) for a vm, there was no state being set (we need to set it to ready). Hence, whilst re-attaching a detached vol, we hit a NPE. Fixed the root cause of the state not being set during vm creation, and consequently, fixed this npe
...
status 7249: resolved fixed
2010-11-23 14:24:29 -08:00
8995e5d2f7
changing the event logged to the right type, whilst starting user vms via cancelstoragemaintenance in master (already merged to 2.2.beta1)
2010-11-22 16:20:18 -08:00
0979b644ef
bug 7230: there was an issue trying to start user vms when the pool state is cancelmaintenance; fixing the same in 2.2RC2
...
status 7230: resolved fixed
2010-11-22 11:00:43 -08:00
1e44925564
api refactoring
2010-11-21 12:00:21 -08:00
138e0914b6
bug 7245: don't try to set vm name for detached volume during expunge process.
...
status 7245: resolved fixed
Fixed couple of other problems:
* cleanup corresponding records in load_balancer_vm_map table when loadBalancerRule is removed.
* don't log "java.lang.IllegalStateException: getAttribute: Session already invalidated" exception when UI session expires
2010-11-19 20:08:18 -08:00
0c35f2f743
bug 7237: disk size is passed in diskProfile, no need size parameter in createcommand
...
status 7237: rresolved fixed
2010-11-19 11:55:27 -08:00
317554d983
ensuring all the following have api values taken in, in GB (disk offering, service offering, custom vol creation and vm creation from cust disk offering)
2010-11-18 14:32:50 -08:00
5490577469
1) Remove forwarding between eth1 and eth2 as it does not solve the problem of asymmetic routing
...
2) correct Eclipse project settings
3) If VM is hosted by vmware hypervisor, give the previous host preference to start on to fit VMware's VM-centric model
2010-11-17 15:55:04 -08:00
c5d78a726e
Modified exception handing in API. Following exceptions are supported now (location - BaseCmd.java):
...
* MALFORMED_PARAMETER_ERROR - when type of the request parameter is invalid (String instead of Long for id for example)
* PARAM_ERROR - when invalid parameter value is specified in api request. For example, id of non existing vm for StartVmCmd
* ACCOUNT_RESOURCE_LIMIT_ERROR - when user tries to exceed his resource limits by executing the api command.
* INSUFFICIENT_CAPACITY_ERROR - when resource fails to create/start due to insufficient capacity.
* RESOURCE_UNAVAILABLE_ERROR - when user tries to create a vm when storage is not available.
* RESOURCE_IN_USE_ERROR - when user tries to delete/modify resource while it's in use. For example, when we try to delete a network group when it contains ingress rules.
* NETWORK_RULE_CONFLICT_ERROR - when LB/PF rule to add conflicts with existing rule
* ACCOUNT_ERROR - when user is not authorized to execute operation on the resource.
* INTERNAL_ERROR
2010-11-16 11:56:34 -08:00
Alex Huang
abhishek
Kelven Yang
anthony
keshav
alena
kishan
edison