cloudstack/server/test/com/cloud/vm
Harikrishna Patnala f34469a41b CLOUDSTACK-9112: deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner
There are some VM deployment failures happening when multiple VMs are deployed at a time, failures mainly due to NetworkModel code that iterates over all the vlans in the pod. This causes each deployVM thread to hold the global lock on Network longer and cause delays. This delay in turn causes more threads to choose same host and fail since capacity is not available on that host.

Following are some changes required to be done to reduce delays during VM deployments which in turn causes some vm deployment failures when multiple VMs are launched at a time.

    In Planner, remove the clusters that do not contain a host with matching service offering tag. This will save some iterations over clusters that dont have matching tagged host
    In NetworkModel, do not query the vlans for the pod within the loop. Also optimized the logic to query the ip/ipv6
    In DeploymentPlanningManagerImpl, do not process the affinity group if the plan has hostId provided.
2017-03-15 15:21:29 +05:30
..
dao CLOUDSTACK-7908: Add user_id column to vm_instance table 2015-02-16 15:02:38 +05:30
snapshot CLOUDSTACK-9539: Support changing Service offering for instance with VM Snapshots 2017-02-16 10:49:09 -03:00
DeploymentPlanningManagerImplTest.java Signed-off-by: Koushik Das <koushik@apache.org> 2017-01-10 14:46:52 +05:30
FirstFitPlannerTest.java CLOUDSTACK-9112: deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner 2017-03-15 15:21:29 +05:30
UserVmManagerTest.java CLOUDSTACK-7985: (1) allow migrate vm from/to project; (2) UI change for selecting account/project/network 2016-12-27 11:58:25 +01:00