cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2843) Support parallel VM deployment with CloudStack
Date Thu, 27 Jun 2013 18:58:19 GMT


ASF subversion and git services commented on CLOUDSTACK-2843:

Commit 0035bbba34d57c6b6bc35d5ada751235e7a7fb35 in branch refs/heads/master-6-17-stable from
[;h=0035bbb ]

Reverting the commit for parallel vm deployment, from beta branch

Revert "CLOUDSTACK-2843: Provideded an ability to turn off the synchronization being done
on the CS agent side,"

This reverts commit 0fe7c5c9353eb1970238015cf48668d196adf82d.


> Support parallel VM deployment with CloudStack
> ----------------------------------------------
>                 Key: CLOUDSTACK-2843
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.2.0
> When a user deploys multiple instances concurrently, the deployment of these VMs are
in fact queued up, so although CloudStack reports that all deployments have started to be
created, it would appear in reality that until the 1st instance is deployed, the second, third,
etc are queued and waiting to be executed. 
> CS should be able to support parallel VM deployment assuming the cluster resources can
handle it.
> As a part of it, we have to:
> 1) Set executeInSequence=false for Start/Stop commands (also might make it false for
PrimaryStorageDownload command as well)
> 2) Identify possible implication of turning off the synchronization for those commands,
and fix the problematic places in the code.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message