cloudstack/engine
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
..
api CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for instances with vm snapshots 2017-02-06 23:39:01 -03:00
components-api CLOUDSTACK-8746: vm snapshot implementation for KVM 2017-01-24 21:47:30 +01:00
network Updating pom.xml version numbers for release 4.9.3.0-SNAPSHOT 2017-01-06 10:40:15 +05:30
orchestration Merge release branch 4.9 to master 2017-03-13 22:09:27 +05:30
schema 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
service Updating pom.xml version numbers for release 4.9.3.0-SNAPSHOT 2017-01-06 10:40:15 +05:30
storage Merge pull request #1825 from Accelerite/CLOUDSTACK-9660 2017-02-28 06:00:02 +05:30
pom.xml Updating pom.xml version numbers for release 4.9.3.0-SNAPSHOT 2017-01-06 10:40:15 +05:30