The platform uses configuration properties to control the number of concurrent operations for a hypervisor or provider, device, or backup manager. This feature also enables you to change the context of concurrency control from the hypervisor/provider level to the VDC level. So you can control concurrent operations on a specified type of hypervisor, public cloud region, or VDC. This enables administrators to restrict only a specific hypervisor type The platform can control concurrency for VM operations and many kinds of entities associated with VMs (firewalls, load balancers, NAT IPs, and backups).
You can now define limits for specific hypervisor type or provider (e.g. vCloud with no concurrency) without affecting other types (e.g. ESXi with maximum concurrency).
At And you can also change the context of concurrency control to the VDC level, . This means that the platform can limit concurrent operations that affect the same virtual datacenter, while allowing ones concurrent operations to other VDCs. Through the VDC context, the platform can control concurrency for the many kinds of entities associated with a VM (its firewalls, load balancers, NAT IPs, and backups).
You can choose to You sets the limits at the platform or provider levels, and the platform applies these limits PER VDC.
You can also allow concurrent operations that change the state of a VM , (e.g. powering it power on), while limiting VM concurrent configure operations.
List of VM operations where the platform controls concurrency
...