Koushik Das 331e257ca0 CLOUDSTACK-8103: Vmsync marks VM as stopped even after failing to stop it in HV ...

During vmsync if StopCommand (issued as part of PowerOff/PowerMissing report) fails to stop VM (since VM is running on HV),
don't transition VM state to "Stopped" in CS db. Also added a check to throw ConcurrentOperationException if vm state is not
"Running" after start operation.

2014-12-22 10:52:13 +05:30

..

api

CLOUDSTACK-8066: There is not way to know the size of the snapshot created.

2014-12-17 16:00:19 +05:30

components-api

CLOUDSTACK-8061: Extracting volume when it is in migrating state causes

2014-12-11 09:53:33 -08:00

network

removed executable flags from java classes

2014-11-23 19:49:01 +01:00

orchestration

CLOUDSTACK-8103: Vmsync marks VM as stopped even after failing to stop it in HV

2014-12-22 10:52:13 +05:30

schema

CLOUDSTACK-8097: Failed to create volume snapshot after vm live migration across clusters.

2014-12-19 14:26:48 +05:30

service

CLOUDSTACK-8011: Upgrade maven dependencies

2014-12-04 02:12:51 +05:30

storage

CLOUDSTACK-8101: volume sync not working as expected - MS restart during upload volume leaves volume in hung state.

2014-12-19 16:51:41 -08:00

pom.xml

Bump master version to 4.6.0-SNAPSHOT after branching 4.5.0-SNAPSHOT

2014-10-29 14:54:23 +01:00