On Tue, Apr 02, 2013 at 01:35:13AM +0000, Musayev, Ilya wrote: > If I need to do a mass operation on my vmware cluster, all jobs will be > schedule and executed one at a time. > > If you need to do a mass migration from one storage to another, this may take > enormous amount of time. vSphere allows at least 4 concurrent operations and > others are scheduled until the queue frees up. > > Is there any possible method of allowing concurrent operations and not > waiting for job X to complete before another one executes? > > Thanks > ilya
AFAIK, CloudStack takes the approach of acting as the throttling mechanism itself for VMware interactions. You're right that vSphere is able to handle some number of concurrent operations (depending on the operation, the target host and / or datastore, and the version of vSphere), and that it does queue up tasks in Virtual Center. I can offer a warning though, that we should probably be careful about trying to make any change to the way CloudStack does this. Virtual Center will actually time-out tasks that may not ever have a chance to run if they are pending for too long. This may confuse CloudStack's logic in that scenario.
