sorry. executeInSequence=false
2013/5/29 Nguyen Anh Tu
> I just changed StartCommand.java with executeInSequence=true and tested it
> with Xen XCP 1.1. The speed was enhanced beatifully.
>
> Thanks.
>
>
> 2013/4/5 Jeronimo Garcia
>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-1940
>>
>>
I just changed StartCommand.java with executeInSequence=true and tested it
with Xen XCP 1.1. The speed was enhanced beatifully.
Thanks.
2013/4/5 Jeronimo Garcia
> https://issues.apache.org/jira/browse/CLOUDSTACK-1940
>
> Thank you all.
>
>
> On Thu, Apr 4, 2013 at 3:15 PM, Jeronimo Garcia >wr
https://issues.apache.org/jira/browse/CLOUDSTACK-1940
Thank you all.
On Thu, Apr 4, 2013 at 3:15 PM, Jeronimo Garcia wrote:
> Hi All.
>
> Thanks for the help .
>
> I'll be trying to fill a bug about this today/tomorrow.
>
> Thanks Again
>
>
> On Thu, Apr 4, 2013 at 3:12 PM, Chip Childers
> wro
> -Original Message-
> From: Alex Huang
> Sent: Thursday, April 4, 2013 1:09 PM
> To: dev@cloudstack.apache.org
> Subject: RE: Job-Executor workers
>
> Jeronimo,
>
> Do you mind filing a bug for this?
>
> There's some legacy with this th
Hi All.
Thanks for the help .
I'll be trying to fill a bug about this today/tomorrow.
Thanks Again
On Thu, Apr 4, 2013 at 3:12 PM, Chip Childers wrote:
> On Thu, Apr 04, 2013 at 01:09:00PM -0700, Alex Huang wrote:
> > Jeronimo,
> >
> > Do you mind filing a bug for this?
> >
> > There's some l
On Thu, Apr 04, 2013 at 01:09:00PM -0700, Alex Huang wrote:
> Jeronimo,
>
> Do you mind filing a bug for this?
>
> There's some legacy with this that went all the way back to 1.0 of our
> product. Back then, multiple commands executing on the same hypervisor was
> just not very reliable. Xe
com]
> Sent: Thursday, April 4, 2013 12:40 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Job-Executor workers
>
> Ok I'll rebuild and see the differences and wether we want to have this live
> or not .
>
> Thanks a lot for your help!
>
>
> On Thu, A
Most of commands are executed in sequence at per-host scope, there will be
some concurrency when VMs are being deployed among different hosts.
However, for each individual orchestration flow, concurrency is usually
not in consideration in current code base.
Kelven
On 4/4/13 12:39 PM, "Jeronimo G
Ok I'll rebuild and see the differences and wether we want to have this
live or not .
Thanks a lot for your help!
On Thu, Apr 4, 2013 at 2:23 PM, Alena Prokharchyk <
alena.prokharc...@citrix.com> wrote:
> No, it can't be updated using UI/WebServices APIs.
>
> I remember somebody in the dev list
No, it can't be updated using UI/WebServices APIs.
I remember somebody in the dev list mentioned that he modified
StartCommand.java with executeInSequence=false and tested it with KVM
hypervisor, and it worked for him. Not sure how concurrent starts (and how
many) are supported by other hypervisor
Hi.
I can see the override on *agent/api/StartCommand.java*
*
*
*@Override*
*public boolean executeInSequence() {*
* return true;
*
*}*
*
*
I'm guessing this can't be changed from the gui or api right?
Thanks
On Thu, Apr 4, 2013 at
Thanks Alena, im checking that out now.
Chiradeep , I'm using the default centos template that comes with the
secondary storage sys vm.
Thanks!
On Thu, Apr 4, 2013 at 1:53 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:
> Note that each deployment to local storage has to download the
Note that each deployment to local storage has to download the base
template to local disk from secondary storage. How big is the template?
How fast is your secondary storage?
On 4/4/13 11:36 AM, "Jeronimo Garcia" wrote:
>Hi List.
>
>I'm having issues when deploying a big number of virtual mach
Hi Jeronimo,
The StartCommands for the Virtual machine are executed sequentially by the
agent. This behavior is set as "executeInSequence" flag on the command
level.
You might look at the Command abstract class (StartCommand extends it) to
see how it works. But basically if this flag is set to tr
14 matches
Mail list logo
