[ https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk resolved CLOUDSTACK-2843. ------------------------------------------- Resolution: Fixed For QA to test DeployVm cases ============================================ * deploy multiple vms for the new network * deploy multiple vms for the existing network in Implemented state * deploy multiple vms from password enabled template * deploy multiple vms with huge userData. Make sure user data was set for all of them * deploy multiple vms from password enabled template. Make sure that the password works for all of them Start Vm cases ============================================= * start multiple vms that are in Stopped state * start multiple vms having more than 1 disk attached * start multiple vms with huge user data Stop vm cases ============================================ * stop multiple vms * execute stop commnad right after start command was sent for the vm StartCommand StopCommand CreateCommand CopyVolumeCommand DhcpEntryCommand PasswordResetCommand UserDataCommand VmDataCommand * Test on different hypervisors * Check that you can turn synchornization back on by changing following parameters values to true (false by default): execute.in.sequence.hypervisor.commands execute.in.sequence.network.element.commands > 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