Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of kelven.yang@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Kelven Yang <kelven.yang@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Date: Tue, 2 Apr 2013 10:26:46 -0700
Subject: Re: [VMWARE]Any way to allow concurrent operations?
Thread-Topic: [VMWARE]Any way to allow concurrent operations?
Thread-Index: Ac4vx0EKUMSLLqPaRia97UpDiJQS7g==
Message-ID: <CD806039.3B497%kelven.yang@citrix.com>
In-Reply-To: 
 <CALFpzo5cgFJ+sVB_KK07Rt6mE3fWGUv3KAoy7qe9Gsmv5cHi8A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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.=20

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" <shadowsor@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.childers@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.
>>