We don't use queue facility/concurrency management within CloudStack extensively for now, the orchestration flow (i.e., putting storage into maintenance process) should launch concurrent tasks and manage it properly to achieve maximum of concurrency without breaking integrity of the operation.
We do need to add more convenient facilities at framework level to enable these apparently needed features in various individual orchestration flows. Currently we write most of orchestration flows in a sequential execution manner. Kelven On 4/2/13 8:12 AM, "Marcus Sorensen" <shadow...@gmail.com> wrote: >Edison was saying something about executeInSequence, causing the serial >operations, and how it was a compatibility thing. He said he removed it >once as a test and it seemed to work for concurrent operations on KVM, but >I don't know much about it. Just thought it was worth mentioning. > > >On Tue, Apr 2, 2013 at 9:06 AM, Chip Childers ><chip.child...@sungard.com>wrote: > >> On Tue, Apr 02, 2013 at 02:56:24PM +0000, Musayev, Ilya wrote: >> > Long story short - due to the fact, we do things serially, any mass >> operation will be queued, and may take very long time to complete. >> > >> > We need to improve this area, as its going to be one of the major >> complaints in the near future for corporate users that run vmware. >> >> Sounds like something that we should create as an "Improvement" ticket. >>
