cloudstack/engine/orchestration
Mike Tutkowski e471a46a05 managed-storage: handle VM start in a new cluster on different host (#2656)
Example: A VM that uses managed storage is stopped. The VM is then started on a different host in the same cluster. The Start operation fails.

To get around this issue, you must either start the VM up on the same host or on a host in a different cluster.

The reason is due to a slightly erroneous check in VolumeOrchestrator.prepare.

To solve this issue, we should be checking if the cluster ID changes, not if the host ID changes.
2018-05-21 16:22:33 +05:30
..
resources/META-INF/cloudstack/core CLOUDSTACK-10108: ConfigKey based approach for reading 'ping' configuaration (#2292) 2018-01-05 11:23:42 +05:30
src managed-storage: handle VM start in a new cluster on different host (#2656) 2018-05-21 16:22:33 +05:30
test config-drive: support user data on L2 networks (#2615) 2018-05-09 21:33:11 +05:30
pom.xml CLOUDSTACK-10132: Extend support for management servers LB for agents (#2469) 2018-03-15 16:34:03 +05:30