[CLOUDSTACK-9112] deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.6.0
• Fix Version/s: Future
• Component/s: Management Server
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Harikrishna Patnala
• Reporter: Harikrishna Patnala
• Created: 07/Dec/15 06:20
• Updated: 16/May/17 05:50

Description

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.

Issue Links

• links to: GitHub Pull Request #1180