Hi Chip, Thanks for the feedback,
I'm well aware of that. But here is some food for thought. I was running everything of NFS backend, primary and secondary stores. As I was running out of disk space I decided to decommissioned my primary NFS store and use VMFS instead. Here is a kicker, I've only had about 10 - 15 VMS in this env - very much lean with nothing but operating systems. This is POC, production will have several 100s. My attempt to place NFS store in maintenance mode and bring up these VMs on VMFS - is still in progress. Its been over 10 hours. Mostly due to the fact that it runs 1 operation at a time. Here is another scenario to try - more realistic, on the hypervisor that has many VMs, preferably 30 or more, place it into maintenance mode. This operation will take at least an hour or two depending on your setup - again due to the fact that we are running it in serial. Even if we can bump up the number of threads to 2, this will greatly increase productivity. Regards ilya -----Original Message----- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Tuesday, April 02, 2013 10:30 AM To: dev@cloudstack.apache.org Subject: Re: [VMWARE]Any way to allow concurrent operations? 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.
