[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706525#comment-13706525
 ] 

ASF subversion and git services commented on CLOUDSTACK-2843:
-------------------------------------------------------------

Commit dd91974920c8a8c6b10010aaa95e5ac6987d4c35 in branch refs/heads/master 
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dd91974 ]

CLOUDSTACK-2843: added CopyCommand to the list of the commands controlled by 
execute.in.sequence.hypervisor.commands global config. This command was 
introduced by the Storage refactoring, and used for volume creation on the 
primary storage

                
> Support parallel VM deployment with CloudStack
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-2843
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843
>             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: http://www.atlassian.com/software/jira

Reply via email to