cloudstack/server
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
..
conf Remove extraneous log directory and add catalina.out log rotation 2016-05-12 08:41:39 +01:00
resources CLOUDSTACK-9456: Update Spring version in maven poms 2016-12-16 21:21:20 +05:30
scripts License header updates for the server folder. 2012-08-03 09:41:27 -04:00
src 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
test 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
pom.xml Updating pom.xml version numbers for release 4.9.3.0-SNAPSHOT 2017-01-06 10:40:15 +05:30